• 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 route additional cells after normal P&R

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 91
  • Views 938
  • 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 route additional cells after normal P&R

Sirrius
Sirrius over 16 years ago

 Hi All

My job involves taking a routed design and changing some of the cells and routing them to the cells that already exist.

I looked at some ways, and the most obvious way is to manually "Add Wire" option in Encounter. Is there any way to tell the routing tool built in (like sroute) to route the cell for me? For example, I would like to route (or connect) a cell MY_CELL1/PortA (where PortA is the port of this cell) to MY_CELL2/PortB.

Can I use sroute? If yes, then, can someone please throw a hint as to how?

Any other method? I am sure that some method should exist, which should avoid manual "Add Wire" method.

 

Would appreciate any help!

 

Thanks

  • Cancel
Parents
  • BobD
    BobD over 16 years ago

    Hi Sirrius,

    Incremental capabilities aside for a moment, which automatic routing function you should use in general depends on the nature of the signals being routed.  NanoRoute (ie, "globalDetailRoute") is typically used for routing signal and clock nets.  "sroute" is typically used for routing power/ground connections so it doesn't seem well-suited to your purpose (I'm inferring this from the PortA/PortB names you mentioned rather than VDD/VSS).

    Automatic routers in the tool rely on logical connections being in place which instruct the router as to which connections should be made.  For signal nets, these connections are determined from the input Verilog netlist primarily, which can be altered in-session with ECO commands like "addInst", "addNet", and "attachTerm".  You could verify these connections by clicking the terminals and querying their net and flight lines.

    Once these connections are logically in place, you can proceed with incrementally routing them with "globalDetailRoute".  It would probably be good to "setNanoRouteMode -routeWithEco true" to inform the tool that routing is present and the tool should incrementally refine the routing.

    Hope this helps,
    Bob

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • BobD
    BobD over 16 years ago

    Hi Sirrius,

    Incremental capabilities aside for a moment, which automatic routing function you should use in general depends on the nature of the signals being routed.  NanoRoute (ie, "globalDetailRoute") is typically used for routing signal and clock nets.  "sroute" is typically used for routing power/ground connections so it doesn't seem well-suited to your purpose (I'm inferring this from the PortA/PortB names you mentioned rather than VDD/VSS).

    Automatic routers in the tool rely on logical connections being in place which instruct the router as to which connections should be made.  For signal nets, these connections are determined from the input Verilog netlist primarily, which can be altered in-session with ECO commands like "addInst", "addNet", and "attachTerm".  You could verify these connections by clicking the terminals and querying their net and flight lines.

    Once these connections are logically in place, you can proceed with incrementally routing them with "globalDetailRoute".  It would probably be good to "setNanoRouteMode -routeWithEco true" to inform the tool that routing is present and the tool should incrementally refine the routing.

    Hope this helps,
    Bob

     

    • 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