hi, is this error log means a crash ? [ERROR]: during executing openroad script /openlane/scripts/openroad/droute.tcl [ERROR]: Exit code: 1 [ERROR]: Last 10 lines: child killed: kill signal [ERROR]: Flow failed. this is the repo: https://github.com/mbaykenar/first_asic i have difficulties in global routing phase, i tried different config options, absolute or relative FP_SIZING, different FP_CORE_UTIL and PL_TARGET_DENSITY values. I always got congestion error. Then i added set ::env(GLB_RT_ALLOW_CONGESTION) 1 but this time again in global routing i got errors that i have written above any suggestion is appreciated: config.tcl parameters: set ::env(DESIGN_IS_CORE) 0 set ::env(CLOCK_PORT) "wb_clk_i" set ::env(CLOCK_NET) "pulpino_top_wrapper.clk" set ::env(CLOCK_PERIOD) "200" set ::env(PL_RESIZER_MAX_SLEW_MARGIN) 40 set ::env(PL_RESIZER_MAX_CAP_MARGIN) 40 set ::env(GLB_RESIZER_MAX_SLEW_MARGIN) 40 set ::env(FP_SIZING) absolute set ::env(DIE_AREA) "0 0 2500 2500" set ::env(FP_PIN_ORDER_CFG) $script_dir/pin_order.cfg set ::env(SYNTH_STRATEGY) "AREA 1" set ::env(PL_BASIC_PLACEMENT) 0 set ::env(PL_TARGET_DENSITY) 0.3 set ::env(FP_CORE_UTIL) {30} set ::env(PL_MACRO_CHANNEL) {30 30} set ::env(PL_MACRO_HALO) {10 10} set ::env(CELL_PAD) {2} set ::env(GLB_RESIZER_HOLD_MAX_BUFFER_PERCENT) {60} set ::env(ROUTING_CORES) {6} set ::env(GLB_RT_OVERFLOW_ITERS) {100} set ::env(GLB_RT_ALLOW_CONGESTION) 1 macro.cfg: pulpino_top.core_region_i.data_mem.open_ram_2k 1000 300 N pulpino_top.core_region_i.instr_mem.sp_ram_wrap_i.open_ram_2k 1000 1500 N

Hi, are the symbols in xschem "cap_mim_m3_2" and "cap_mim_m3_1" (installed from OpenPDK from the sky130_fd_pr library) the same as the ones shown from https://skywater-pdk.readthedocs.io/en/main/rules/device-details.html#details? It does not show the capacitance like as in the online document and does not show the parasitic resistances or capacitance value as mentioned (in the spice or xschem). Is there a way to show that in xschem or these are not the same devices?

I am getting an error in the openlane flow like:

[ERROR GRT-0076] Net CONTROL_LOGIC.SRAM12_WRAPPER.ram_din0\[0\] not properly covered.
Error: resizer_routing_timing.tcl, 67 GRT-0076
[ERROR]: during executing openroad script /openlane/scripts/openroad/resizer_routing_timing.tcl
[ERROR]: Exit code: 1
[ERROR]: Last 10 lines:
child process exited abnormally

What does this “not properly covered” mean?

Hi, I'm trying to use OpenLane with the following module of my project: https://github.com/theatomb/Elpis-Light-MPW3/blob/main/verilog/rtl/elpis/regfile.v with the following config: https://github.com/theatomb/Elpis-Light-MPW3/blob/main/openlane/regfile/config.tcl The workflow stops at step 15 with the following messages and then it raises an error:

[INFO GRT-0101] Running extra iterations to remove overflow.

[INFO GRT-0103] Extra Run for hard benchmark.

How can I reduce congestion and overflow with that very simple module (even having a big die and low density)? What is wrong in my Verilog code or config file?? Thank you!

How can I integrate sky130 with cadence tools

@Harald Pretl I just pulled your latest container and it seems to use the above new hash. But, my original issue is somehow still not addressed. Here's a test case:

* old binned models
*.lib /foss/pdks/sky130A/libs.tech/ngspice/sky130.lib.spice tt
* new continuous models
.lib /foss/pdks/sky130A/libs.tech/combined/sky130.lib.spice tt

.param mc_mm_switch=0
.param lx=0.15 wx=162.5 nfx=40 idx=0.5m
.save @m.xm1a.msky130_fd_pr__nfet_01v8_lvt

