English
SoC technology underscores need for verification
Amjad Qureshi, Cadence Design Systems
(08/27/2007 8:57 AM EDT) -- EE Times
As system-on chip (SoC) designs become more complex, verification remains the critical challenge. Larger teams continually use more resources to search for the most efficient ways to integrate new methodologies and ultimately design with verification in mind. Although we know that implementing a verification plan accounts for nearly two- thirds of the overall chip design effort, we continue to see teams delivering chips late and missing projected tape-out deadlines. This type of carelessness can result in serious consequences to the business, because it means that hardware and software bugs often escape discovery until late in the design cycle.
To create a comprehensive verification solution, we must first acknowledge both the differences and the challenges that designers and verification engineers face. In the process, we find that certain gaps are inadvertently neglected. The first major gap that is commonly overlooked is "reuse." Often, block-level verification environments are not leveraged within the cluster level (subsystem) or the chip level, which presents a major problem.
(08/27/2007 8:57 AM EDT) -- EE Times
As system-on chip (SoC) designs become more complex, verification remains the critical challenge. Larger teams continually use more resources to search for the most efficient ways to integrate new methodologies and ultimately design with verification in mind. Although we know that implementing a verification plan accounts for nearly two- thirds of the overall chip design effort, we continue to see teams delivering chips late and missing projected tape-out deadlines. This type of carelessness can result in serious consequences to the business, because it means that hardware and software bugs often escape discovery until late in the design cycle.
To create a comprehensive verification solution, we must first acknowledge both the differences and the challenges that designers and verification engineers face. In the process, we find that certain gaps are inadvertently neglected. The first major gap that is commonly overlooked is "reuse." Often, block-level verification environments are not leveraged within the cluster level (subsystem) or the chip level, which presents a major problem.
|
E-mail This Article | 
|
|
Printer-Friendly Page |
|
||||||
Cadence Design Systems, Inc. Hot IP
Related Articles
New Articles
- Discover new Tessent UltraSight-V from Siemens EDA, and accelerate your RISC-V development.
- The Critical Factors of a High-performance Audio Codec - What Chip Designers Need to Know
- Density Management in Analog Layout Design: Addressing Issues and Ensuring Consistency
- Nexus: A Lightweight and Scalable Multi-Agent Framework for Complex Tasks Automation
- How the Ability to Manage Register Specifications Helps You Create More Competitive Products
Most Popular
- System Verilog Assertions Simplified
- System Verilog Macro: A Powerful Feature for Design Verification Projects
- Synthesis Methodology & Netlist Qualification
- Discover new Tessent UltraSight-V from Siemens EDA, and accelerate your RISC-V development.
- Understanding Logic Equivalence Check (LEC) Flow and Its Challenges and Proposed Solution