OpenROAD to GDS Layer Conversions #3518
-
|
I've set up a few PDKs to work with OpenROAD and I have run into somewhat of a new issue with the layer mapping in the latest one I have been using. I've set up an LYT file with the layer mappings, but unfortunately the foundry is a bit unconventional in their layer mapping, so metal 1 drawing might be on layer 4/0, but metal 1 pin is on layer 40/0. The data types do not match up, and I have been having troubling getting OpenROAD to following the layer map in the tech file over the LEF stack order. It will assign pins to the type I want, but it will assign the layer number to be the order it is in the technology LEF. When I use a .map file, the layers will be assigned correctly, but no text will be present in the design. Any advice on what I might be missing? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
The lyt file is used by klayout not openroad. You might have better luck with getting help at https://www.klayout.de/forum (@stefanottili ideas?) |
Beta Was this translation helpful? Give feedback.
-
|
I would use strm2oas/gds to convert def to oas/gds. Use strm2oas -h for help. Since I don't use it, I'm not sure whether lyt allows two PIN mappings. |
Beta Was this translation helpful? Give feedback.
I would use strm2oas/gds to convert def to oas/gds. Use strm2oas -h for help.
The --lefdef-map option allows to have two M1 PIN statements.
This way you can map def PINS geometry to two different layer/datatype pairs.
Use NAME M1/PIN for the TEXT layer/datatype.
Since I don't use it, I'm not sure whether lyt allows two PIN mappings.
Also the "purpose" strings in lyt are slightly different from the lefdef-map ones.
See The-OpenROAD-Project/OpenROAD#1919