Stats

  • Locked Locked
  • Replies 2
  • Subscribers 126
  • Views 14579
  • 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

Changing layer numbers in a design library

Lynks

We created a library using a custom technology file where different layers were assigned arbitrary layer numbers in IC6.1.5-64b.500.8. Now we want to take that same library and use it with a much larger technology file which will add additional layers and include all layers previously defined in the custom technology file we had. Unfortunately, there are some conflicts in the layer numbers.

At this point, we've edited the larger technology file so that all the layers from the custom technology file have been assigned to available layer numbers. Now because the layer numbers are different, the polygons in the design library do not show (only the polygons whose layers just so happened to have the same layer number as it originally had actually showed correctly).

One idea we've tried is to stream out the design library to a GDS file and create a layer mapping. I would take take the layer name that was obtained from the custom tech file and map it to a stream layer number. The stream layer number I'd choose would be the same number as this layer would appear in the larger tech file. Then I would stream-in the GDS file back into Virtuoso with the larger tech file attached. Even in this manner, I got a similar result as mentioned previously. As a test, I streamed in the GDS file again with the custom tech file attached instead and everything looked good. It seems like the layer mapping didn't affect the layer numbers. Perhaps, I missed an important step here.

In the end, I simply want this design library which was originally made using a custom tech library, to work with this larger manually merged tech file where the same layers from the custom tech library are now using different layer numbers. Does anyone know of a simple way to do this?

Any help is appreciated. 

Parents
  • Lynks

    Thank you for the follow up, Quek.

    Yes, actually we managed to get it to work through this method. In our first attempt, the newly merged techfile was created such that we assigned layer names to layer numbers that were first available in the large list (e.g. say layer numbers 1, 3, 4, 5, 7 are taken so we started with 2, 6 and so on). In our second attempt, we simply moved the layers to the very end of the list so that they're all together (e.g. last defined layer is 100, so we started integrating the new layers from 101 and on). I guess this helped to minimize any mistakes in the layer mapping as the new layers are adjacent to each other numerically. The procedure with exporting the gds, mapping the gds numbers, and importing the gds remained essentially the same.

    So yep, it does in fact work. 

Reply
  • Lynks

    Thank you for the follow up, Quek.

    Yes, actually we managed to get it to work through this method. In our first attempt, the newly merged techfile was created such that we assigned layer names to layer numbers that were first available in the large list (e.g. say layer numbers 1, 3, 4, 5, 7 are taken so we started with 2, 6 and so on). In our second attempt, we simply moved the layers to the very end of the list so that they're all together (e.g. last defined layer is 100, so we started integrating the new layers from 101 and on). I guess this helped to minimize any mistakes in the layer mapping as the new layers are adjacent to each other numerically. The procedure with exporting the gds, mapping the gds numbers, and importing the gds remained essentially the same.

    So yep, it does in fact work. 

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.