0
Efficiency Through Methodology
                                   DV Club RTP
                                  Mark Stric...
Challenge of Verification




                Quality                                          Schedule
           (all bu...
How to Meet the Challenge

  • Efficiency – get the most from your time
               Use components from other projects
...
Some Examples Used at Cisco

  • A high-level overview of some reuse methodology
    techniques that we use at Cisco follo...
Three Stages of Testbench Creation

  • Component Design
               Want to describe the behavior of the component wit...
Testflow

  • The Issue: Sometimes all components must finish
    an activity (e.g. reset) before any of them moves on
  •...
Unit-Level Benches and Reuse

  • Unit-level benches offer best control of stimulus
    and visibility of results
  • Reus...
Transaction Linking

  • Each checker that corresponds to a block that
    passes information to the next block contribute...
Templates and Generators

  • Burden falls on the component designer
  • The infrastructure of components can be made in a...
Summary

  • Biggest efficiency gains from methodology
               – If code was in the same language but did not inclu...
Upcoming SlideShare
Loading in...5
×

Strickland dvclub

321

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
321
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Strickland dvclub"

  1. 1. Efficiency Through Methodology DV Club RTP Mark Strickland October 18, 2006 © 2006 Cisco Systems, Inc. All rights reserved. 1
  2. 2. Challenge of Verification Quality Schedule (all bugs found) and Resources DV Club Oct. 2006 © 2006 Cisco Systems, Inc. All rights reserved. 2
  3. 3. How to Meet the Challenge • Efficiency – get the most from your time Use components from other projects Don't specify behavior twice in the same project methodology Don't specify standard behavior that can be inferred at instantiation Provide flexibility to meet all late-stage needs Let automation do a lot of the work Eliminate decisions regarding infrastructure language Describe testbench concisely Run simulations faster DV Club Oct. 2006 © 2006 Cisco Systems, Inc. All rights reserved. 3
  4. 4. Some Examples Used at Cisco • A high-level overview of some reuse methodology techniques that we use at Cisco follows … DV Club Oct. 2006 © 2006 Cisco Systems, Inc. All rights reserved. 4
  5. 5. Three Stages of Testbench Creation • Component Design Want to describe the behavior of the component with minimal code to support the needs of the next stages • Testbench Integration Want to specify only components and interconnections, instance-specific constraints and initialization • Testcase Creation Want to specify only valid configuration space and sequences of constrained data (for the most part); everything else is a necessary evil May be done by those with shallower language knowledge DV Club Oct. 2006 © 2006 Cisco Systems, Inc. All rights reserved. 5
  6. 6. Testflow • The Issue: Sometimes all components must finish an activity (e.g. reset) before any of them moves on • Solution: A built-in testflow –Testcase specifies unique behavior for each phase –Testbench integration specifies standard behavior for each phase –Component starts processes in appropriate phase –None of these has to worry about synchronization of behavior between components DV Club Oct. 2006 © 2006 Cisco Systems, Inc. All rights reserved. 6
  7. 7. Unit-Level Benches and Reuse • Unit-level benches offer best control of stimulus and visibility of results • Reuse of unit-level checkers avoids creating new chip-level checkers that could be complex in cases such as dropped packets • Problem: Specification inconsistencies between two blocks can be missed Block A Block B to reset B, reset if 11 send 10 received Scenario: A tries to reset B 10 is sent no reset of B checker A checker B DV Club Oct. 2006 © 2006 Cisco Systems, Inc. All rights reserved. 7
  8. 8. Transaction Linking • Each checker that corresponds to a block that passes information to the next block contributes to building a linked list of the information hops • Each checker where information terminates (with some effect) traverses the linked list to find the source and the intent at that source Transaction linking is also a great debug aid DV Club Oct. 2006 © 2006 Cisco Systems, Inc. All rights reserved. 8
  9. 9. Templates and Generators • Burden falls on the component designer • The infrastructure of components can be made in a common manner • This commonality can be captured in templates and generators, allowing the designer to focus on the particulars of the component DV Club Oct. 2006 © 2006 Cisco Systems, Inc. All rights reserved. 9
  10. 10. Summary • Biggest efficiency gains from methodology – If code was in the same language but did not include testflow, transaction linking, and the testcase / integration / component separation, it would not help much if at all • Push most behavior into the components that can be used by many testbenches which in turn can be used by many tests • Make the component designer's job easier by standardizing common pieces into templates DV Club Oct. 2006 © 2006 Cisco Systems, Inc. All rights reserved. 10
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×