• 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 Parameter Mismatch Error

Stats

  • Locked Locked
  • Replies 14
  • Subscribers 127
  • Views 24073
  • 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 Parameter Mismatch Error

tonyinbos
tonyinbos over 7 years ago

Hi All,

I'm using Virtuoso Layout XL 617 and Assura 415, with TSMC mixed-mode 130nm PDK.

I included a multi-fingered NMOS moscap into the layout, using the generated parameterized cell. The Cap has 5 fingers, W=L=20um for each, with top&bottom plate connection, and top poly contact head.

 

The cell looked like that above.

However, when running assura lvs, I got the following error:

Schematic Instance: C0 nmos1v
Layout Instance: avD10_1 N

w 2e-05 vs 0.0001 differs by 400%
Layout Instance is the merged result of: avD10_1 avD10_2 avD10_3 avD10_14
avD10_15

While clearly the device has five fingers totaling 100um, ASSURA says it's only 20um. It works only when just 1 finger is used. Is there an explanation to this weird behavior of ASSURA? Thank you very much. -Tony

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 7 years ago

    It's unlikely to be Assura's fault - it's probably the rule deck (or the rule deck not being used properly). This is something that you either need to take up with the foundry (TSMC) or maybe as a first step Cadence Customer Support - that way we can look at the exact situation  you have - and retrieve the rule deck for the specific document number you have (there are several 130nm processes, so we'd need to check the right one) and check what's going on.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 7 years ago

    It's unlikely to be Assura's fault - it's probably the rule deck (or the rule deck not being used properly). This is something that you either need to take up with the foundry (TSMC) or maybe as a first step Cadence Customer Support - that way we can look at the exact situation  you have - and retrieve the rule deck for the specific document number you have (there are several 130nm processes, so we'd need to check the right one) and check what's going on.

    Regards,

    Andrew.

    • 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