Stats

  • Locked Locked
  • Replies 7
  • Subscribers 125
  • Views 19048
  • 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 short small resistor for lvs purpose

harleyMax

 h, i have a small resistoe which dracula lvs (version 4.8) used to short its 2 nodes, but, now i am using dracula version 4,9 and no longer short them in lvs. what options i have. i am using ic5.41.

Thanx a lot

max

Parents

  • Max,

    It's rather hard to see how *.RESI could work if you're using *.RESSIZE, given that the ignore threshold is specified as a resistance, and if the CDL netlist just has widths and lengths, it wouldn't know the resistance (the sheet resistance would not be known to LOGLVS).

    In fact the documentation for *.RESI (ICinstDir/doc/dracularef/dracularef.pdf) says:

    You must also specify the *.RESVAL command when using the *.RESI command. However, do not specify the *.RESSIZE command when using the *.RESI command as it may result in unpredictable behavior.

    Maybe it worked in the older version due to the "unpredictable behavior" mentioned above - something that should not have been relied upon

    Regards,

    Andrew.

Reply

  • Max,

    It's rather hard to see how *.RESI could work if you're using *.RESSIZE, given that the ignore threshold is specified as a resistance, and if the CDL netlist just has widths and lengths, it wouldn't know the resistance (the sheet resistance would not be known to LOGLVS).

    In fact the documentation for *.RESI (ICinstDir/doc/dracularef/dracularef.pdf) says:

    You must also specify the *.RESVAL command when using the *.RESI command. However, do not specify the *.RESSIZE command when using the *.RESI command as it may result in unpredictable behavior.

    Maybe it worked in the older version due to the "unpredictable behavior" mentioned above - something that should not have been relied upon

    Regards,

    Andrew.

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.