def to gds conversion

[titan73]

I want to convert a def from openroad to a gds? I'm using a proprietary PDK.
I found the scripts that seem to do that:

./flow/util/def2stream.py
./flow/scripts/klayout.tcl

The tcl script has:

exec klayout -zz -rd design_name=$::env(DESIGN_NAME) \
  -rd in_def=$::env(RESULTS_DIR)/6_final.def \
  -rd in_files="$::env(GDSOAS_FILES) $::env(WRAPPED_GDSOAS)" \
  -rd config_file=$fill_config \
  -rd seal_file=$seal_gds \
  -rd out_file=$::env(RESULTS_DIR)/6_final.$::env(STREAM_SYSTEM_EXT) \
  -rd tech_file=$::env(OBJECTS_DIR)/klayout.lyt \
  -rm $::env(UTILS_DIR)/def2stream.py

It requires a klayout.lyt files not present in orfs. I don't know how to make such a file for my PDK. Isn't a tech life sufficient?

[maliberty]

You need to map info GDS layer:datatype. See https://openroad-flow-scripts.readthedocs.io/en/latest/contrib/PlatformBringUp.html#klayout

[titan73]

I read the doc. This section:

In the LEF+Macro Files section, you add the LEF files by clicking the + button on the right hand side of the box.
Note: Only add your original merged LEF file. Make sure it includes the full path to the LEF file.

That is the original merged LEF. What does it contains?
Also in this sections:

In the Production section, scroll down and add the layer map file by hitting the Load File button.
Note: Make sure it includes the full path.

What is this layer map? where does it comes from?

[titan73]

If flow/platforms/ihp-sg13g2/sg13g2.map a valid one?

[titan73]

Ah no. It's a layer map for innovus.

[maliberty]

https://github.com/The-OpenROAD-Project/OpenROAD-flow-scripts/blob/master/flow/platforms/ihp-sg13g2/sg13g2.lyt

[maliberty]

You can see examples in the various platforms, eg https://github.com/The-OpenROAD-Project/OpenROAD-flow-scripts/blob/master/flow/platforms/sky130hd/sky130hd.lyt

[titan73]

I managed to generate a gds. I checked it with Calibre and I didn't see anything wrong.
I follow the doc with some change based on the doc with some difference:
Step 6: I didn't use a .lyp file
Step 8: Add techno lef and all lefs for libraries insteand of "merged lef"
Step 9: I added the my techno's layer map I use to stream out gds from Innovus. It has the same format as flow/platforms/ihp-sg13g2/sg13g2.map. I guess this is thisformat use for Innovus & Virtuoso.

Regarding the call to klayout, I had this error:

ERROR: def2stream.py:14: NameError: name 'layer_map' is not defined
  def2stream.py:14 (class NameError)
ERROR: /sw/freetools/klayout/0.29.8/rh80_64/bin/macros/xsection.lym:1033: NoMethodError: undefined method `menu' for nil:NilClass
  /sw/freetools/klayout/0.29.8/rh80_64/bin/macros/xsection.lym:1033:in `initialize'
  /sw/freetools/klayout/0.29.8/rh80_64/bin/macros/xsection.lym:1172:in `new'
  /sw/freetools/klayout/0.29.8/rh80_64/bin/macros/xsection.lym:1172:in `<main>' (class NoMethodError)

So I added -rd layer_map="../lefs_libs/streamOut.map" to point to my layer map (Is the Step 9 useful?)

klayout -zz \
  -rd design_name=top_module \
  -rd in_def=dbs/routing.def \
  -rd in_files="lib1_gds lib2_gds lib3_gds" \
  -rd config_file="" \
  -rd seal_file="" \
  -rd out_file=dbs/routing.gds \
  -rd tech_file="techno.lyt" \
  -rd layer_map="../lefs_libs/streamOut.map" \
  -rm def2stream.py

Then it worked although there are some warnings and errors:

Warning: No mapping for layer 'metal1', purpose 'LEFOBS' - layer is ignored (line=298, cell=, file=routing.def)
Warning: No mapping for layer 'metal2', purpose 'LEFOBS' - layer is ignored (line=298, cell=, file=routing.def)
Warning: No mapping for layer 'v1', purpose 'LEFOBS' - layer is ignored (line=298, cell=, file=routing.def)
Warning: No mapping for layer 'v1', purpose 'LEFLABEL' - layer is ignored (line=303, cell=, file=routing.def)
        ../LIBRARIES/lib1.gds
        ../LIBRARIES/lib2.gds
        ../LIBRARIES/lib3.gds
[INFO] All LEF cells have matching GDS/OAS cells
[INFO] No orphan cells in the final layout
ERROR: /sw/freetools/klayout/0.29.8/rh80_64/bin/macros/xsection.lym:1033: NoMethodError: undefined method `menu' for nil:NilClass
  /sw/freetools/klayout/0.29.8/rh80_64/bin/macros/xsection.lym:1033:in `initialize'
  /sw/freetools/klayout/0.29.8/rh80_64/bin/macros/xsection.lym:1172:in `new'
  /sw/freetools/klayout/0.29.8/rh80_64/bin/macros/xsection.lym:1172:in `<main>' (class NoMethodError)

[rovinski]

For what it's worth, I think there's a KLayout script or plugin floating around that can translate GDS mappings for Virtuoso to KLayout. It is also rather straightforward (although potentially tedious) to manually translate as the map files are in plain text.

[titan73]

I use klayout only for generating a gds and calibre for the rest but I note for when I'll use klayout more often thx