XM1a d g s 0 sky130_fd_pr__nfet_01v8_lvt L={lx} W={wx} nf={nfx} ad='int((nf+1)/2) * W/nf * 0.29' as='int((nf+2)/2) * W/nf * 0.29' pd='2*int((nf+1)/2) * (W/nf + 0.29)'
+ ps='2*int((nf+2)/2) * (W/nf + 0.29)' nrd='0.29 / W' nrs='0.29 / W' sa=0 sb=0 sd=0 mult=1 m=1
XM1b d g s 0 sky130_fd_pr__nfet_01v8_lvt L={lx} W={wx} nf={nfx} ad='int((nf+1)/2) * W/nf * 0.29' as='int((nf+2)/2) * W/nf * 0.29' pd='2*int((nf+1)/2) * (W/nf + 0.29)'
+ ps='2*int((nf+2)/2) * (W/nf + 0.29)' nrd='0.29 / W' nrs='0.29 / W' sa=0 sb=0 sd=0 mult=1 m=1
vg  g  0  1
vd  d  0  1
is  s  0  {2*idx}

.control
  op
  *show
  print @m.xm1a.msky130_fd_pr__nfet_01v8_lvt[gm]
  print @m.xm1a.msky130_fd_pr__nfet_01v8_lvt[cgg]
.endc
.end

Hello, I'm just testing the LVS with a circuit that I know has a correct LVS. If I send this message, you can imagine the LVS didn't pass. When I check the log, I have no problem with vias and nets. The final result says: 'LVS result: Final result: Circuits match uniquely.' In checking ext.log, I saw this: _Reading "sky130_ef_sc_hd__decap_12$1"._ _Error while reading cell "$$$CONTEXT_INFO$$$" (byte position 1718): Cell "sky130_ef_sc_hd__decap_12$1" was already defined in this file._ _Error while reading cell "$$$CONTEXT_INFO$$$" (byte position 1718): Ignoring duplicate definition_ _Reading "sky130_fd_sc_hd__decap_8$1"._ _Error while reading cell "$$$CONTEXT_INFO$$$" (byte position 5514): Cell "sky130_fd_sc_hd__decap_8$1" was already defined in this file._ _Error while reading cell "$$$CONTEXT_INFO$$$" (byte position 5514): Ignoring duplicate definition_ _Reading "sky130_fd_sc_hd__decap_3$1"._ _Error while reading cell "$$$CONTEXT_INFO$$$" (byte position 9054): Cell "sky130_fd_sc_hd__decap_3$1" was already defined in this file._ _Error while reading cell "$$$CONTEXT_INFO$$$" (byte position 9054): Ignoring duplicate definition_ _Reading "sky130_fd_sc_hd__fill_1$1"._ _Error while reading cell "$$$CONTEXT_INFO$$$" (byte position 11730): Cell "sky130_fd_sc_hd__fill_1$1" was already defined in this file._ _Error while reading cell "$$$CONTEXT_INFO$$$" (byte position 11730): Ignoring duplicate definition_ _Reading "sky130_fd_sc_hd__tapvpwrvgnd_1$1"._ _Error while reading cell "$$$CONTEXT_INFO$$$" (byte position 13046): Cell "sky130_fd_sc_hd__tapvpwrvgnd_1$1" was already defined in this file._ _Error while reading cell "$$$CONTEXT_INFO$$$" (byte position 13046): Ignoring duplicate definition_ _Reading "sky130_fd_sc_hd__decap_6$1"._ _Error while reading cell "$$$CONTEXT_INFO$$$" (byte position 14724): Cell "sky130_fd_sc_hd__decap_6$1" was already defined in this file._ _Error while reading cell "$$$CONTEXT_INFO$$$" (byte position 14724): Ignoring duplicate definition_ _Reading "sky130_fd_sc_hd__fill_2$1"._ _Error while reading cell "$$$CONTEXT_INFO$$$" (byte position 17880): Cell "sky130_fd_sc_hd__fill_2$1" was already defined in this file._ _Error while reading cell "$$$CONTEXT_INFO$$$" (byte position 17880): Ignoring duplicate definition_ _Reading "sky130_fd_sc_hd__clkbuf_1$1"._ _Error while reading cell "$$$CONTEXT_INFO$$$" (byte position 19320): Cell "sky130_fd_sc_hd__clkbuf_1$1" was already defined in this file._ _Error while reading cell "$$$CONTEXT_INFO$$$" (byte position 19320): Ignoring duplicate definition_ _Reading "sky130_fd_sc_hd__dfxtp_1$1"._ _Error while reading cell "$$$CONTEXT_INFO$$$" (byte position 23140): Cell "sky130_fd_sc_hd__dfxtp_1$1" was already defined in this file._ _Error while reading cell "$$$CONTEXT_INFO$$$" (byte position 23140): Ignoring duplicate definition_ _Reading "sky130_fd_sc_hd__decap_4$1"._ _Error while reading cell "$$$CONTEXT_INFO$$$" (byte position 35272): Cell "sky130_fd_sc_hd__decap_4$1" was already defined in this file._ _Error while reading cell "$$$CONTEXT_INFO$$$" (byte position 35272): Ignoring duplicate definition_ _Reading "sky130_fd_sc_hd__buf_2$1"._ _Error while reading cell "$$$CONTEXT_INFO$$$" (byte position 38074): Cell "sky130_fd_sc_hd__buf_2$1" was already defined in this file._ _Error while reading cell "$$$CONTEXT_INFO$$$" (byte position 38074): Ignoring duplicate definition_ _Reading "vias_gen"._ _Error while reading cell "$$$CONTEXT_INFO$$$" (byte position 42562): Cell "vias_gen" was already defined in this file._ _Error while reading cell "$$$CONTEXT_INFO$$$" (byte position 42562): Ignoring duplicate definition_ Reading "Dff$1". _Error while reading cell "$$$CONTEXT_INFO$$$" (byte position 42988): Cell "Dff$1" was already defined in this file._ _Error while reading cell "$$$CONTEXT_INFO$$$" (byte position 42988): Ignoring duplicate definition_ _Reading "user_analog_project_wrapper"._ _Processing sky130_ef_sc_hd__decap_12$1_ Processing Dff$1 Do you think this is the cause of the LVS failing in the percheck process?

