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 PDK is supported (with the high density standard cells).
  • 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
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.0.2.tar.gz (98.5 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.0.2-py3-none-any.whl (96.9 kB view details)

Uploaded Python 3

File details

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

File metadata

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

File hashes

Hashes for microlane-0.0.2.tar.gz
Algorithm Hash digest
SHA256 75d50c3b8eabbc7f6068e1739cd89cb9d5fcdcc0480dcb97e64579af6147ae61
MD5 a1f63ec24a6206752689e51d47ca55c5
BLAKE2b-256 31604ed278ac17c5e5df3e5ecab61d33fc73f991ac71a1a2ccc51f77042f8f69

See more details on using hashes here.

File details

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

File metadata

  • Download URL: microlane-0.0.2-py3-none-any.whl
  • Upload date:
  • Size: 96.9 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.0.2-py3-none-any.whl
Algorithm Hash digest
SHA256 fa2b35955a36d35b492a74bcecbb5bafb7326d3b662d57900277d90a72eec362
MD5 29f2cf9358d41b22fe5863f97b1100f8
BLAKE2b-256 956c0c716c783bc4445a5f32aa1a96ce79e06a26440ba0e725e0121f9abd6e6e

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