• 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. SoC Encounter routing help needed !

Stats

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

SoC Encounter routing help needed !

Calistudent
Calistudent over 16 years ago

Hello,

I am using Cadence SoC Encounter tool. How to make sure that routing done using "Trial Route", "Special Route" or "Nano Route" is uni-directional on each layer ? For example, if M2 is horizontal, M3 is vertical and so on...

Also, how to check for routing shorts, i.e. when two nets are shorting after routing ?

Any comments on above two questions would be greatly helpful.

Thanks in advance.

  • Cancel
Parents
  • Scrivner
    Scrivner over 16 years ago

    There is no way to control the amount of non-preffered routing direction used in routing. Encounter determines this automatically based on congestion. Refer to Solution Number 11161520 on Sourcelink.

    If you're trying to route an entire block with these strict restrictions, the block probably would not route anyway. If there are only a few nets that you are concerned about, you could try using routing blockages to restrict the routing area for those specific signals and then routing just that collection of nets using the -routeSelectedNetOnly option of setNanoRouteMode.

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

    There is no way to control the amount of non-preffered routing direction used in routing. Encounter determines this automatically based on congestion. Refer to Solution Number 11161520 on Sourcelink.

    If you're trying to route an entire block with these strict restrictions, the block probably would not route anyway. If there are only a few nets that you are concerned about, you could try using routing blockages to restrict the routing area for those specific signals and then routing just that collection of nets using the -routeSelectedNetOnly option of setNanoRouteMode.

    • 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