Tapeout is the moment your design leaves the digital world and becomes physical reality. A single DRC error or LVS mismatch at this stage costs weeks and millions of dollars. This chapter covers the final steps from routed layout to foundry-ready GDS2 — and the long road to production silicon.
Tapeout is the delivery of the final chip layout — a GDS2 (GDSII) file — to the semiconductor foundry. The name derives from the era when design data was physically delivered to the fab on magnetic tape. Today, the encrypted GDS2 database is transmitted electronically, but the moment remains the most significant milestone in the chip development process.
GDS2 is a hierarchical binary database format that stores every geometric polygon on every mask layer of the chip. A modern SoC GDS2 file is typically 50–500 GB, containing trillions of polygons across 60–100 mask layers. The foundry uses the GDS2 file to generate photomasks — the glass reticles that expose the wafer during lithography.
| Node | Mask count | Mask cost | MPW shuttle cost |
|---|---|---|---|
| 180 nm | ~25 | $50K–$150K | $5K–$20K |
| 28 nm | ~40 | $500K–$1.5M | $50K–$200K |
| 7 nm | ~70+ | $5M–$15M | $300K–$1M |
| 3 nm | ~100+ | $20M–$50M | $1M–$3M |
Multi-Project Wafer (MPW) shuttles share a mask set across multiple designs, splitting the cost. Foundries (TSMC, GlobalFoundries) run regular MPW shuttles — small companies and universities can tapeout for a fraction of the full mask cost by sharing die space with other customers.
DRC verifies that every polygon in the GDS2 conforms to the foundry's manufacturing rules. A modern PDK contains thousands of DRC rules per layer — minimum spacing, minimum width, via enclosure, density rules, forbidden patterns, and complex multi-layer interaction rules. Sign-off DRC uses the foundry's official rule deck (not the EDA tool's internal rules) run on Calibre or PVS.
LVS extracts the netlist from the GDS2 layout by tracing metal connectivity through vias and comparing it to the schematic (or post-route netlist). Every net, every transistor, every device parameter must match exactly. Common LVS failures:
ERC catches electrical issues that DRC and LVS miss: floating gate inputs (undriven gates that may latch-up), antenna violations, ESD rule violations, and power domain connectivity errors. ERC complements LVS — where LVS checks connectivity structure, ERC checks electrical correctness.
Semiconductor manufacturing requires uniform metal and poly density across the die for CMP (Chemical Mechanical Planarization) — the polishing step that planarizes each layer. Where density is too low, CMP over-polishes, creating dishing and erosion. Where density is too high, CMP under-polishes, leaving bumps. Both affect the flatness of the next deposited layer, ultimately impacting yield.
The fill engine automatically inserts dummy fill shapes — floating metal or poly polygons with no electrical connection — to bring all layers within the foundry's density window (typically 20–80% density measured in any 50×50 µm window). Fill shapes are added after routing and before DRC sign-off, because they affect the final DRC density checks.
The seal ring is a closed ring of metal and poly that runs around the entire chip perimeter, just inside the scribe line (the area where the wafer is diced). It serves two critical protection functions:
Inside the seal ring, an inner guard ring (often called an ESD guard ring) provides additional ESD protection. These guard rings use specific PDK cells and must connect to VDD and VSS rails. DRC checks that the seal ring is complete (no gaps) and that all via connections are present.
The final GDS2 is not a single file generated by the router — it is a merge of multiple components:
The merge tool (Calibre Merge, PVS Stream) hierarchically combines all components into a single master GDS. The final DRC and LVS must run on this merged GDS — not on intermediate pre-merge databases. Any differences between the merged GDS and the post-route database must be investigated and resolved.
# Run final DRC sign-off (Calibre) run_drc \ -rule_file ${PDK_DIR}/calibre_drc.rule \ -layout_file final_chip.gds \ -top_cell CHIP_TOP \ -output_db ./signoff/drc_results.db # Run LVS sign-off run_lvs \ -rule_file ${PDK_DIR}/calibre_lvs.rule \ -layout_file final_chip.gds \ -source_file final_netlist.cdl \ -report ./signoff/lvs_report.txt # Insert dummy fill create_fill \ -layers {M1 M2 M3 M4 M5} \ -space_to_signal 0.1 \ -density_window 50 # Export GDS stream for foundry export_stream \ -format GDS2 \ -output final_chip_tapeout.gds \ -map_file metal_layer_map.txt \ -merge_files {cells.gds macros.gds pads.gds fill.gds sealring.gds}
After the GDS2 is accepted by the foundry, the journey from digital file to working chip takes months:
From RTL coding through synthesis, floorplan, placement, CTS, routing, STA, DFT, power analysis, and tapeout — you now have a complete mental model of the ASIC design flow. Explore the series index to review any chapter.
Back to Series Overview