English
Using OVM to reuse vital verification knowledge
By Jana Richards, LSI Corp. and Dan Cohen, Mentor Graphics
edadesignline.com (January 05, 2010)
Reuse of legacy directed test environments is common practice but, with each generation of reuse, the number of tests grows and with it the overhead of maintaining the environment across multiple projects. Another concern lies in the fragility of directed tests. With each change to a design, a percentage of the directed tests will fail, but a certain percentage will pass but no longer verify their intended feature. Careful, tedious, time consuming auditing is the only way to identify and fix these tests.
During the design of a fifth generation SAS device at LSI, it was clear that our testbench needed significant updates to verify the new features. The environment surrounding the SAS expander design had become cumbersome to manage. With each generation many new features had been added to the design. The new features complicated the existing environment, which, although flexible, had not been designed to verify these features. And, as each new feature meant adding directed tests to the library, after four generations the library contained thousands upon thousands of tests.
Of course, vital verification knowledge was embedded in the existing test patterns that we wanted to preserve. However, documentation associating the tests to the relevant sections within the design specification needed improvement and porting the tests directly would also involve many tedious hours (that our team did not have). As if all of these factors weren't problematic enough, all of this work would need to be repeated for future generations of the device.
Clearly, we needed a new approach; one that could encapsulate the verification knowledge in a portable, documented form that could move easily through future generations of the project without manual intervention. The new approach also needed to show which features of the device had been verified —not just a list of directed tests that had been written.
|
E-mail This Article | 
|
|
Printer-Friendly Page |
|
||||||
Related Articles
- API-based verification: Effective reuse of verification environment components
- Reuse UVM RTL verification tests for gate level simulation
- Reduce SoC verification time through reuse in pre-silicon validation
- Design Reuse without Verification Reuse Is Useless
- SystemC library supporting OVM compliant verification methodology
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)