Hello all,
I am trying to run the setup described at
https://openlane.readthedocs.io/en/latest/getting_started/installation/installation_ubuntu.html
I am using Windows 11 with ubuntu 20.04 installed on an Oracle VirtualBox.
I am running everything smoothly down to the make mount command, with all messages in line with the description.
after make mount I tried to open the spm.gds with klayout using the commands, but I got an error message.
my commands are below, showing that make test command returns "Basic test passed" but then running make mount and the klayout commands fail somehow.
I am not very familiar with running an ASIC environment with make and python commands, but I have used klayout previously.
I noticed that klayout is not in fact installed after running the commands described on the page.
Should I install klayout independently of the openlane installation?
Any hints and help are appreciated.
*****************
dorin@ASIC:~/OpenLane$ make test
...
[WARNING]: Current core area is too small for the power grid settings chosen. The power grid will be scaled down.
Basic test passed
dorin@ASIC:~/OpenLane$ make mount
cd /home/dorin/OpenLane && \
docker run --rm -v /home/dorin/OpenLane:/openlane -v /home/dorin/OpenLane/designs:/openlane/install -v /home/dorin/OpenLane/pdks:/home/dorin/OpenLane/pdks -e PDK_ROOT=/home/dorin/OpenLane/pdks -e PDK=sky130A --user 1000:1000 -e DISPLAY=:0 -v /tmp/.X11-unix:/tmp/.X11-unix -v /home/dorin/.Xauthority:/.Xauthority --network host --security-opt seccomp=unconfined -ti efabless/openlane:45980c85ecf4094c977785432a8ebb0adf0e562d-amd64
OpenLane Container (45980c8):/openlane$ klayout -e -nn $PDK_ROOT/sky130A/libs.tech/klayout/tech/sky130A.lyt \
-l $PDK_ROOT/sky130A/libs.tech/klayout/tech/sky130A.lyp \
./designs/spm/runs/openlane_test/results/final/gds/spm.gds
process 10: The last reference on a connection was dropped without closing the connection. This is a bug in an application. See dbus_connection_unref() documentation for details.
Most likely, the application was supposed to call dbus_connection_close(), since this is a private connection.
D-Bus not built with -rdynamic so unable to print a backtrace
******************