Week 13 - Verification and Test
Week 13 - Verification and Test
1
Verification
2
Types of tests
A typical test suite may involve 109 or more test patterns. – definitely cannot
look through all the results manually to see if they are correct.
• A common approach is to compare our design (cycle-level timing) to a
higher level model (transaction-level) of the same function.
3
Static timing analysis
With static timing analysis, all paths are checked without the need to
generate ___________.
The limitation of static timing analysis is that it often report issues on paths
that are guaranteed never to be used.
4
Formal verification
5
Bug tracking
#bugs
time
The majority of bugs are closed quickly, within one day. However, a small
fraction of difficult bugs remain open for a week or more.
6
Summary
7
Verification and Test - Test
8
Test
9
Fault model: Stuck at 0/1 at q
10
Combinational testing
11
Testing redundant logic
Stuck-at-0 at Q3?
12
Verification and Test – Design for testability
13
Scan
1. Scan-in
2. Run
3. Scan-out
14
Built-in-self-test (BIST) for RAM
1 3
2
4
1 → 2, 3, 2, 3, .... → 4
15
Built-in-self-test (BIST) for logic
Pseudo-random
sequence generator
16
Characterization
17
Summary
18