• 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. How to make nanoroute understand "USEMINSPACING"

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 90
  • Views 6514
  • 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

How to make nanoroute understand "USEMINSPACING"

archive
archive over 18 years ago

Hi,

I am facing the following issue for quite sometime. Wonder if anyone is also facing the issue and has a solution?

I have "USEMINSPACING OBS OFF ;" in the technolog lef. However, nanoroute places alot of wire at min spacing to "thick blockage". VerifyGeometry is able to detect these DRC, but nanoroute does not detect the violations. It is quite a pain to clean these violations post-layout.

Anyone also face this issue? Thanks.

Regards,
Eng Han



Originally posted in cdnusers.org by EngHan
  • Cancel
  • archive
    archive over 18 years ago

    Hi,
    Try the following:
    setNanoRouteMode -quiet drouteUseMinSpacingForBlockage false

    If the "thick blockage" is memory, those min_step violations you see maybe false, because LEF doesn't show the real route of the memory, and the blockage you see is not "thick". The final DRC checks are performed with GDS and not with LEF


    Originally posted in cdnusers.org by Stalker
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    Hi Stalker,

    Thanks for the tip. I try the setting, and it works around 95% of the time! For example, if I don't use this setting, I get 100 violations. If I use the setting, I get much less violations, about 5.

    With or without the settings, nanroute finished with 0 violations. Something else is still strange...

    Regards,
    Eng Han


    Originally posted in cdnusers.org by EngHan
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    It is possible that Nanoroute still did not see those 5 violationsblockages as fat blockages. In lef5.6 syntax, you can make those blockages with the spacing you want. You can check the lef reference doc. As for why Nanoute did not see the violation, one possible answer is that those are power wire with slotting and the lef is modeled it as thin blockage.

    li siang


    Originally posted in cdnusers.org by lisiang
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    Hi,

    I look at the remaing violations and observed that they are of the same type.

    The violation is between routed M4 with M4 pin (from the lef). The M4 pin is a power net. When this M4 pin tape to a wide M3 pin (also in the lef), spacing from the VIA34 has to obey wide metal spacig. It look like nanorouter does not understanding this while verifyGeometry detct the error.For now, I am not sure if nanoroute is correct or verifyGeometry is correct.

    Regards,
    Eng Han


    Originally posted in cdnusers.org by EngHan
    • 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