• 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. HELP: Warnings on setting technology library name

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 144
  • Views 15264
  • 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

HELP: Warnings on setting technology library name

frasheed
frasheed over 11 years ago

 Hello,

I am writing a short code to set the technology library property of the new library same as the old libraray. When I use the function:

techSetTechLibName(ddGetObj(newLib) oldLib )

 

*WARNING* ddGetObjLib: Was passed an Invalid Id (0x203763a0).

*WARNING* ddGetObjLib: Was passed an Invalid Id (0x1dc20fa0).

*WARNING* ddGetObjLib: Was passed an Invalid Id (0x1d72f3b0).

*WARNING* ddGetObjLib: Was passed an Invalid Id (0x1aa5cbb0).

*WARNING* ddGetObjLib: Was passed an Invalid Id (0x1e57d7c0).

*WARNING* ddGetObjLib: Was passed an Invalid Id (0x1da91fc0).

*WARNING* ddGetObjLib: Was passed an Invalid Id (0x1e567bc0).

*WARNING* ddGetObjLib: Was passed an Invalid Id (0x1d741fd0).

*WARNING* ddGetObjLib: Was passed an Invalid Id (0x1eb66bd0).

*WARNING* ddGetObjLib: Was passed an Invalid Id (0x1d342ff0).

*WARNING* ddGetObjLib: Was passed an Invalid Id (0x1cbd0ff0).

*WARNING* ddGetObjLib: Was passed an Invalid Id (0x1ded2ff0)

 

please can anyone tell me that why I am gettings these warnings ?

  • Cancel
Parents
  • theopaone
    theopaone over 11 years ago

     A technology library (techLib) is created when an ascii techfile is compiled into it. A techLib contains the layer and purpose definitions as well as via defs and other technology specific data. In addition, it may have primitive cells such as pcells used in designs. You can tell a techLib because the library directory contains a tech.db file.

    A design library uses the information from a techLib  when creating data for your design. The techLib can be attached (one techLib for the design) or it can be referenced (multiple techLibs support the design - see Virtuoso Technology Data User Guide). If it is the latter, it will contain a tech.db file, the former does not.

    Your error messages look like it is looking for some data which in the original techLib of newLib, changing the techLib makes that data invalid. Do you have any open designs when doing this? It could have stored some data (via definitions, etc.) in VM and now can't find the original references.

    Maybe this is one for customer support.

    Ted

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • theopaone
    theopaone over 11 years ago

     A technology library (techLib) is created when an ascii techfile is compiled into it. A techLib contains the layer and purpose definitions as well as via defs and other technology specific data. In addition, it may have primitive cells such as pcells used in designs. You can tell a techLib because the library directory contains a tech.db file.

    A design library uses the information from a techLib  when creating data for your design. The techLib can be attached (one techLib for the design) or it can be referenced (multiple techLibs support the design - see Virtuoso Technology Data User Guide). If it is the latter, it will contain a tech.db file, the former does not.

    Your error messages look like it is looking for some data which in the original techLib of newLib, changing the techLib makes that data invalid. Do you have any open designs when doing this? It could have stored some data (via definitions, etc.) in VM and now can't find the original references.

    Maybe this is one for customer support.

    Ted

    • 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