Project update 2 of 13
Hey everyone,
If you’ve been following open silicon over the past few years, you know the story: Google’s open PDK program changed everything, but when Efabless shut down earlier this year, a lot of infrastructure disappeared. That’s part of why wafer.space exists - to rebuild accessible fabrication services.
But fabrication is only half the equation. You also need tools to actually design your chip. That’s where LibreLane comes in.
Last month at ORConf 2025 in Valencia, Mohamed Gaber and Leo Moser presented LibreLane - the next-generation design flow for open silicon. And there’s now a ready-to-use gf180mcu project template that makes starting your wafer.space design even easier.
LibreLane is a ground-up rewrite of OpenLane - the tool that made hundreds of open-source tapeouts possible through Google’s MPW shuttles and Efabless programs. Originally developed as "OpenLane 2" at Efabless, it’s now community-driven under the FOSSi Foundation after being officially released in July 2025.
If you used OpenLane 1, you know it works: you give it a Verilog file and a config, run one command, and get GDS ready for fabrication. LibreLane keeps that simplicity while fixing the pain points.
OpenLane 1 was built under tight deadlines to enable the first Google MPW shuttles. It worked amazingly well for that goal, but had some limitations:
LibreLane addresses all of this while maintaining backwards compatibility - your existing OpenLane 1 configs work with LibreLane.
🐍 Python-Based Infrastructure: Modern Python instead of Tcl means better tooling, clearer code, and a real API if you need programmatic control. No more fighting with "stringly-typed" scripts.
🔧 Modular Architecture: Run individual steps (synthesis, placement, routing) independently. Insert custom tools into the flow. Debug specific stages without rerunning everything. The flow is a pipeline you can actually customize.
📊 Clear Error Reporting: Standardized metrics and status reporting at every step. When something fails, you know exactly where and why.
🎯 Automated Padframe Generation: LibreLane handles IO pad insertion and configuration automatically. This is huge - pad ring creation used to be one of the most error-prone manual steps. Now it just works.
🌍 Multi-PDK Support: The same design can target different process design kits. gf180mcu is fully supported on the main branch, as is sky130, while ihp-sg13g2 is supported in the dev branch. Write once, fabricate anywhere.
↔ Backwards Compatible: Existing OpenLane 1 configurations work with LibreLane. Easy migration path if you’ve used OpenLane before.
LibreLane isn’t experimental - it’s already in production use:
The shift from OpenLane 1 to LibreLane mirrors what happened in the fabrication world: when Efabless shut down, the community rebuilt better infrastructure. wafer.space rebuilt affordable fabrication access. LibreLane rebuilt the design flow. Both are about making open silicon sustainable.
To make getting started even easier, there’s now a project template specifically configured for wafer.space designs targetting the gf180mcuD PDK variant.
This template gives you a working starting point with everything included:
nix-shell and you're ready to go, no manual tool installation# Clone the template
git clone https://github.com/wafer-space/gf180mcu-project-template
cd gf180mcu-project-template
# Set up environment (installs everything automatically)
nix-shell
# Add your design to src/
# Update librelane/config.yaml with your design parameters
# Run the flow
make librelane
# View the results
# Opens in OpenROAD GUI or KLayout
make librelane-openroad
make librelane-klayout
That’s it. Five steps from empty directory to GDS output.
Everything is set up to work together. You focus on your design, the template handles the infrastructure.
Want to see LibreLane in action? The full ORConf 2025 presentation by Mohamed Gaber and Leo Moser is on YouTube:
The talk covers:
It’s worth watching if you want to understand the full capabilities beyond just running make librelane.
This is a work in progress. LibreLane and the template are actively developed and improving. If you use them:
The template is an example to help you get started, not a mandatory requirement. You can use LibreLane directly, adapt the template to your needs, or build your own workflow entirely. It’s there to make your life easier, not to constrain how you work.
Community support is available through the FOSSi Foundation chat and the wafer.space Discord / Matrix channels. LibreLane has active developers and users who can help.
LibreLane:
gf180mcu Project Template:
Community:
Open silicon has come a long way in just a few years. We went from "you need millions of dollars and proprietary tools" to "here’s an affordable MPW run and free, open-source tools."
But accessible doesn’t mean easy. Chip design is inherently complex. Projects like LibreLane and templates like this one are about removing the incidental complexity - the tool installation headaches, the configuration mysteries, the "why doesn’t this work" debugging sessions.
Your time should go into designing your chip, not fighting your tools.
LibreLane handles the flow. The template handles the setup. You handle the innovation.
Whether you’re targeting the December 3rd deadline or planning for a future run, these tools are here to help you go from idea to silicon faster and with less friction.