DRC debugging challenges in AMS/custom designs at 20 nm
Srinivas Velivala, Mentor Graphics
5/23/2013 5:16 PM EDT
The number and complexity of design rule checks (DRC) has always increased node over node, but as the semiconductor industry moves towards 20 nm and below, these increases are skyrocketing (Figure 1). The traditional DRC verification flow used by custom layout designers simply can’t provide the needed level of productivity when debugging DRC results at these advanced nodes. For example, custom layout designers are now confronted with complex checks that involve multiple factors, such as voltage-dependent design rule checks (VD-DRC) and double patterning (DP) checks.
In the long-established verification flow, the designer creates the layout in the design environment, writes out a GDSII file to disk, launches a DRC run, and then fixes the DRC errors in the design environment. Because the error correction and the validation of that correction are separate processes, designers must usually perform multiple iterations of this check-correct-verify process before they achieve signoff DRC closure.
To read the full article, click here
Related Semiconductor IP
- Band-Gap Voltage Reference with dual 2µA Current Source - X-FAB XT018
- 250nA-88μA Current Reference - X-FAB XT018-0.18μm BCD-on-SOI CMOS
- UCIe D2D Adapter & PHY Integrated IP
- Low Dropout (LDO) Regulator
- 16-Bit xSPI PSRAM PHY
Related Articles
- How to tackle serial backplane challenges with high-performance FPGA designs
- How to get more performance in 65 nm FPGA designs
- Security Challenges in Embedded Designs
- Mixed-Signal IP Design Challenges in 28 nm and Beyond
Latest Articles
- SCENIC: Stream Computation-Enhanced SmartNIC
- Agentic AI-based Coverage Closure for Formal Verification
- Microarchitectural Co-Optimization for Sustained Throughput of RISC-V Multi-Lane Chaining Vector Processors
- RISC-V Functional Safety for Autonomous Automotive Systems: An Analytical Framework and Research Roadmap for ML-Assisted Certification
- Emulation-based System-on-Chip Security Verification: Challenges and Opportunities