Stats

  • Locked Locked
  • Replies 3
  • Subscribers 92
  • Views 17595
  • 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

Converting a Special Route to a Regular Wire

jgentry

I've finally delved into the 'dbCreateRestrictedViaCell' and 'dbCreateVia' commands.  Pretty slick!  However, I'm having trouble with "Special Route" versus "Regular Wire".  When I create vias on non-power/ground nets, I don't want my vias to end up in the "SPECIAL NETS" section of the DEF.  One way to do this is:
 
  dbCreateVia $netPtr $viaCellPtr $cX $cY
...then...
  convertSNetToNet -nets $net
  setNet -net $net -type regular
  editSelect -nets $net
  editChangeStatus -to FIXED

  However, this is HORRIBLY slow to do each time I create a new via.  I've removed this from the via-generation code and instead moved it into its own "convertSNetToNet" proc that can be run after via-generation is finished.  Anyone know of a better way? 

Parents

  • You could try editAddVia (along with setViaEdit to set parameters). I'm not sure if vias created this way would be marked as SPECIAL or REGULAR when adding a via to a REGULAR net. I've only used it for SPECIALNETs so far. Also, I'm not sure if these commands are slower than the dbCreate commands you are currently using. Worth a try though! Let us know what you find out if you try these.

     - Kari

Reply

  • You could try editAddVia (along with setViaEdit to set parameters). I'm not sure if vias created this way would be marked as SPECIAL or REGULAR when adding a via to a REGULAR net. I've only used it for SPECIALNETs so far. Also, I'm not sure if these commands are slower than the dbCreate commands you are currently using. Worth a try though! Let us know what you find out if you try these.

     - Kari

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.