"Tagging version 1.0.194"
Added the "MR" (manufacturing rules) DRC deck for klayout.
2 files changed
tree: b7560e3225c4b0f22113131c144d0fcd9897ee72
  1. .gitignore
  2. .travis.yml
  3. .travisCI/
  4. LICENSE
  5. Makefile.in
  6. README
  7. README.md
  8. VERSION
  9. common/
  10. configure
  11. scripts/
  12. sky130/
README.md

Open-PDKs (open_pdks)

Summary:

Automatic setup of PDKs for open-source tools from foundry sources.

Builds out and populates a new set of directories and subdirectories in the efabless format, with the efabless name for the PDK at the top, followed by categories “libs.ref” (IP) and “libs.tech” (EDA tool setup), each with subcategories corresponding to layout, abstract views, netlists, etc. for the IP; and magic, netgen, qflow, etc., for the EDA tool setup.

The populated PDK directories can contain either copies of files from the foundry sources, links to the foundry sources, or links back to another PDK.

Generates magic layout views for all vendor IP for which either a GDS view or a LEF view exists. Annotates the views as needed to handle ports, bounding boxes, etc.


This distribution contains sources for building out the SkyWater SKY130 130nm process. Sources for the foundry process data must be obtained separately. Read the README file in subdirectory sky130/ for instructions on obtaining and building the SkyWater sky130A PDK.


License:

Open_PDKs is open-source software distributed under the Apache-2.0 license. See file LICENSE for the complete license text.


Instructions:

git clone https://github.com/RTimothyEdwards/open_pdks.git
cd open_pdks
./configure [options]
make
[sudo] make install

where the configure [options] are specific to each foundry PDK supported by open_pdks and can be queried using

./configure --help

At a minimum you will want to pass a configure option to declare the location of the PDK vendor source distribution (which can be obtained separately),

./configure --enable-[PDK_name]-pdk=[path]

The open_pdks version of the PDK can be built locally within open_pdks without the need to declare an install target or run “make install”. However, it is recommended to declare a target location and install there, using

./configure --enable-[PDK_name]-pdk=[path] --with-[PDK_name]-local-path=[path]

followed by “make” and “make install”.

Also see the website at http://opencircuitdesign.com/open_pdks/. The “Install” page has full instructions for configuring and installing open_pdks.