• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Digital Implementation
  3. Filtering of false DRC violations due to routing blockages...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 90
  • Views 13204
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Filtering of false DRC violations due to routing blockages in enounter.

KVBABU
KVBABU over 15 years ago

Hi All,

 I am implementing a  mixed signal design , in which i have huge number of custom routes in many areas. As a result we are employing routing blockages in those areas.  i.e. for example, i will route a custom net using metal3 and i will block further routing  of metal 3 in those areas. Like those , we have huge number of such  areas. So finally , after completing routing with Nanoroute, if i verify geometry  using the command 

  verifyGeometry -noRoutingBlkg

it is not filtering out the false violations with blockages. If there is any real violation, then it is tedious for me to manuulay filter out all thesefalse one's and trace out real violations.

Is there any way to mask these violations. Please suggest me .

 

Thanks in advance,

Regards,

K.VISWANADH BABU 

  • Cancel
  • BobD
    BobD over 15 years ago

    I did a test here on a small design and I'm unable to reproduce the problem you're seeing.  Here's what I did:

    I created a regular signal route with NanoRotue on M1 and placed a routing blockage over it.  I ran verifyGeometry and I saw a drc violation appear.  Then I cleared the violation markers and ran verifyGeometry -noRoutingBlkg.  The violation didn't appear.

    I also tried converting the route to a special route- still no violation reported with verifyGeometry -noRoutingBlkg.  I also tried marking the routes FIXED- still no violation reported with verifyGeometry.

    Let me know if you can think of any nuance that might be present in your situation that is different than what I've described here.  I've used 8.1.USR3 for my testing- let me know if you're on an earlier version and I can re-run these same tests.  If still no resolution then please file a service requrest at http://support.cadence.com

    Thanks,
    Bob

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information