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
- Post-Quantum Digital Signature IP Core
- Compact Embedded RISC-V Processor
- Power-OK Monitor
- RISC-V-Based, Open Source AI Accelerator for the Edge
- Securyzr™ neo Core Platform
Related White Papers
- 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 White Papers
- DRsam: Detection of Fault-Based Microarchitectural Side-Channel Attacks in RISC-V Using Statistical Preprocessing and Association Rule Mining
- ShuffleV: A Microarchitectural Defense Strategy against Electromagnetic Side-Channel Attacks in Microprocessors
- Practical Considerations of LDPC Decoder Design in Communications Systems
- A Direct Memory Access Controller (DMAC) for Irregular Data Transfers on RISC-V Linux Systems
- A logically correct SoC design isn’t an optimized design