• 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. create a copy of device library, some parameters' limitCheck...

Stats

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

create a copy of device library, some parameters' limitCheck failed....

ringamp
ringamp over 4 years ago

I am doing the porting one project schematic from PDK1 to PDK2 (both GF foundry PDK). In order to keep the original wire connection, I uses the symbols of the element devices from PDK1 as reference then to modify those symbols of PDK2.

For library in PDK2, It is better way to copy the original device library (e.g. 180NSX1) to a new one (e.g. 180NSX1_mac) and in "Attach to an existing technology library" option I choose to attach to 180NSX1. I just rename the devices with "_mac" added.

here comes the question: (before I did any modification on symbol)

when I create an instance of resistor "opppcresx_mac" from library "180NSX1_mac", CIW windows says: *WARNING* one80NSX1baseResLengthLimitCheck()  : Device "opppcresx_mac" not suported...

when I try to modify "W" of "opppcresx_mac" from default value (e.g. 3u) to any number, it will automatically change to "0", and a window pop-up

                                 Limits Exceeded

        !    Device "opppcresx_mac":

              Width is larger than maximum value of 0. Resetting value.

So I want to know how to solve this problem and more importantly I want a right way to create a 180NSX1_mac library with only its device symbol shape changed and everything keep the same as its original

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

    I can't really advise on doing what you're doing - it's highly likely that there are interdependencies between the data in the device library which are very dependent upon how the foundry has implemented it - doing what you're doing appears to break that and appears to be rather dangerous as a result. The messages you are seeing are coming from the PDK code, and I have no idea what they are checking (even if I knew which PDKs were involved, I wouldn't be comfortable advising you to do any such modification). Perhaps you should speak to the foundry?

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ringamp
    ringamp over 4 years ago in reply to Andrew Beckett

    Thanks Andrew!

    So does it mean that it is better I only do porting on those devices and  re-do the wire connections ?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • ringamp
    ringamp over 4 years ago in reply to Andrew Beckett

    Thanks Andrew!

    So does it mean that it is better I only do porting on those devices and  re-do the wire connections ?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • Andrew Beckett
    Andrew Beckett over 4 years ago in reply to ringamp

    Maybe. I don't think I can really answer without the context and understanding what you're trying to do. Perhaps talking to customer support would make more sense.

    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