1 / 18

Exploiting Architecture For Verification

Exploiting Architecture For Verification. Dave Whipp. Architecture For Verification. Simplify the Design Reduce corner cases Decoupled State Machines Focus Complexity on Performance Tradeoff Performance Vs Schedule Provide Verification-Friendly Work Products Models Test benches Tests.

nadda
Download Presentation

Exploiting Architecture For Verification

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Exploiting ArchitectureFor Verification Dave Whipp

  2. Architecture For Verification • Simplify the Design • Reduce corner cases • Decoupled State Machines • Focus Complexity on Performance • Tradeoff Performance Vs Schedule • Provide Verification-Friendly Work Products • Models • Test benches • Tests

  3. A HW Development Flow (BAD) Big Paper Spec ISS Model Verification Coverage Debug Design Checkers Testbench Tests RTL Synthesis Clocks, Resets C Model Directed Assertions BFMs, Assertions Randoms TLMs Scoreboard

  4. A HW Development Flow (BAD) Big Paper Spec ISS Model Verification Coverage Debug Design Checkers Testbench Tests RTL Synthesis Clocks, Resets C Model Directed Assertions BFMs, Assertions Randoms TLMs Scoreboard

  5. A HW Development Flow (Better) Small Paper Spec Coverage Triage ISS Model ESL Verification C Model Debug Coverage Testbench Randoms Interfaces Validation Design Assertions Scoreboards TLMs RTL BFMs Assertions Directed Tests Clocks, Resets Synthesis

  6. What Type of Model? ISS: A B C D E F G TLM: BE CF D A G How do we model that these are equivalent?

  7. Exploitation of Executable Models • Product Development • Enable SW development • Validate the Architecture • Verification Bootstrapping • Validate Tests • Functional Checkers • Validate Assertions • Architectural Coverage

  8. Design Verification Testbenches Coverage Model Scenario Generator Scenario Checker UTF model Transaction Producer Transaction Consumer DUT BFM BFM

  9. Architectural Validation Testbenches Coverage Model Scenario Generator Scenario Checker UTF model Transaction Producer Transaction Consumer

  10. How To Reuse Architectural Tests Micro Architectural Architectural

  11. Architectural Bringup Tests Micro Architectural Architectural

  12. Micro-architectural Directed Tests Micro Architectural Architectural

  13. Micro-architectural Directed Tests Deep Interactions Shallow Features

  14. Constrained Random Tests Deep Interactions Shallow Features

  15. Random Directed Tests Deep Interactions Shallow Features

  16. Testing using Graphs Shape Triangle Line Aspect Body Solid Short Fat Stipple Outline Long Skinny Dashed Filled

  17. Micro-Architectural Tests Address Cacheable No Page Yes New Evict dirty Reuse Evict about-to-be-needed

  18. Conclusion • Architects must create Executable Representations • Validated by Architects • Reused by Verifiers • Not Just Models • Testbenches and VIP • Self-Checking Tests (Directed Random) • Traditional Models serve Multiple Roles • Checkers • Assertions • Coverage

More Related