Stats

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

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

Parents

  •  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

Reply

  •  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

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.