and more to the point of the question is there any place where openlane would document such reasoning ?

I am specifically looking for a list around the lines of: these std_cells from this set (ex. hd in this case) have been used by design x and are known to be "good"

@User Here is the def file obtained at the end of routing.

so I'm a little late to the party and just setting up OpenLANE, was able to get the example

spm

built, should we still be using rc2 or is there a better version to be running with yet?

#27 Cannot install via docker method on branch

develop

Issue opened by frznchckn I'm using Ubuntu (see below) and this system successful build

rc2

and ran the example design

spm

Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.1 LTS
Release:	20.04
Codename:	focal

The docker build fails on

vlogtoverilog

~/git/openlane-develop/docker_build$ make build-vlogtoverilog
mkdir -p logs/docker
export DOCKER_BUILDKIT=1;  docker build --rm  -t vlogtoverilog docker/vlogtoverilog | tee logs/docker/vlogtoverilog.build.txt
[+] Building 15.3s (5/16)                                                                                                                                                       
 => [internal] load build definition from Dockerfile                                                                                                                       0.0s
 => => transferring dockerfile: 38B                                                                                                                                        0.0s
 => [internal] load .dockerignore                                                                                                                                          0.0s
 => => transferring context: 2B                                                                                                                                            0.0s
 => [internal] load metadata for <http://docker.io/library/centos:centos6|docker.io/library/centos:centos6>                                                                                                          0.0s
 => CACHED [1/13] FROM <http://docker.io/library/centos:centos6|docker.io/library/centos:centos6>                                                                                                                    0.0s
 => ERROR [2/13] RUN yum -y install centos-release-scl &&     yum -y install devtoolset-6 devtoolset-6-libatomic-devel                                                    15.2s
------                                                                                                                                                                          
 > [2/13] RUN yum -y install centos-release-scl &&     yum -y install devtoolset-6 devtoolset-6-libatomic-devel:                                                                
#5 0.415 Loaded plugins: fastestmirror, ovl                                                                                                                                     
#5 0.622 Setting up Install Process                                                                                                                                             
#5 12.38 Resolving Dependencies                                                                                                                                                 
#5 12.38 --> Running transaction check                                                                                                                                          
#5 12.38 ---> Package centos-release-scl.noarch 10:7-4.el6.centos will be installed
#5 12.38 --> Processing Dependency: centos-release-scl-rh for package: 10:centos-release-scl-7-4.el6.centos.noarch
#5 12.48 --> Running transaction check
#5 12.48 ---> Package centos-release-scl-rh.noarch 0:2-4.el6.centos will be installed
#5 12.49 --> Finished Dependency Resolution
#5 12.50 
#5 12.50 Dependencies Resolved
#5 12.50 
#5 12.50 ================================================================================
#5 12.50  Package                   Arch       Version                  Repository  Size
#5 12.50 ================================================================================
#5 12.50 Installing:
#5 12.50  centos-release-scl        noarch     10:7-4.el6.centos        extras      12 k
#5 12.50 Installing for dependencies:
#5 12.50  centos-release-scl-rh     noarch     2-4.el6.centos           extras      12 k
#5 12.50 
#5 12.50 Transaction Summary
#5 12.50 ================================================================================
#5 12.50 Install       2 Package(s)
#5 12.50 
#5 12.50 Total download size: 24 k
#5 12.50 Installed size: 39 k
#5 12.50 Downloading Packages:
#5 12.78 --------------------------------------------------------------------------------
#5 12.78 Total                                            85 kB/s |  24 kB     00:00     
#5 12.78 warning: rpmts_HdrFromFdno: Header V3 RSA/SHA1 Signature, key ID c105b9de: NOKEY
#5 12.79 Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6
#5 12.81 Importing GPG key 0xC105B9DE:
#5 12.81  Userid : CentOS-6 Key (CentOS 6 Official Signing Key) <centos-6-key@centos.org>
#5 12.81  Package: centos-release-6-10.el6.centos.12.3.x86_64 (@CentOS/6.10)
#5 12.81  From   : /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6
#5 12.83 Running rpm_check_debug
#5 12.83 Running Transaction Test
#5 12.84 Transaction Test Succeeded
#5 12.84 Running Transaction
  Installing : centos-release-scl-rh-2-4.el6.centos.noarch                  1/2 
  Installing : 10:centos-release-scl-7-4.el6.centos.noarch                  2/2 
  Verifying  : centos-release-scl-rh-2-4.el6.centos.noarch                  1/2 
  Verifying  : 10:centos-release-scl-7-4.el6.centos.noarch                  2/2 
#5 13.05 
#5 13.05 Installed:
#5 13.05   centos-release-scl.noarch 10:7-4.el6.centos                                   
#5 13.05 
#5 13.05 Dependency Installed:
#5 13.05   centos-release-scl-rh.noarch 0:2-4.el6.centos                                 
#5 13.05 
#5 13.05 Complete!
#5 13.19 Loaded plugins: fastestmirror, ovl
#5 13.19 Setting up Install Process
#5 13.26 Determining fastest mirrors
#5 13.77  * base: <http://centos.host-engine.com|centos.host-engine.com>
#5 13.77  * centos-sclo-rh: <http://mirror.steadfastnet.com|mirror.steadfastnet.com>
#5 13.77  * centos-sclo-sclo: <http://repos-tx.psychz.net|repos-tx.psychz.net>
#5 13.77  * extras: <http://repo1.dal.innoscale.net|repo1.dal.innoscale.net>
#5 13.77  * updates: <http://centos.host-engine.com|centos.host-engine.com>
#5 14.97 No package devtoolset-6 available.
#5 15.08 No package devtoolset-6-libatomic-devel available.
#5 15.14 Error: Nothing to do
------
failed to solve with frontend dockerfile.v0: failed to build LLB: executor failed running [/bin/sh -c yum -y install centos-release-scl &&     yum -y install devtoolset-6 devtoolset-6-libatomic-devel]: runc did not terminate sucessfully

