Design for Verification: A Natural Next Step?
Let's look at a variety of "Design for Verification" techniques aimed at reducing bugs and making designs easier to verify.
After years of innovation in verification of increasingly complex designs, should we now turn our attention to the design process itself? Since starting in verification in the early 1990s, I have witnessed the introduction of code and functional coverage, constrained random, assertions, numerous metrics, formal verification, various languages and methodologies, and, more recently, Requirements Driven Verification. However, we have never considered in detail how to reduce the number of bugs that get introduced into the designs in the first place and ways to make them easier to find.
To read the full article, click here
Related Semiconductor IP
- LPDDR6/5X/5 PHY V2 - Intel 18A-P
- ML-KEM Key Encapsulation & ML-DSA Digital Signature Engine
- MIPI SoundWire I3S Peripheral IP
- ML-DSA Digital Signature Engine
- P1619 / 802.1ae (MACSec) GCM/XTS/CBC-AES Core
Related Blogs
- Design for Verification - a natural next step?
- Verification of the Lane Adapter FSM of a USB4 Router Design Is Not Simple
- 4 Ways that Digital Techniques Can Speed Up Memory Design and Verification
- DDR5 DIMM Design and Verification Considerations
Latest Blogs
- PCIe Low-Power Validation Challenges and Potential Solutions (PIPE/L1 Substates)
- Rethinking Edge AI Interconnects: Why Multi-Protocol Is the New Standard
- Tidying Up: FIPS-Compliant Secure Zeroization for OTP
- Accelerating Your Development: Simplify SoC I/O with a Single Multi-Protocol SerDes IP
- Why What Where DIFI and the new version 1.3