@Matt Venn @Tim Edwards I'm having some issues getting my OpenLane installation to work. Certain parts of the flow seem to run fine as root, but not as a normal user. I'm not quite sure what's going on so I've compiled a list of "observations" below. I'm hoping someone might be able to identify what I'm doing wrong and help me out. Before listing them out, I saw the warnings in the documentation about making Docker available without root and followed those closely, so I'm pretty sure it's not that. I've tried uninstalling, reinstalling, etc., etc., but still no luck and now I'm out of ideas. 1. "docker run hello-world" runs fine when I'm not root. 2. When I run "make" in the OpenLane directory. I get: Version cd1748bb197f9b7af62a54507de6624e30363943 not found locally, attempting to download… [Errno 13] Permission denied: '/opt/pdk/share/pdk/volare' 'Permission denied: '/opt/pdk/share/pdk/volare'. 3. If I run sudo make, it runs just fine though. I'm able to get all the way to where I see GDS in Klayout or Magic. 4. If I run "make mount" then ./flow.tcl -design gcd I get the following error: [ERROR]: open_pdks 30656fcd54fb8ba48caf1701f5b01b89f3f0c4fc magic 038f02d2b2802251dd9a346e0c94489026003d56 The version of open_pdks used in building the PDK does not match the version OpenLane was tested on (installed: 30656fcd54fb8ba48caf1701f5b01b89f3f0c4fc, tested: cd1748bb197f9b7af62a54507de6624e30363943) This may introduce some issues. You may want to re-install the PDK by invoking

make pdk

. The version of magic used in building the PDK does not match the version OpenLane was tested on (installed: 038f02d2b2802251dd9a346e0c94489026003d56, tested: 0afe4d87d4aacfbbb2659129a1858a22d216a920) This may introduce some issues. You may want to re-install the PDK by invoking

make pdk

. [ERROR]: Please update your environment. OpenLane will now quit. 5. If I run the above root I don't get that error. 6. I noticed that I have PDK's installed at both /usr/local/share/pdk as well as /opt/pdk/share/pdk. I'm not sure why and I'm wondering if this might have something to do with the different version errors? 7. I tried a fresh install of open_pdk from the OCD website this morning. That didn't seem to fix it.

@Stefan Schippers I know one can create a symbol from a schematic, but can one also automatically create a symbol from a SPICE netlist?

error_dc_reram.PNG