How to increase confidence that third-party IP is functionally correct
October 01, 2006 -- edadesignline.com
The EDA industry has provided designers with a vast arsenal of tools that can be used to verify the functional correctness of an IP design.
Functional correctness for IP is essential yet elusive. In our first article A hierarchy of needs for SoC IP reuse, we described a hierarchical model to relate the relative priority of the deliverables from IP providers to the SoC designer who uses them. Based on Abraham Maslow's theory that all human beings have a basic set of needs that form a hierarchy, the SoC Designer's IP Needs Hierarchy has five levels of needs beginning with Functional Correctness:
In this article, we discuss the most basic need of every chip designer – functionally correct IP. The best and most unambiguous measure of functional correctness is the extent to which IP has been validated in production silicon. SoC designers don't like being the lab rats of IP providers and often find themselves discovering bugs that should have been sorted out long ago by the provider. SoC designers want to use IP that has been silicon proven – and the more times the better.
E-mail This Article | Printer-Friendly Page |
|
Related Articles
New Articles
- Quantum Readiness Considerations for Suppliers and Manufacturers
- A Rad Hard ASIC Design Approach: Triple Modular Redundancy (TMR)
- Early Interactive Short Isolation for Faster SoC Verification
- The Ideal Crypto Coprocessor with Root of Trust to Support Customer Complete Full Chip Evaluation: PUFcc gained SESIP and PSA Certified™ Level 3 RoT Component Certification
- Advanced Packaging and Chiplets Can Be for Everyone
Most Popular
- System Verilog Assertions Simplified
- System Verilog Macro: A Powerful Feature for Design Verification Projects
- UPF Constraint coding for SoC - A Case Study
- Dynamic Memory Allocation and Fragmentation in C and C++
- Enhancing VLSI Design Efficiency: Tackling Congestion and Shorts with Practical Approaches and PnR Tool (ICC2)