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

Stats

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

LVS errors

tester
tester over 15 years ago

Hi All,

I am using ic5.1.41 for schematic, Virtuoso XL layout and Jazz CA 18 for design kits. After running LVS, I got the following warning and error message. Can anyone give me some hints please? thanks

 

  • result.jpg
  • View
  • Hide
  • Cancel
  • Quek
    Quek over 15 years ago

    Hi tester

    Would you please upload your cls file? This means the file with .cls extension in the run directory. It would be great if you can also provide the specific version of the tool which you are using. E.g.

    terminal>assura -W

    Thanks
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • tester
    tester over 15 years ago

    Dear Quek,

    Thank you very much for your email. Here is the information that you requested:

    assura -w gives:

    ********************************************************************* 

    Assura (tm) Physical Verification Version av3.2:Production:dfII5.1.41:5.10.41.500.6.130

    Release 3.2_USR2_HF7

    no mcf file specified

    ***********************************************************************

    The following is the attached cls file

     

    test2.doc
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quek
    Quek over 15 years ago

    Hi tester

    It looks like rppoly_lo and ind devices in your layout cannot be extracted. This should be the main cause of your net mismatches. An in- depth troubleshooting would be required to understand why the devices cannot be extracted. Possible reasons are:

    a. Bug in extract.rul file
    b. Pdk and extract.rul file are out of sync. Pdk devices now uses slightly different layers and hence are not recognized by the rule deck

    Please contact your local Cadence support for more help. : )

    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