Skip to main content

Self-contained RTL to GDS flow for simple chip designs

Project description

microlane

Self-contained RTL to GDS flow for simple chip designs

In a quest to better understand the chip hardening flow I challenged myself to write minimal implementations of Verilog parsing, synthesis, floorplanning, placement, routing and GDS streamout such that they can transform a simple RTL design into a layout that can be manufactured on Tiny Tapeout.

Of course, many corners were cut. 7000 lines of Python code written over a couple of weeks won't stand up to any serious EDA tool. But it does harden the demo design in a way that it passes DRC, LVS and the Tiny Tapeout precheck, as well as the gate-level cocotb testbench and the transistor-level SPICE simulation.

Limitations

  • Only the sky130 & ihp-sg13g2 PDKs are supported.
  • The floorplan is fixed to use a single 1x1 Tiny Tapeout tile.
  • The design has to fit in a single Verilog module.
  • There is only one clock domain. All synchronous logic has to use posedge clk.
  • The gate level netlist is not optimised, so the area needed will be higher than usual.
  • There is no static timing analysis. To prevent hold violations the design is modified to use a two phase non-overlapping clock generated internally. This ensures that it will work at some frequency but not at a particular one known in advance. Also, two physical clock ticks will correspond to one logical clock tick.
  • There is no separate global and detailed placement, nor global and detailed routing. Performing them in a single step incurs extra runtime and memory use.
  • There is no antenna check.
  • The flow is in general rough around the edges. Features not covered by the demo design are only lightly tested and might break or raise "not implemented" errors. Changing the random seed can cause DRC violations in designs that worked previously.
  • DRC, LVS, etc. are not part of the flow. You will need external tools for verification.

Usage

You can try hardening the demo design with:

pip install microlane
export PDK=sky130A
microlane demo.v

The command line interface writes outputs to the current directory and uses fixed settings. For more control, you can import the microlane library from a script and change the configuration.

References

These resources have been helpful in designing the microlane flow:

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

microlane-0.1.0.tar.gz (124.1 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

microlane-0.1.0-py3-none-any.whl (123.5 kB view details)

Uploaded Python 3

File details

Details for the file microlane-0.1.0.tar.gz.

File metadata

  • Download URL: microlane-0.1.0.tar.gz
  • Upload date:
  • Size: 124.1 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.13.11

File hashes

Hashes for microlane-0.1.0.tar.gz
Algorithm Hash digest
SHA256 c85b7400e7608106e77b4740a58d3d8eb3dc1626190d16ac5691ce06b0cc5842
MD5 31e9b12c64cdd4e679d5cdeec61a2e8a
BLAKE2b-256 da338e5663e5c9d49da56020727cd1ab294db53782a891e0b752ce6d45600746

See more details on using hashes here.

File details

Details for the file microlane-0.1.0-py3-none-any.whl.

File metadata

  • Download URL: microlane-0.1.0-py3-none-any.whl
  • Upload date:
  • Size: 123.5 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.13.11

File hashes

Hashes for microlane-0.1.0-py3-none-any.whl
Algorithm Hash digest
SHA256 66449dbfb38fe8d3859fd2bebc8c828f9ceb6979bbc1f8a70af7569ea2c07d65
MD5 ffcd53638a71260276a84df4245927df
BLAKE2b-256 1d7d69f1bc1497116808ec8be8736807981ed342badf130a54f11442807e1e3c

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page