ASIC Flow and Platform Support Guide

Understanding the End-to-End ASIC Design Flow

ASIC (Application-Specific Integrated Circuit) design is one of the most complex and rigorous engineering disciplines. It involves transforming a conceptual idea into a physical silicon die. The process is linear, cyclical, and requires absolute coordination across multiple specialized EDA tools and engineering teams. Understanding the design flow is recognizing the ordered series of checks and modifications required before tape-out.

The flow typically begins at the architectural or behavioral level (RTL) and progresses through increasingly physical, constrained stages. The overall goal is high performance, low power, and manufacturability, all verified against the foundry's Process Design Kit (PDK).

From RTL to Silicon: The Key Stages

• Behavioral Model (RTL): The design is first written in an HDL like Verilog. This is the intellectual core, defining what the circuit must do.
• Functional Simulation: High-level simulation checks if the circuit logic is correct, independent of physical constraints.
• Synthesis: The RTL code is translated into standard cell netlists using place and route tools. This defines how the circuit must be built using library components.
• Physical Design: The netlist is laid out onto the silicon wafer. This involves detailed placement, routing, and power grid generation.
• Verification & Sign-off: This is the final, critical step where every physical constraint is checked, ensuring the design is stable, robust, and ready for manufacturing.
• RISC-V EDA Tools Guide

The Role of the Process Design Kit (PDK)

The PDK is perhaps the most crucial component for a successful ASIC run. It acts as the rulebook for the entire process. A PDK is a comprehensive collection of documents, libraries, and rules provided by the silicon foundry (the fab). It defines:

• Design Rules (DRC): Minimum spacing between wires and transistors.
• Electrical Rules (LVS): Ensuring the layout perfectly matches the intended connectivity (netlist).
• Process Parameters: Transistor types, metal stack details, etc.

Without following the PDK rules, the chip cannot be patterned correctly by the fabrication plant (fab), leading to failures or non-functional silicon.

Deep Dive: Physical Verification Techniques

Physical verification is not a single step; it is a series of checks performed at escalating levels of complexity. The primary tools are DRC (Design Rule Check) and LVS (Layout Versus Schematic).

1. Design Rule Check (DRC)

DRC is the most fundamental check. It ensures every geometrical element (via, wire, transistor) adheres to the minimum spacing and size rules mandated by the PDK. For instance, if a foundry mandates 20nm spacing between contacts, the DRC tool verifies this spacing across the entire layout.

2. Layout Versus Schematic (LVS)

LVS is the circuit connectivity check. It compares the netlist derived from the physical layout against the original, synthesized netlist. It must confirm that every connection exists exactly as intended and that no spurious connections (shorts) or broken connections (opens) were introduced during physical steps. A typical LVS check involves traversing the nets and comparing the list of connected pins.

3. Advanced Checks: Timing and Power

Beyond geometry, verification includes Static Timing Analysis (STA), which ensures all signals arrive within their specified setup and hold times. Furthermore, Signal Integrity (SI) and Power Integrity (PI) analysis are critical to ensure the design can handle voltage drop and noise without failure. These checks guide the placement and power mesh design to prevent operational failures.

Platform Enablement and Automation

The complexity of modern designs makes manual execution impossible. This necessitates 'Platform Enablement'—automating the entire flow. This is where expertise in scripting languages like Tcl/Tk, Python, and specialized EDA scripting languages (like SKILL for Cadence) comes into play. Scripting allows designers to:

• Automate Repetitive Tasks: Running the full DRC/LVS/STA sequence across multiple IP blocks or corners.
• Manage Data Flow: Tracking design iterations, associating specific PDK versions, and passing results between tools.
• Create Reusable IP: Building complex wrappers or flows that can be dropped into different system-level designs.

Effective platform support means building a scaffold of code and scripts that guides novel designs through the established, tedious manual process, drastically reducing Time-to-Market (TTM) and increasing yield.

Related Articles

• What Is EDA Automation?
• Cadence SKILL Scripting Guide
• CAD Infrastructure for Semiconductor
• PDK Setup and Enablement
• DRC/LVS Physical Verification
• Synopsys Custom Compiler Automation
• Tcl/Tk for EDA Automation
• Virtuoso Layout Automation
• GDSII OASIS Layout Automation
• FlexNet Licensing for EDA Tools
• Open Source EDA Tools Guide
• Advanced Node Verification
• Cloud EDA SaaS Solutions
• DFT Design for Test Automation
• Timing Closure Automation Guide
• Calibre SVRF TVF Rule Decks Guide
• Python EDA Automation Guide
• IP Porting and Migration Guide
• Mixed-Signal Verification Guide