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.
To read the full article, click here
Related Semiconductor IP
- ReRAM NVM in DB HiTek 130nm BCD
- UFS 5.0 Host Controller IP
- PDM Receiver/PDM-to-PCM Converter
- Voltage and Temperature Sensor with integrated ADC - GlobalFoundries® 22FDX®
- 8MHz / 40MHz Pierce Oscillator - X-FAB XT018-0.18µm
Related Articles
- Early Interactive Short Isolation for Faster SoC Verification
- SV-LLM: An Agentic Approach for SoC Security Verification using Large Language Models
- PCI Express verification underscores need to plan
- Interconnect (NoC) verification in SoC design
Latest Articles
- An FPGA-Based SoC Architecture with a RISC-V Controller for Energy-Efficient Temporal-Coding Spiking Neural Networks
- Enabling RISC-V Vector Code Generation in MLIR through Custom xDSL Lowerings
- A Scalable Open-Source QEC System with Sub-Microsecond Decoding-Feedback Latency
- SNAP-V: A RISC-V SoC with Configurable Neuromorphic Acceleration for Small-Scale Spiking Neural Networks
- An FPGA Implementation of Displacement Vector Search for Intra Pattern Copy in JPEG XS