Why does openlane create the docker image by merging a tar file and then extracting it in the final image? Why not actually use Dockerfile includes? By not using RUN/ADD/COPY it is intentionally NOT creating layers in the image which can save download

Guys, I am running

make user_project_wrapper

and running into the following error:

[ERROR]: during executing: "openroad -exit /openLANE_flow/scripts/openroad/or_opendp.tcl |& tee >&@stdout /project/openlane/user_project_wrapper/runs/user_project_wrapper/logs/placement/29-opendp.log"
[ERROR]: Exit code: 1
[ERROR]: Last 10 lines:
child process exited abnormally

[ERROR]: Please check openroad  log file
[ERROR]: Dumping to /project/openlane/user_project_wrapper/runs/user_project_wrapper/error.log

The stack call is the following:

invalid command name "17"
    while executing
"17"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 ${cmd}"
    (procedure "set_log" line 3)
    invoked from within
"set_log ::env($index) $escaped_env_var $::env(GLB_CFG_FILE) 1"
    (procedure "save_state" line 9)
    invoked from within
"save_state"
    (procedure "flow_fail" line 6)
    invoked from within
"flow_fail"
    (procedure "try_catch" line 25)
    invoked from within
"try_catch $::env(OPENROAD_BIN) -exit $::env(SCRIPTS_DIR)/openroad/or_opendp.tcl |& tee $::env(TERMINAL_OUTPUT) [index_file $::env(opendp_log_file_tag)..."
    (procedure "detailed_placement_or" line 6)
    invoked from within
"detailed_placement_or"
    (procedure "run_routing" line 32)
    invoked from within
"run_routing"
    (procedure "run_routing_step" line 10)
    invoked from within
"[lindex $step_exe 0] [lindex $step_exe 1] "
    (procedure "run_non_interactive_mode" line 43)
    invoked from within
"run_non_interactive_mode {*}$argv"
    invoked from within
