• 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 SKILL
  3. error in running LVS

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 144
  • Views 14981
  • 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

error in running LVS

Aritra
Aritra over 13 years ago

Hi ,

      I am tring to run LVS in ASSURA. It is failing & error file says :

"*WARNING Corrupted type field (0x0x4f35d) at 0x0x4880cf8 in file <file location>layout.cdb

 *WARNING bad type table pointer 0x0x2a91d0004f35d at 0x0x4880cf8 "

Please help. I have no clue how to solve it.

  • Cancel
  • Quek
    Quek over 13 years ago

    Hi Aritra

    Would you please retry using latest version of Assura? If it still gives the same error, please file a service request to your local Cadence support. Thanks.

    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • zeynep
    zeynep over 9 years ago

    Hello,

    I have another error while running Assura LVS. After finilizing comparing layout and schematic it fails due to a (possibly some sort of DRC) error:

    (66)  ###### Eight levels of metal M1-M2-M3-MQ  ...

    I cannot see any reason because I am using an 8-metal process and using the correct metal layers. Although I can still reach the LVS result from the files generated, the real problem is due to extraction. Since LVS fails I cannot do the extraction either. Any idea about this issue?

    Thank you!

    Below is the end of the log file:  

    parCAPcomb Resultant: (nil bp 3 tlev2 2 tlev1 3 setind -99 par 1 m 1 c 1.501074e-10)

    Schematic and Layout Match

    *Error* ilGetInt: arg must be fixnum - nil

    ******* Non-recoverable error (no top-level or error handler)

    ******* Exiting program ...

    *WARNING* nvn exit with bad status

    *WARNING* Status 65280

    *****  nvn fork terminated abnormally  *****

    *WARNING* Assura execution terminated

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    The problem might be something to do with how the LVS rules are written, or it might be an issue with the specific version of Assura. You didn't mention which technology or Assura version you're using, but that said, I couldn't find any reports of this failure mechanism. Note, the error is almost certainly due to the ilGetInt bit, not the ##### Eight levels ... part (which is just a comment, I think).

    Almost certainly the best thing you could do is to contact customer support - I think we'll need to see the data. I'd check that you're using recent versions of Assura and have checked with the foundry if you have up to date rule decks or if they've seen the same problem.

    Regards,

    Andrew.

    • 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