• 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. Global library with layout view which able to use in all...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 142
  • Views 14371
  • 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

Global library with layout view which able to use in all processes

kbhow
kbhow over 15 years ago

Hi,

Is it possible to construct a global library with layout view which able to use in all processes? If yes, do you mind providing the proper way to do that. Thanks

BTW, Noticed that each process has their own techFile and layer mapping as well, if we create the layout in particular process, the layout will not able to work on other process due to imcompatible data.

Your advice/suggestion is very appreciated.

How

  • Cancel
  • kbhow
    kbhow over 15 years ago

    Hi all,

    I think i found the solution for this. To create a library which able to use globally, we can use incremental techFile method. We can create a new library and techFile.tf that contains layers that use in the layout and load it, then save it as tech.db. The layer names and numbers in the techFile.tf cannot be the same as other techfiles. Otherwise it will lead to errors during techfile compilaton.

    Then, in the main tech file, add global library to refTechLibs eg: refTechLibs("cs1234" "globLibrary")

    For all other processes, you can now simply add "globLib" in refTechLibs and the library "glodLib" in cds.lib to ensure that users can make use of the rdt cells. This is basically the concept of incremental techfiles.

    How
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Austin CAD Guy
    Austin CAD Guy over 15 years ago

     Hi How

     You are creating an independent library which does not collide with the existing techLib definitions. You may have to map the additional layers in the ITDB library to the layers in your process techLib using a layerMap file for GDS and equivalent layers for the tools. This leaves open many potential areas of error.

    If the devices are not complex, you could represent them as pcells with the layers and possibly the rules defined from the existing techLib. Each placement would be custom for the design. Use dbWriteSkill to get the initial SKILL which you would have ot parameterize with layer names, etc.

    You can also use the mapper capability to take an original library and map it to a specific technology. Copy the original library, set up the mapping table (once per technology) and it will change the layers to the ones in the techLib. You will now have a copy of the original library in the new technology. This is probably the safest methodology.

     Ted

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • kbhow
    kbhow over 15 years ago

    Hi Ted,

    Thanks for the info. I use to create an original library and map it to a specific technology, where this techFile is created with layer defination only. Can this work too?

     

    How

    • 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