Design for Verification: A Natural Next Step?
January 8, 2015
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
- Flexible Pixel Processor Video IP
- Complex Digital Up Converter
- Bluetooth Low Energy 6.0 Digital IP
- Verification IP for Ultra Ethernet (UEC)
- MIPI SWI3S Manager Core IP
Related Blogs
- Design for Verification - a natural next step?
- Verification of the Lane Adapter FSM of a USB4 Router Design Is Not Simple
- Leveraging a Unified Emulation and Prototyping System to Address Verification Requirements Across the Chip Development Cycle
- Delivering a Secure, Cloud-Based SoC Design Environment for Aerospace Chip Designers
Latest Blogs
- Evolution of CXL PBR Switch in the CXL Fabric
- CNNs and Transformers: Decoding the Titans of AI
- How is RISC-V’s open and customizable design changing embedded systems?
- Imagination GPUs now support Vulkan 1.4 and Android 16
- From "What-If" to "What-Is": Cadence IP Validation for Silicon Platform Success