Closed xobs closed 1 year ago
The following changes need to be made, after which klayout runs successfully:
in_gds
as -rd {in_gds=/si/work/caravel-gf180-pio/deps/pdks/gf180mcuC/libs.ref/gf180mcu_fd_sc_mcu7t5v0/gds/gf180mcu_fd_sc_mcu7t5v0.gds }
, but the curly braces seem like they should be omitted/si/work/caravel-gf180-pio/deps/pdks/gf180mcuC/libs.tech/klayout/gf180mcuC.lyt
does not exist -- the path should be /si/work/caravel-gf180-pio/deps/pdks/gf180mcuC/libs.tech/klayout/tech/gf180mcu.lyt
(i.e. add a /tech/
directory and remove the C
)I think 1
is fixed. 2
is an open_pdks
issue which will need its own PR there.
Is there a standard that should be followed that gf180mcu is not adhering to? Or is it more along the lines of sky130 is the de-facto standard and I should reference that in the issue?
It doesn't actually matter: OpenLane looks for the lyt and lyp wherever the libs.tech/openlane/config.tcl
variables tell it to. That just means that variable is set incorrectly for gf180.
I think we also need to make sure that the internal reference from the lyt
to the lyp
file also conform to the final open_pdks layout, see:
https://github.com/google/globalfoundries-pdk-libs-gf180mcu_fd_pr/blob/74e4ec59b55bcf5be2f153abff8519d15ebe21fa/tech/klayout/gf180mcu.lyt#L23-L24
Resolved via #1609
Description
When
magic
crashes (e.g. https://github.com/The-OpenROAD-Project/OpenLane/issues/1587), it can be useful to try usingklayout
by settingRUN_MAGIC=0
andRUN_KLAYOUT=1
in the config file. However, OpenLane appears to generate invalid command line arguments to klayout, and fails to run.Expected Behavior
klayout should run normally
Environment report
Reproduction material
There is no reproduction material (see Relevant log output) -- there is no "Reproducible packaged" message.
Relevant log output