• 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. Nanoroute stops at Placement blockage

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 91
  • Views 15222
  • 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

Nanoroute stops at Placement blockage

schnufff
schnufff over 12 years ago

In my design with 5 cores I have a Placement blockage around each core. This was suggested by Kari to stop sroute from connecting all follow pins together. But now CTS and also nanoroute stops routing all signal that run from the cores trough the blockage to the IO pads.

I though its a placement blockage and not a routing blockage. Trial route works fine, but produces a lot of violations. What can I do to

allow nanoroute to pass trough the placement blockage?

Thanks

Stefan

  • Cancel
Parents
  • schnufff
    schnufff over 12 years ago

     Hi Kari,

    after reading the manual, I am able to route the wires manually without problems. I also can see the pins of the IOs at layer M2 and M3.

    There is no attribute like special/power/whatever set to the wires.  The lef files of the cells have CLASS PAD INOUT, the Pins have USE SIGNAL, and a PORT definition with the metal layers. In the def file, in SPECIALNETS are only the power nets and in NETS are all the signal as expected.I am unshure if tis an error within the lef files are some tool set these "fully connected" attribute wrong. Trial route is connecting the IO-wires correct! So the physical pins seem to be there.

    Thanks

    Stefan

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • schnufff
    schnufff over 12 years ago

     Hi Kari,

    after reading the manual, I am able to route the wires manually without problems. I also can see the pins of the IOs at layer M2 and M3.

    There is no attribute like special/power/whatever set to the wires.  The lef files of the cells have CLASS PAD INOUT, the Pins have USE SIGNAL, and a PORT definition with the metal layers. In the def file, in SPECIALNETS are only the power nets and in NETS are all the signal as expected.I am unshure if tis an error within the lef files are some tool set these "fully connected" attribute wrong. Trial route is connecting the IO-wires correct! So the physical pins seem to be there.

    Thanks

    Stefan

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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