Functional Verification

1. Functional Verification Figure 1.1 p 6 • Detection of errors in the design • Before fab for design errors, after fab for physical errors

2. Design Error, Traffic Light Controller Figure 1.2 p 8 Figure 1.3 p 9 • Design may not match specification • Design (and spec) may not match intent Example: Elm St. light may starve is Main St. has traffic

3. General Verification Approaches Simulation-Based - Simulate the design with test stimuli and check the results • Only a small part of the space can be explored • Hard to tell if testing is sufficient Formal Verification - Proving facts about the design • Model checking, Equivalence checking • Time and space issues • Hard to tell if properties are complete

4. Functional Verification Challenges State Space Size - Capturing state can consume space and exploring state space consumes time Test Generation - Generating input sequences to reveal errors Response Analysis - Checking the results to see that they are correct

5. State Space Size 232 colors 1024 x 768 pixels Fig 1.5, p 11 • Pressing a button superimposes name on the screen • Must consider screen state as well • Total states = 5 * 232 * 1024 * 768 = 16,888,498,602,639,360

6. Test Generation/ Response Analysis Table 1.1, p13 • Test gen and analysis depends on the design

7. Test and Response Options Microprocessor • Functional-Based Stimulus - Instruction stream loaded into memory • Result Validation - Do the resulting registers have the correct values after each instruction? Digital Video Converter • Functional-Based Stimulus - Streaming encoded video • Result Validation - Does the video appear correctly on a monitor? • How do you test internal components (forwarding, DCT)?

8. Costs of Testing • Schedule (Time-to-Market) - Release your product before your competition • Paying Engineers - Could be working on another project • Test Hardware Purchase/Maintainance - • Machines to run simulation/debug • May need special test fixtures to model environment • Quality Requirements - • Cost of recall • Loss of life/money

9. Cost of Errors During Lifetime Fig 1.7, p 17 • The cost of undetected problems grows over time

10. Verification Cycle • Start with a functional specification • Verification partially in parallel with design process • Big cycle involves learning from previous designs Fig 1.9, p 25

11. Functional Specification • A natural language description of the functionality • Hard to define, varies based on design style • Defines I/O behavior without implementation detail • May include timing diagrams, UML, scenarios, etc. • Ambiguous and Incomplete - All natural languages are ambiguous. • Ambiguity is resolved during design • Specification is generally not executable • Cannot be understood by an automatic tool

12. Verification Plan • A plan for organizing the verification process • Abstract, no testing details • Includes required tools, completion criteria, resources, functions to be verified, etc. • Used to manage the process

13. Develop Environment Write code and setup tools used to perform testing Write testbench to generate test stimuli Define assertions to check responses Define reference model to compare responses Determine when and where to sample values

14. Debug and Regression • Perform simulation, debug the HDL and the environment • Regression - Continuous running of tests in verification plan • Randomness in tests • Design modifications

15. System Test and Escape Analysis • Apply tests to the real system • Fast, but bad observability • Captures effects not modeled by a simulator • Determine why simulation missed bugs • Reproduce bugs in simulation • Good for future designs