• 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. Custom IC Design
  3. Assura LVS - How to force shorted layout devices to be netlisted...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 126
  • Views 2838
  • 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

Assura LVS - How to force shorted layout devices to be netlisted and compared?

miketqs
miketqs over 13 years ago
I would like to LVS shorted layout devices (resistors used for analog matching purposes, shorted to power or ground), but I can't get them to netlist on the layout side. I have commented out the filter("X") command in the compare.rul file. I also tried changing the device type from Generic to RES, but the shorted devices still don't netlist or get compared.
  • Cancel
  • Quek
    Quek over 13 years ago

    Hi miketqs

    The shorted layout resistor should not be filtered out if option "X" is not used. Would you please execute the following egrep cmd in the Assura rules file directory to check if there are any filter/filterOptions command which might have been missed out?

    terminal>egrep -ir "filter" your-rules-file-directory

    If you cannot find any useful info from the egrep cmd, would you please add avCompareRules option "echoUsedAvCompareRules", re-run LVS and upload your assura log file as an attachment?

    By the way, "filter" cmd has already been obsoleted and should be replaced by "filterOptions" cmd.

    Thanks
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • miketqs
    miketqs over 13 years ago
    Hello Quek,

    I resolved the problem.

    The real issue was that the shorted devices were being flagged as malformed devices, and this was causing them to not show up in the layout netlist.  Since these devices were generically defined using an extractDevice statement (as opposed to extractRES), the solution was to add in the "physical" option to the device statement.

    Thanks,
    -Mike
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quek
    Quek over 13 years ago

    Hi Mike

    That's great. : )  Thanks for the follow-up on the issue.

    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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