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
- SpaceWire Node IP core
- nQrux Secure Boot
- 4K/8K Multiformat IP supporting AV2 decoder
- Ultra Ethernet MAC & PCS 100G/200G/400G/800G
- Ethernet PCS 100G/200G/400G/800G/1.6T
Related Blogs
- Design for Verification - a natural next step?
- Design, Verification, and Software Development Decisions Require a Single Source of Truth
- 4 Ways that Digital Techniques Can Speed Up Memory Design and Verification
- DDR5 DIMM Design and Verification Considerations
Latest Blogs
- A Repeatable Framework for Hardware Security Assurance
- Inside the SiFive Performance™ P570 Gen 3: High Performance Efficiency for Next-Generation Consumer and Commercial Applications
- What the steam engine can teach us about modern chip design
- Automotive silicon in the era of AI, functional safety, and cybersecurity
- JPEG XS Officially Joins GenICam, The Machine Vision Standard Managed By EMVA