• 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. Digital Implementation
  3. Innovus vs Calibre DRC results

Stats

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

Innovus vs Calibre DRC results

Anas2023a95
Anas2023a95 over 2 years ago

Dear all, 

I have a DRC-clean design on Innovus (verified by the Innovus tool: Verify -> Verify DRC). However, when I extract the GDS and import it into Calibre, hundreds of errors are highlighted! Calibre uses a separate DRC_rule_file which, I think, Innovus has no access to.
I guess Innovus only uses the rules in the .LEF files to generate and verify the layout, am I right?
Is it possible to feed the DRC_rule_file (what Calibre reads) to Innouvs so the generated layout meets those rules?
Should I trust Innovus and go ahead with the current design?
Could it be an issue with generating the GDS file? 

Many thanks,

Anas

  • Cancel
Parents
  • DimoM
    DimoM over 2 years ago

    Hi Anas,
    Calibre uses a runset file which cannot be consumed by Innovus. Innovus uses and knows only the rules as defined in the techLef.
    Sometimes it can happen that a rule is missing in Innovus or it is interpreted differently, but what we see here are 420000 violations for even simple width and spacing rules.

    Something went wrong with the setup of either Innovus or Calibre.

    Should I trust Innovus and go ahead with the current design? --> No, you need to resolve this issue.

    Could it be an issue with generating the GDS file?  --> This is indeed a possibility. Maybe you used the wrong mapping file ?

    Open the Calibre GUI and look at a few errors and their surroundings. See if the shapes are the same as in Innovus, in the same layer, the sizes of the features  etc.

    -Dimo

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Anas2023a95
    Anas2023a95 over 2 years ago in reply to DimoM

    Hi Dimo,

    Thank you for your reply!

    I tried to verify the GDS on PVS and it highlighted much fewer errors. However, some of those errors are related to densities (which I will deal with later), but some other errors are about widths and spacings (which I have to solve at this stage). 

    The violated rules that I'm trying to fix now are:

    1- maximum width of metal greater than <max>

    2- minimum metal area less than <min>

    3- minimum metal width less than <min>

    4- minimum spacing between vias less than <min>

    Are there commands to variables to set before the P&R process so Innovus can avoid violating those rules?

    Kind regards,

    Anas

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Anas2023a95
    Anas2023a95 over 2 years ago in reply to DimoM

    Hi Dimo,

    Thank you for your reply!

    I tried to verify the GDS on PVS and it highlighted much fewer errors. However, some of those errors are related to densities (which I will deal with later), but some other errors are about widths and spacings (which I have to solve at this stage). 

    The violated rules that I'm trying to fix now are:

    1- maximum width of metal greater than <max>

    2- minimum metal area less than <min>

    3- minimum metal width less than <min>

    4- minimum spacing between vias less than <min>

    Are there commands to variables to set before the P&R process so Innovus can avoid violating those rules?

    Kind regards,

    Anas

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • DimoM
    DimoM over 2 years ago in reply to Anas2023a95

    Hi Anas,

    these rules are supposed to be coded in the tech LEF which Innovus uses. Check which rules you can find in the tech LEF, and compare with the Calibre reports.

    Sometimes the LEF format is self-explanatory, but there are also complex constructs. Please refer to the LEF/DEF 5.8 Language Reference if you have doubts. 

    -Dimo

    • 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