• 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. Layout and LVS of a non-standard device!

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 14859
  • 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

Layout and LVS of a non-standard device!

Ueue
Ueue over 16 years ago

Hi,

I'm currently trying to draw the layout of a device not present in the library of my technology. So, I think to create a symbol to put in the schematic of my circuit and after to draw the complete layout.

When I will finish the layout, what can I do to execute the LVS?

I think the LVS will not recognize the new device. Someone suggested me to add a lot of labels in my circuit near to the non-standard devices.

Is it a good idea?

Are there other more efficient method to execute the LVS of circuit with non-standard devices?

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

    Hi Stefano,

    If the device does not get recognized by the LVS rules, then I think your best bet (if you don't want to code the recognition into the rule deck - which would be worth it if you're using them a lot) would be to use a black box approach.

    Relying on labelling nets around the device is risky - for a start, it's hard to guarantee that the mismatch of this device would only cause a localized problem - it could cause a bigger mismatch (this is very dependent on the LVS tool you're using). Also, it makes it much hard to distinguish between real errors and intentional errors such as this.

    So I refer you back to the suggestions I made in my previous reply.

    Regards,

    Andrew.

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

    Hi Stefano,

    If the device does not get recognized by the LVS rules, then I think your best bet (if you don't want to code the recognition into the rule deck - which would be worth it if you're using them a lot) would be to use a black box approach.

    Relying on labelling nets around the device is risky - for a start, it's hard to guarantee that the mismatch of this device would only cause a localized problem - it could cause a bigger mismatch (this is very dependent on the LVS tool you're using). Also, it makes it much hard to distinguish between real errors and intentional errors such as this.

    So I refer you back to the suggestions I made in my previous reply.

    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