Hardware-Assisted Verification: The Real Story Behind Capacity
While design engineers contemplate the power, performance and area calculation of an SoC design, their verification counterparts are thinking about whether the hardware emulation and prototyping platform available to them has enough capacity to complete the system-level verification task.
This is particularly true for verifying hardware functionality with complex software workloads. Here is where the concept of usable capacity is an important metric and often misunderstood—especially in the era of skyrocketing gate counts (2.5D- and 3D-IC stacking and chiplets) and massive software workloads. Verification engineers need to know, up front, that their hardware verification platform delivers required usable capacity to verify the SoC at the system level.
To verify large, complex designs like these, verification teams need a platform that can handle capacity scaling in a deterministic and repetitive way. For example, emulating 10 one-billion gate designs versus one 10-billion gates is different and poses significant scaling challenges for both the hardware and software.
To read the full article, click here
Related Semiconductor IP
- MACsec Engine optimized for 10Base-T1S/T1L applications
- Dual Port, Voltage Scaling Register File Compiler on GF22FDX+
- Single Port, Voltage Scaling, High Speed SRAM Memory Compiler on GF22FDX+
- I3C Full Controller / Target
- I3C HCI Host Controller
Related Blogs
- Synopsys CXL Protocol Verification Solutions Proven with Real World Vendor Devices at the CXL Compliance Test Event
- The Rise of Physical AI: When Intelligence Enters the Real World
- Heterogeneous NPU Data Movement Tax: Intel's Own Slides Tell the Story
- Verification Sanity in Chiplets & Edge AI: Avoid the “Second Design” Trap