Stats

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

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.

  •  The layer directions for Encounter are defined in the techfiles (LEF).

     As for shorts, Trial Route is used as a "quick and dirty" way to gauge the congestion and routability of a design. It does not report shorts. Special Route and Nano Route will report shorts. They will appear as white "X" markers in the layout window.

  • Thanks for the answer. My LEF files have directions specified for each layer, but still the routing solution has small bends of the same metal layer sometimes. How do I disable that ? For example, even if M2 is specified to run Vertical in LEF file, sometimes routing solution uses M2 in Horizontal direction. Such instances are rare and for small length. But, I want to disable that for good. Which option would do that ?

     Thanks in advance.

     

     

  • 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.

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.