Transcript Lectures 15: System Diagnosis

VLSI Testing
Lecture 15: System Diagnosis
Dr. Vishwani D. Agrawal
James J. Danaher Professor of Electrical and
Computer Engineering
Auburn University, Alabama 36849, USA
[email protected]
http://www.eng.auburn.edu/~vagrawal
IIT Delhi, Aug 26, 2013, 3:30-4:30PM
Copyright 2001, Agrawal & Bushnell
Lecture 15: System Test
1
VLSI Testing
Lecture 14: System Diagnosis





Definition
Functional test
Diagnostic test
 Fault dictionary
 Diagnostic tree
System design-for-testability (DFT) architecture
 System partitioning
 Core test-wrapper
 DFT overhead
Summary
Copyright 2001, Agrawal & Bushnell
Lecture 15: System Test
2
A System and Its Testing


A system is an organization of components
(hardware/software parts and subsystems) with capability to
perform useful functions.
Functional test verifies integrity of system:




Checks for presence and sanity of subsystems
Checks for system specifications
Executes selected (critical) functions
Diagnostic test isolates faulty part:



For field maintenance isolates lowest replaceable unit (LRU),
e.g., a board, disc drive, or I/O subsystem
For shop repair isolates shop replaceable unit (SRU), e.g., a
faulty chip on a board
Diagnostic resolution is the number of suspected faulty units
identified by test; fewer suspects mean higher resolution
Copyright 2001, Agrawal & Bushnell
Lecture 15: System Test
3
System Test Applications
Application
Functional test
Diagnostic test
Resolution
A
Manufacturing
Yes
LRU, SRU
Maintenance
Yes
Field repair
LRU
Shop repair
SRU
LRU: Lowest replaceable unit
SRU: Shop replaceable unit
Copyright 2001, Agrawal & Bushnell
Lecture 15: System Test
4
Functional Test




All or selected (critical) operations executed with
non-exhaustive data.
Tests are a subset of design verification tests (testbenches).
Software test metrics used: statement, branch and
path coverages; provide low (~70%) structural
hardware fault coverage.
Examples:


Microprocessor test – all instructions with random data
(David, 1998).
Instruction-set fault model – wrong instruction is
executed (Thatte and Abraham, IEEETC-1980).
Copyright 2001, Agrawal & Bushnell
Lecture 15: System Test
5
Gate-Level Diagnosis
Karnaugh map
Logic circuit
(shaded squares are true outputs)
b
a
d
b
c
e
T2
a
Stuck-at fault tests:
T1 = 010
T2 = 011
T3 = 100
T4 = 110
Copyright 2001, Agrawal & Bushnell
Lecture 15: System Test
T1
T4
T3
c
6
Gate Replacement Fault
Karnaugh map
Faulty circuit
(faulty output:
red sqaure is 1 output)
(OR replaced by AND)
a
b
d
b
c
e
T2
a
Stuck-at fault tests:
T1 = 010 (pass)
T2 = 011 (fail)
T3 = 100 (pass)
T4 = 110 (fail)
Copyright 2001, Agrawal & Bushnell
Lecture 15: System Test
T1
T4
T3
c
7
Bridging Fault
Faulty circuit
Karnaugh map
(OR bridge: a, c)
a
b
c
(red squares are faulty 1 outputs)
b
a+c
d
e
a+c
T2
a
Stuck-at fault tests:
T1 = 010 (pass)
T2 = 011 (pass)
T3 = 100 (fail)
T4 = 110 (pass)
Copyright 2001, Agrawal & Bushnell
Lecture 15: System Test
T1
T4
T3
c
8
Fault Dictionary
Fault
Test syndrome
t1
t2
t3
t4
No fault
0
0
0
0
a0, b0, d0
0
0
0
1
a1
1
0
0
0
b1
0
0
1
0
c0
0
1
0
0
c1, d1, e1
1
0
1
0
e0
0
1
0
1
Copyright 2001, Agrawal & Bushnell
Lecture 15: System Test
a0 : Line a stuckat-0
ti = 0, if Ti passes
= 1, if Ti fails
9
Diagnosis with Dictionary
Dictionary look-up with minimum Hamming distance
Fault
OR
AND
OR-bridge (a,c)
OR
NOR
Copyright 2001, Agrawal & Bushnell
Test syndrome
t1
t2
t3
t4
Diagnosis
0
1
0
1
e0
0
0
1
0
b1
1
1
1
1
Lecture 15: System Test
c1, d1, e1, e0
10
Diagnostic Tree
T3
T2
Pass: t4=0
a1
T3
a1, c1, d1, e1
T4
Fail: t4=1
c0
T1
T2
a0, b0, d0, e0
Copyright 2001, Agrawal & Bushnell
No fault
found
b1
OR bridge
(a,c)
c1, d1, e1
a0, b0, d0
e0
OR
AND
OR
NOR
Lecture 15: System Test
11
System Test: PCB vs. SOC
PCB*