Seems odd as I don't think the dockerfile for this tool has changed between

rc2

and the HEAD of

develop

, but I'm just getting used to this repo, so I could be mistaken. efabless/openlane

@User has left the channel

Can someone just explain me the information present in the tracks.info file.I'm kind of confused with the values and the X Y notations?

I'm trying to plug in my custom inverter cell (inv_1) into picorv32a design and run the openlane flow..the runs are OK but placement of my cell isn't legalized (attached is a section of the post-routing layout & the inverter cell highlighted is my cell)..can anybody help?

I am getting errors in placement stage using replace in the openlane flow. Attaching the errors:

[INFO] FillerInit: FillerCellArea = -nan

[INFO] FillerInit: FillerCellSize = (-nan, -nan) [ERROR]: during executing: "replace < /openLANE_flow/scripts//replace_gp.tcl |& tee >&@stdout /openLANE_flow/designs/AMUX2_3V_top/runs/19-08_05-37//logs/placement/replace.log" [ERROR]: Last 10 lines: child killed: segmentation violation After debugging found out that the following line in replace_gp.tcl is causing the error: rep place_cell_nesterov_place. can someone help?

@User And the cell matches the spec for that standard library ? And the LEF is correct ?

I'm getting the following error during SPICE extraction using Magic for the Aardonyx SoC: aardonyx: 3 fatal errors 1952018 warnings Total of 3 fatal errors. Any idea how to resolve this?

@User: Use "feedback why" in the layout to check what the errors are (@User: this probably should be in the extraction script. Since it is run in batch, errors arising from extraction cannot be queried and so it would be the responsibility of the script to run a "feedback why" to print the reason for any errors that occurred during extraction). In this case "fatal errors" are probably not fatal. There are known issues with some of the cells in the libraries disagreeing about the definition of pins and obstructions, especially around the power rails. This causes obstruction layers and pin layers to overlap when the cells are abutted, which makes all the EDA tools unhappy. That one is a false positive error. But you should check and make sure that the errors being reported can be ignored.

@User: The feedback file is saved (with

feedback save

) alongside the magic logs, so you could have a look at the fatal errors there. @User: This is basically the same as

feedback why

, right?

@User: Right. Sorry, I didn't know that you were running "feedback save".

@User I was using rc1 branch of Openlane till now. Figured that you've added the "feedback save" command in the extraction script of rc2. Will look into it. Thanks!!

Is there a way to run just specific intermediate steps like routing/magic by providing the required input files rather than running all the way from synthesis each time? Would help a lot in saving time.

Yes, you can use the interactive mode to "tune-in" on an existing run and run commands on the latest files available. Put the following in a file:

package require openlane
prep -design <design_name> -tag <run_tag_name>; # this is the name of the directory containing the run files under designs/<design_name>/runs/<run_tag_name>

# if you want to change the DEF to be used by the next commands, then use:
# set_def /path/to/def/file

# your commands here:
run_magic

Then execute it using

./flow.tcl -interactive -file /path/to/above/script

#28 error during placement stage Issue opened by praharshapm Hi, I am getting error on running run_placement. Replace is causing the issue.

[INFO] 80pCellArea = -nan [INFO] FillerInit: TotalFillerArea = 821.911865 [INFO] FillerInit: NumFillerCells = -2147483648 [INFO] FillerInit: FillerCellArea = -nan [INFO] FillerInit: FillerCellSize = (-nan, -nan) [ERROR]: during executing: "replace < /openLANE_flow/scripts//replace_gp.tcl |& tee >&@stdout /openLANE_flow/designs/AMUX2_3V_top/runs/19-08_07-19//logs/placement/replace.log" [ERROR]: Last 10 lines: child killed: segmentation violation

After debugging, I understood that

rep place_cell_nesterov_place

is causing error which is present in replace_gp.tcl Can someone please help? efabless/openlane

I am trying to update some tools in openlane using the steps given in the GitHub page. But I am getting the following errors. How to resolve this?

I'm encountering spacing violations during the DRC check. Do I need to manually re-route to get rid of these violations?

#15 Add license scan report and status Pull request closed by ax3ghazy efabless/openlane

Getting the layout like this. Macro is not placed correctly. There are many overlaps. Could someone help?

I am encountering a mismatch of nets during the LVS check. The no. of device instances match. When I checked the LVS report, the missing nets in the schematic are those involving VGND and VPWR. Any idea what could be causing this error? Circuit 1 contains 716828 devices, Circuit 2 contains 716828 devices. Circuit 1 contains 184338 nets, Circuit 2 contains 183262 nets. * MISMATCH **

Not sure if this has been asked here before..but using fake antenna diodes in openlane does have an area tradeoff (since we are including fake antennas in every input cell)..which could become a de-limiting factor in high instance count designs. Will we be going forward with this approach or do we plan on something else? Pl. do correct if my observation is incorrect.

AFAIK that's the strategy for now. And yes, you're wasting area.

While implementing run_magic_drc, my macro is getting scaled. Till routing it is correct size. How to avoid this scaling?

I was able to implement the first multi-height mixed signal run. I am attaching the layout for your reference. AMUX2_3V is the analog IP on which I performed the flow. I would like to thank the entire Openlane team for your constant support wherever required. I would also like to thank @User for mentoring me and encouraging me to achieve this.

@User From your screenshot it looks like we need a mode in magic which strips off the initial prefix to make that image easier

does openlane support VHDL?

When I go to build one of my test designs I get this error, anyone know possible causes?