https://open-source-silicon.dev
Join Slack
```[INFO]: Back-up GDS-II streamed out. [INFO]: Incremented step index to 29. [INFO]: Running XOR on...
# openlane
t
Copy code
[INFO]: Back-up GDS-II streamed out.
[INFO]: Incremented step index to 29.
[INFO]: Running XOR on the layouts using Klayout...
First Layout: /mnt/sky130/mpw4/openlane_workspace/openlane/designs/spm/runs/RUN_2021.12.23_11.31.24/results/finishing/spm.gds
Second Layout: /mnt/sky130/mpw4/openlane_workspace/openlane/designs/spm/runs/RUN_2021.12.23_11.31.24/results/finishing/spm.klayout.gds
Design Name: spm
Output GDS will be: /mnt/sky130/mpw4/openlane_workspace/openlane/designs/spm/runs/RUN_2021.12.23_11.31.24/reports/finishing/spm.xor.gds
ERROR: Unable to determine format for file from suffix or format spec /mnt/sky130/mpw4/openlane_workspace/openlane/scripts/klayout/xor.drc
[ERROR]: during executing: "bash /mnt/sky130/mpw4/openlane_workspace/openlane/scripts/klayout/xor.sh /mnt/sky130/mpw4/openlane_workspace/openlane/designs/spm/runs/RUN_2021.12.23_11.31.24/results/finishing/spm.gds /mnt/sky130/mpw4/openlane_workspace/openlane/designs/spm/runs/RUN_2021.12.23_11.31.24/results/finishing/spm.klayout.gds spm /mnt/sky130/mpw4/openlane_workspace/openlane/designs/spm/runs/RUN_2021.12.23_11.31.24/reports/finishing/spm.xor.gds |& tee >&@stdout /mnt/sky130/mpw4/openlane_workspace/openlane/designs/spm/runs/RUN_2021.12.23_11.31.24/logs/finishing/30-xor.log"
[ERROR]: Exit code: 1
[ERROR]: Last 10 lines:
child process exited abnormally
Does that ring a bell to anyone ?
m
nope never seen it
image.png
m
Don't know if it's related, but I'm on 
mpw4
and I'm getting
Copy code
[INFO]: Streaming out GDS II...
Using Techfile: /home/user/pull-requests/openlane-efabless/pdks/sky130A/libs.tech/klayout/sky130A.lyt
Using DEF file: /openlane/designs/spm/runs/RUN_2021.12.23_15.05.51/results/routing/spm.def
Design Name: spm
Output GDS will be: /openlane/designs/spm/runs/RUN_2021.12.23_15.05.51/results/finishing/spm.klayout.gds
Extra GDSes:
/home/user/pull-requests/openlane-efabless/pdks/sky130A/libs.ref/sky130_fd_sc_hd/gds/sky130_fd_sc_hd.gds
ERROR: /openlane/scripts/klayout/def2gds.py:143: Macro not found in LEF file: sky130_fd_sc_hd__fill_1 (line=60, cell=, file=spm.def) in Layout.read
  /openlane/scripts/klayout/def2gds.py:143 (class exceptions.RuntimeError)
[INFO]: Back-up GDS-II streamed out.
[INFO]: Incremented step index to 29.
[INFO]: Running XOR on the layouts using Klayout...
[WARNING]: /openlane/designs/spm/runs/RUN_2021.12.23_15.05.51/results/finishing/spm.klayout.gds wasn't found. Skipping GDS XOR.
Looks like a LEF problem. SOURCES
Copy code
openlane 667b8f89dc45ee0f487acc824a33fb9cb2815c6e
skywater-pdk c094b6e83a4f9298e47f696ec5a7fd53535ec5eb
open_pdks 476f7428f7f686de51a5164c702629a9b9f2da46
magic 8.3.241
netgen 1.5.213
@User Are you getting a valid 
designs/spm/runs/RUN_2021.12.23_11.31.24/results/finishing/spm.klayout.gds
?
t
@User I'm using the 
mpw-4
tag because the 
3a
segfaults in spdlog for me. (known bug, fixed in later openroad, but newer openroad don't work with openlane 
3a
).
m
there's never been an announcement about what tags to use for mpw4, so I'm sticking with what is working here and works for the precheck and tapeout jobs
t
Sure ... but given that doesn't work for me I thought I'd try something else ...
It's that or nothing anyway.
@User Yes, I'm getting a 
spm.klayout.gds
generated. I have the same skywater-pdk and open_pdks hash. openlane tag is different though.
m
Sorry about that. 
openlane
is basically 
96a630e29c60f47d87c63642e2af39c19a48cdb7
with a few changes I'm creating PR's for.
If you don't need the klayout XOR GDS results, you could try setting 
KLAYOUT_XOR_GDS
to 
0
. I believe the default is 
1
. Openlane should still do 
KLAYOUT_XOR_XML
.
t
TBH I'm using that to see if my install is functional ... the fact it doesn't complete tells me something is wrong.
b
@User what tags work for you?
m
The ones I posted above in this thread
Open in Slack
PreviousNext
Powered by

What is Linen?

Linen is a search-engine friendly community platform. We offer integrations with existing Slack/Discord communities and make those conversations Google-searchable.

Powered by