Reference Flow Semiconductor

A reference flow is a foundry's documented, step-by-step methodology for taking a design from RTL through synthesis, place-and-route, and signoff to a tapeout-ready GDSII on a specific process node, using a specific, named combination of EDA tools and settings the foundry has already validated to work correctly together. It exists because a PDK's technical files alone do not tell a design team which tool at which version, run with which specific options and in which specific order, will actually produce a working, signoff-clean result, and discovering that sequence independently, through trial and error, is exactly the multi-month exploration a reference flow is built to eliminate.

A Validated Path From RTL to Signoff-Clean GDSII each stage names a specific tool, version, and setting already proven to work on this process RTL design entry point Synthesis named tool + version pre-validated settings Place & route named tool + version pre-validated settings Signoff DRC/LVS/timing checks named explicitly GDSII tapeout-ready Without a reference flow Team must independently discover a working tool/version/setting combination through trial and error — a multi-month exploration, repeated per project This is exactly the exploration a reference flow is built to eliminate Reference flows are validated once, by the foundry and EDA vendors together, then reused by every subsequent customer.

This validation is specifically a joint effort between the foundry and EDA vendors, not something either party could produce correctly alone. The foundry knows its own process's specific design rules, parasitic behavior, and known problem areas at that node, while the EDA vendor knows its own tool's actual behavior and failure modes in detail; a reference flow is the product of running real test designs through the actual tool chain on the actual process and iterating until the combination produces reliably correct, signoff-clean results, which is exactly why a reference flow for a given node typically is not available until well after that node's preliminary PDK, matching the ecosystem-maturity timeline covered elsewhere on this site.

Foundry and EDA vendor jointly validate a tool chain
against real test designs on the actual process
Specific tool, version, and settings combination proven to work
produces reliably correct, signoff-clean results
Reference flow documented and released to customers
a single customer's independent trial-and-error is no longer necessary
Every subsequent customer reuses the same validated path
the multi-month discovery cost is paid once, not per project

This is why a reference flow's absence, not the absence of a PDK, is frequently what actually blocks a design team from confidently starting a new project, since a team can technically begin exploring a process with only the PDK's technical files, but doing so without a proven tool chain means absorbing exactly the validation risk and schedule cost the reference flow exists to remove, which is why experienced design teams treat reference-flow availability as a real go/no-go gate for committing engineering resources to a new node.

Without a reference flowWith a reference flow
Team independently discovers a working tool chainFoundry and EDA vendor already validated it jointly
Trial-and-error repeated per projectValidation cost paid once, reused by every customer
Real risk of signoff surprises late in the flowSignoff-clean path already proven on real test designs

A reference flow is the specific deliverable that completes the ecosystem-maturity timeline covered elsewhere on this site — it is the last major piece that turns "the node has a PDK" into "a design team can confidently commit to tape out on this node."

Take reference flow semiconductor further

Ask the copilot about this term, or have our engineers assess it against your process.