"if { [info exists flags_map(-interactive)] || [info exists flags_map(-it)] } {
	puts_info "Running interactively"
	if { [info exists arg_values(-file)..."
    (file "/openLANE_flow/flow.tcl" line 356)
make[1]: *** [Makefile:43: user_project_wrapper] Error 1
make[1]: Leaving directory '/home/mkhan33/openram_dummy/openlane'
make: *** [Makefile:70: user_project_wrapper] Error 2

I am not sure why is it taking “17" as a command which might be the issue behind this child killed error.

#655 Diode Insertion Problem at TritonRoute Issue closed by dralabeing The-OpenROAD-Project/OpenLane

Has anyone gotten decap mismatches? Why would this be?

Subcircuit summary:
Circuit 1: user_project_wrapper            |Circuit 2: user_project_wrapper
-------------------------------------------|-------------------------------------------
sky130_fd_sc_hd__tapvpwrvgnd_1 (1)         |sky130_fd_sc_hd__tapvpwrvgnd_1 (1)
sky130_fd_sc_hd__and2_1 (333)              |sky130_fd_sc_hd__and2_1 (333)
sky130_fd_sc_hd__and2_2 (38)               |sky130_fd_sc_hd__and2_2 (38)
sky130_fd_sc_hd__decap_3 (2917)            |sky130_fd_sc_hd__decap_3 (1) **Mismatch**
sky130_fd_sc_hd__clkbuf_2 (227)            |sky130_fd_sc_hd__clkbuf_2 (227)

#642 Enable the OR GUI Issue closed by donn The-OpenROAD-Project/OpenLane

#697 rewrite or_replace.tcl to use global_placement command not low-level swig Issue closed by donn The-OpenROAD-Project/OpenLane

#704 Floorplanning logs still call some steps verilog2def New issue created by donn Prompt Title. Proposal Rename the logs to something more appropriate. The-OpenROAD-Project/OpenLane

@User has left the channel

I've gotten some really odd power stripes in my design. These cause spacing errors, obviously. Any idea why this is?? I'm using the same pdn setup I had in MPW2.

Are docker images updating or something?

~/demo/openlane ((HEAD detached at mpw-3))$ make mount
cd /home/mrg/demo/openlane && \
        docker run -it --rm -v /home/mrg/demo/openlane:/openLANE_flow -v /software/PDKs:/software/PDKs -e PDK_ROOT=/software/PDKs  --user 1000:1000 efabless/openlane:mpw-3
Unable to find image 'efabless/openlane:mpw-3' locally
docker: Error response from daemon: manifest for efabless/openlane:mpw-3 not found: manifest unknown: manifest unknown.
See 'docker run --help'.
make: *** [Makefile:175: mount] Error 125
~/demo/openlane ((HEAD detached at mpw-3))$ docker pull efabless/openlane:mpw-3
Error response from daemon: manifest for efabless/openlane:mpw-3 not found: manifest unknown: manifest unknown

I am modifying openlane/scripts/tcl_commands/all.tcl and just adding a puts or puts_info output in a function. This never gets shown during my run... I'm really confused why. If I look at the file in docker (using make mount) it is there. I'm sure that the code is being executed because it is the only function named save_state and outputs "Saving Runtime Environment". Neither of these exists anywhere in openlane. @User @User?

proc save_state {args} {
    set ::env(INIT_ENV_VAR_ARRAY) [split [array names ::env] " "]
    puts_info "FOOSaving Runtime Environment"

and definitely gets called:

[INFO]: Saving Runtime Environment
invalid command name "17"
    while executing
"17"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 ${cmd}"
    (procedure "set_log" line 3)
    invoked from within
"set_log ::env($index) $escaped_env_var $::env(GLB_CFG_FILE) 1"
    (procedure "save_state" line 9)
    invoked from within
"save_state"
    (procedure "flow_fail" line 6)
    invoked from within
"flow_fail"
    (procedure "try_catch" line 25)
    invoked from within

#704 Floorplanning logs still call some steps verilog2def Issue closed by donn The-OpenROAD-Project/OpenLane

Hello all, in openlane while running our design, At the lvs check step, flow is getting stuck (not ending) , after running for some time. I am not sure what's the mistake. I checked the generated lvs log file, there weren't any mismatch but it showed two unconnected pins. Can this be a reason for this? if that's the case, what should be done for it? I have attached the lvs log file and lvs report for reference.

#710 Flow crushed at STA Multicorner - segmentation fault in the newest docker image tag: 2021.11.13_01.43.55 New issue created by KHermanUBB Description Happy to see that there is a multi-corner analysis however it fails on the SS corner Environment

Python: v3.6.9
Kernel: Linux v4.15.0-162-generic
Distribution: ubuntu 18.04
Container Engine: docker v20.10.7
OpenLane Git Version: 2021.11.13_01.43.55

Alert: Click is not installed.
---
PDK Version Verification Status: OK
---
Git Log (Last 3 Commits)

commit cbb562bd43c5c410b1b498604803c3dd88a44856
Author: Donn <me@donn.website>
Date:   Sat Nov 13 13:20:00 2021 +0200

    Assorted Usability Improvements (#709)
    
    * verilog2def -> init_floorplan
    
    Some files still retained the name of a floorplanning tool we're no longer using. It has been removed.
    
    * netlist locations
    
    Netlists generated as part of later steps were placed under `synthesis/`. They have been moved to their proper locations.
    
    * Build tweaks
    
    `make openlane` now actually builds the container. `make pull-openlane` has been added with the original functionality.
    
    The git commit has been placed in the container at `/git_version`.
    
    A custom `.bashrc` has been added.
    
    Non-standard `echo -ne` invocations replaced with `printf`.
    
    * Issues
    
    verify_versions now works without a `PDK_ROOT` set (`$openlane_root/pdks`)
    
    clarified issue template

commit 9958a53dd085020bbc468ea1ae663da57d19357f
Author: Anton Blanchard <anton@linux.ibm.com>
Date:   Sat Nov 13 15:52:06 2021 +1100

    Update documentation to show RUN_SIMPLE_CTS defaults to off (#708)

commit 9d2c4de07e93d9a8f520c3e8d6be896d6993cee6
Author: Manar <manarabdelatty@aucegypt.edu>
Date:   Fri Nov 12 15:14:54 2021 -0600

    Bring back `FP_IO_MIN_DISTANCE` (#705)
    
    * Bring back FP_IO_MIN_DISTANCE
    
    * Set io min distance default to 3

Reproduction Material https://github.com/KHermanUBB/cup-eco.git Expected behavior Clean pass Logs

======================= Slowest Corner ===================================
[ERROR]: during executing: "openroad -exit /openlane/scripts/openroad/sta_multi_corner.tcl |& tee >&@stdout /project/openlane/user_proj_example/runs/user_proj_example/logs/routing/25-spef_extraction_multi_corner_sta"
[ERROR]: Exit code: 1
[ERROR]: Last 10 lines:
child killed: segmentation violation

The-OpenROAD-Project/OpenLane

Hi! I am currently trying to port my design from MPW2 to MPW3, and get the following errors:

grafik.png

grafik.png

Any ideas?

The whole buildreport: https://raw.githubusercontent.com/thesourcerer8/caravel_stdcelllib_stdcells_project/main/build.html

Now my freshly generated standard cells are a little too big to fit between 2 tap cells on sky130. What would be the preferred solution from openlane point of view? Should I make double-sized cells? Should I place well-taps inside my cells and openlane would recognize the well-tap provided cell and spare or move the tap cell next to it? Or should I give up on larger cells on sky130 and limit my cells to lesser area? (The cell I am having problems with is a CLKBUFX2 )

Or could I tell openlane an overlap strategy that it should move/remove TAP cells when they overlap with a cell?

What is the correct usage of the variable CURRENT_STEP in the openlane Makefile? It seems like this allows you to re-run starting from a step, but it always deletes the run directory for me...

Does FINAL_TIMING_REPORT_TAG have to be defined in the config.tcl ?

What is the issue?

what is the issue?? [11/14/21 054021 PST] FAILED STDOUT: {{Project Git Info}} Repository: https://github.com/Univisiontechnocon-com/yifive_a1.git | Branch: HEAD | Commit: b65dd87fa48c67ebc0a47c27e11dafbc3685ee4e STDOUT: {{Extracting GDS}} Extracting GDS Files STDOUT: {{Project GDS Info}} user_project_wrapper: c62988274aac79b62dce3619696d5abc65fc1d12 STDOUT: {{START}} Tapeout Started STDOUT: {{Step Update}} Generating Final Layout: Step 1 of 5 STDOUT: {{Step Update}} Generating Final Layout: Step 2 of 5 STDOUT: {{Step Update}} Generating Final Layout: Step 3 of 5 STDOUT: {{Step Update}} Generating Final Layout: Step 4 of 5 STDOUT: {{Step Update}} Generating Final Layout: Step 5 of 5 STDOUT: Final GDS File caravel_000388fd.gds sha1sum: 9c43a22017067c28afdf632679ba846ab96d0150 STDOUT: {{Step Update}} Converting Final Layout from GDS to OAS STDOUT: Final OAS File caravel_000388fd.oas sha1sum: 0ddb70fac6c6954b0ebe3c4f6eb75076651f07e7 STDOUT: {{Step Update}} Executing Check 1 of 2: Klayout Metal Minimum Clear Area Density STDERR: [ WARN ] MET Density Check Result: GDS has 1 DRC violations. STDOUT: {{Step Update}} Executing Check 2 of 2: Klayout Field Oxide Mask Density STDERR: [ WARN ] FOM Density Check Result: GDS has 0 DRC violations. STDOUT: {{FINISH}} Executing Finished, the full logs can be found in u6256_manikan/design/yifive_a1/jobs/tapeout/9beeb974-e226-4beb-8411-ae9a744265ca/logs

Is there a way to resume on an OpenLANE flow after failing at a particular step, assuming the issue was confined to that step and possible to be fixed?

I'm seeing the error "package require json" while running a sample design from openlane using the command "./flow.tcl -design spm". Could someone help, please?

#683 flow.tcl no longer handles multiple simulation libraries. Issue closed by donn The-OpenROAD-Project/OpenLane

Does anyone know the recommended way to keeping the tools that openlane relies on up to date? Is there anyway I can lookup what the recommended current versions are? For example I know there have been many recent changes to magic that are important but I am not sure what else I should be looking into. Maybe the answer is whatever mpw_precheck needs?

#683 flow.tcl no longer handles multiple simulation libraries. Issue reopened by vijayank88 The-OpenROAD-Project/OpenLane