Is Your Functional Coverage Stuck at 70%?
You certainly can’t improve something unless you measure it. So, how do you know if the functionality of your design has been verified completely? One metric that helps answer this question is coverage. Coverage is a guide for directing verification completeness by identifying covered and uncovered portions of the design.
Coverage can be broadly classified into two categories - Functional and Code coverage. Functional coverage complements Code coverage to handle the exponential increase in complexity and state space of the designs. Functional coverage gets interesting when two or more cover-points are crossed, leading to a variety of possibilities covering interesting combinations of important parameters.
Most of the today’s well-designed constrained random environments will easily take you to around 60 to 70 % of the functional coverage. So, how do you take it from here to get to the magic figure of 100% functional coverage?
The answer lies in following the few steps outlined below. Also added as a ready reckoner, is a flowchart that summarizes these steps.
Related Semiconductor IP
- NPU IP
- JPEG XL Encoder
- I2C Master/Slave Controller Core
- NVMe Validation Test Suite
- Hybrid Memory Cube Verification IP
Related Blogs
- Functional Coverage Plan Management - What's the Secret Sauce?
- Increasing Verification Productivity Through Automation of Functional Coverage Management
- The Role of Coverage in Formal Verification, Part 1 of 3
- Functional verification concepts have to change
Latest Blogs
- Tape-Out Readiness Checklist: Engineering Decisions That Prevent Costly Respins
- How Cadence DSPs Put In-Cabin AI Audio On-Chip in SemiDrive's X10
- The Fastest Path to Scalable Photonic Systems: Using Proven IP for both PIC and EIC designs
- Building Trusted AI Agents from the Silicon Root of Trust
- Heterogeneous Computing in Space