• 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. How to fix layers after changing layer numbers in the technology...

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 126
  • Views 17067
  • 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

How to fix layers after changing layer numbers in the technology file

Sheppy
Sheppy over 9 years ago

Hi,

This is what I have done:
I have updated layer number information in the technology file in the sections TechnologyFile->layerDefinitions->techLayers and TechnologyFile->layerRules->functions. The reason for changing the numbers is that in the original technology file, the layer numbers did not match the actual gds2 numbers. So exporting a layout to gds2 resulted in a not compatible database.The second reason is that I had to change layers because Virtuoso crashed due to inconsistent layer name-number mapping in the technology file, see post Home > Community > Forums > Custom IC Design > Virtuoso crashes when trying to instantiate a stacked Via (community.cadence.com/.../34766).

But then I ran into a problem: after the recompiling and attaching the new technology file, when I open an existing layout layers have changed color/fill or are completely invisible. It looks like Virtuoso does not store the layer purpose pair (lpp) as MET1:drawing, but rather as the assigned numbers, like 19:0. When you reassign the numbers to a different lpp name it will get the display information of that new name as specified in the display.drf file. If a layer had a number like 22:0, and this number is not assigned to any layer in the new technology file, it is completely invisible.

What I see is that all shapes in a layout have the layerNumber stored, and only a few have the layerName stored. When I do the following:
foreach( shape cv->shapes printf( "%L - %L\n" shape->layerName shape->layerNumber ) )
I'll get the following output (example after updating the technology file):
nil - 107
nil - 55
nil - 107
"METTOP" - 31
"VIAT" - 30
"METTOP" - 31
This looks to me that Virtuoso stores only layer number information (all shapes have the number, not all have the name) and when asking for the layer name, it simply matches the number to the name in the technology file. If a layer number is not associated to a name, it reports nil. So the name is not stored.

My questions:
1. How do I fix the layout after changing the layer numbers in the technology file?
2. Is it possible to configure Virtuoso so that is stores the layerName instead of the layerNumber?

If I have to roll-back all changes (giving each layer it's original, wrong, layer number again) I might end-up in a situation that I am unable to instantiate a stacked via, since Virtuoso will crash. How can I disable the stacked via option?

Thanks in advance.

With kind regards,

Sjoerd

  • Cancel
Parents
  • Sheppy
    Sheppy over 9 years ago

    Hi Andrew,

    Thanks for the detailed reply.

    I ended up putting the original layer numbers in the technology file. The only change I made were the numbers in the functions part. There were duplicate numbers in there, and that was what caused the crashes.

    For the next PDK, I'll make sure I generate the technology file with the proper numbers (that layer numbers match the GDS2 layer numbers). I got this PDK from someone else (who "had to leave" the company) and they asked me to clean up the mess he left behind. Unfortunately, this mess is something which will have to be there...


    Kind regards,

    Sjoerd

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Sheppy
    Sheppy over 9 years ago

    Hi Andrew,

    Thanks for the detailed reply.

    I ended up putting the original layer numbers in the technology file. The only change I made were the numbers in the functions part. There were duplicate numbers in there, and that was what caused the crashes.

    For the next PDK, I'll make sure I generate the technology file with the proper numbers (that layer numbers match the GDS2 layer numbers). I got this PDK from someone else (who "had to leave" the company) and they asked me to clean up the mess he left behind. Unfortunately, this mess is something which will have to be there...


    Kind regards,

    Sjoerd

    • 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