Files
OpenLane/docs/source/usage/custom_pdk_builds.md
Mohamed Gaber cbb9e6b02a Documentation Restructure (#1337)
~ Documentation all moved under `docs/source`, arranged hierarchically according to the table of contents
~ `Klayout` changed to `KLayout` in all logging messages
~ Readme rewritten to just be concise, parts of it isolated into standalone documentation
~ RTD builds no longer use conda (saves some time)
~ Fixed all broken links
2022-09-12 14:49:15 +02:00

1.5 KiB

Custom-Building PDKs

The pre-built version of the sky130 PDK variants included with OpenLane includes the following standard cell libraries:

  • sky130_fd_io
  • sky130_fd_pr
  • sky130_fd_sc_hd
  • sky130_fd_sc_hvl
  • sky130 sram modules

If you need other libraries, you will have to resort to manual builds using Volare as shown below. You will need Git 2.35+ and Docker.

Note that this will take a while, from 20 minutes to an hour depending on your internet speed and compute power.

Start a venv shell using make start-build-env. You should see a prompt looking kind of like this:

(venv) [user@host openlane]$ 

First of all, install volare:

pip3 install --upgrade --no-cache-dir volare

Then, build the PDK as follows: The -l options are the libraries you want to include. For example, to also include sky130_fd_sc_hs, you can add -l sky130_fd_sc_hs to the default set of libraries using the following command:

volare build -j$(nproc) --pdk sky130 --clear-build-artifacts --sram -l sky130_fd_io -l sky130_fd_pr -l sky130_fd_sc_hvl -l sky130_fd_sc_hd -l sky130_fd_sc_hs

You can also add -l all to just include all of them:

volare build -j$(nproc) --pdk sky130 --clear-build-artifacts --sram -l all

Either way, go grab a smoothie. This will take a while.

After it's done, you can then enable the resulting PDK as such:

volare enable

Et voila, your custom-built PDK is ready.