SOC**
Tested parts
In-circuit test (ICT)
Easy test access
Bulky
Slow
High assembly cost






High reliability
Fast interconnects
Low cost
Untested cores
No internal test access
Mixed-signal devices
* Printed circuit board
** System on a chip
Copyright 2001, Agrawal & Bushnell
Lecture 15: System Test
12
Core-Based Design



Cores are predesigned and verified but untested
blocks:
 Soft core (synthesizable RTL)
 Firm core (gate-level netlist)
 Hard core (non-modifiable layout, often called
legacy core)
Core is the intellectual property of vendor
(internal details not available to user.)
Core-vendor supplied tests must be applied to
embedded cores.
Copyright 2001, Agrawal & Bushnell
Lecture 15: System Test
13
Partitioning for Test



Partition according to test methodology:
 Logic blocks
 Memory blocks
 Analog blocks
Provide test access:
 Boundary scan
 Analog test bus
Provide test-wrappers (also called collars) for
cores.
Copyright 2001, Agrawal & Bushnell
Lecture 15: System Test
14
Test-Wrapper for a Core


Test-wrapper (or collar) is the logic added around a core to
provide test access to the embedded core.
Test-wrapper provides:
 For each core input terminal



A normal mode – Core terminal driven by host chip
An external test mode – Wrapper element observes core input
terminal for interconnect test
An internal test mode – Wrapper element controls state of core
input terminal for testing the logic inside core
 For each core output terminal



A normal mode – Host chip driven by core terminal
An external test mode – Host chip is driven by wrapper element
for interconnect test
An internal test mode – Wrapper element observes core outputs
for core test
Copyright 2001, Agrawal & Bushnell
Lecture 15: System Test
15
A Test-Wrapper
from/to
External
Test pins
Scan chain
to/from TAP
Copyright 2001, Agrawal & Bushnell
Lecture 15: System Test
Functional
core outputs
Core
Scan chain
Scan chain
Functional
core inputs
Wrapper
elements
Wrapper
test
controlle
r
16
Overhead of Test Access




Test access is non-intrusive.
Hardware is added to each I/O signal of
block to be tested.
Test access interconnects are mostly
local.
Hardware overhead is proportional to:
(Block area)
Copyright 2001, Agrawal & Bushnell
– 1/2
Lecture 15: System Test
17
Overhead Estimate
Rent’s rule: For a logic block the number of gates G
and the number of terminals t are related by
t = K Ga
where 1 ≤ K ≤ 5, and a ~ 0.5.
Assume that block area A is proportional to G, i.e.,
t is proportional to A 0.5. Since test logic is added
to each terminal t,
Test logic added to terminals
Overhead = ─────────────────────── ~ A –0.5
A
Copyright 2001, Agrawal & Bushnell
Lecture 15: System Test
18
DFT Architecture for SOC
Module
N
wrapper
1
Func.
outputs
Func.
inputs
Test
Module
wrapper
Functional
inputs
User defined test access mechanism (TAM)
Test
Test
source
Test
sink
Functional
outputs
Instruction register control
Copyright 2001, Agrawal & Bushnell
Lecture 15: System Test
TDO
TRST
TMS
TCK
SOC inputs
Test access port (TAP)
TDI
Serial instruction data
SOC outputs
19
DFT Components




Test source: Provides test vectors via on-chip LFSR,
counter, ROM, or off-chip ATE.
Test sink: Provides output verification using on-chip
signature analyzer, or off-chip ATE.
Test access mechanism (TAM): User-defined test data
communication structure; carries test signals from source
to module, and module to sink; tests module interconnects
via test-wrappers; TAM may contain bus, boundary-scan
and analog test bus components.
Test controller: Boundary-scan test access port (TAP);
receives control signals from outside; serially loads test
instructions in test-wrappers.
Copyright 2001, Agrawal & Bushnell
Lecture 15: System Test
20
Summary



Functional test: verify system hardware, software, function
and performance; pass/fail test with limited diagnosis; high
(~100%) software coverage metrics; low (~70%) structural
fault coverage.
Diagnostic test: High structural coverage; high diagnostic
resolution; procedures use fault dictionary or diagnostic
tree.
SOC design for testability:





Partition SOC into blocks of logic, memory and analog
circuitry, often on architectural boundaries.
Provide external or built-in tests for blocks.
Provide test access via boundary scan and/or analog test
bus.
Develop interconnect tests and system functional tests.
Develop diagnostic procedures.
Copyright 2001, Agrawal & Bushnell
Lecture 15: System Test
21