CMOS Testing: Part 1krish/teaching/Lectures/Testing.1.pdfCMOS Testing: Part 1 • Introduction •...

18
1 ECE 261 Krish Chakrabarty 1 CMOS Testing: Part 1 • Introduction Fault models Stuck-line (single and multiple) – Bridging – Stuck-open Test pattern generation Combinational circuit test generation Sequential circuit test generation ECE 261 Krish Chakrabarty 3 Outline Testing Logic Verication Silicon Debug Manufacturing Test Fault Models Observability and Controllability Design for Test – Scan – BIST Boundary Scan

Transcript of CMOS Testing: Part 1krish/teaching/Lectures/Testing.1.pdfCMOS Testing: Part 1 • Introduction •...

1

ECE 261 Krish Chakrabarty 1

CMOS Testing: Part 1• Introduction

• Fault models– Stuck-line (single and multiple)

– Bridging

– Stuck-open

• Test pattern generation– Combinational circuit test generation

– Sequential circuit test generation

ECE 261 Krish Chakrabarty 3

Outline• Testing

– Logic Verification

– Silicon Debug

– Manufacturing Test

• Fault Models

• Observability and Controllability

• Design for Test– Scan

– BIST

• Boundary Scan

2

ECE 261 Krish Chakrabarty 4

Testing

• Testing is one of the most expensive parts of chips– Logic verification accounts for > 50% of design effort

for many chips

– Debug time after fabrication has enormous cost

– Shipping defective parts can sink a company

• Example: Intel FDIV bug– Logic error not caught until > 1M units shipped

– Recall cost $450M (!!!)

ECE 261 Krish Chakrabarty 5

Logic Verification

• Does the chip simulate correctly?– Usually done at HDL level

– Verification engineers write test bench for HDL

• Can’t test all cases

• Look for corner cases

• Try to break logic design

• Ex: 32-bit adder– Test all combinations of corner cases as inputs:

• 0, 1, 2, 231-1, -1, -231, a few random numbers

• Good tests require ingenuity

3

ECE 261 Krish Chakrabarty 6

Silicon Debug

• Test the first chips back from fabrication– If you are lucky, they work the first time– If not…

• Logic bugs vs. electrical failures– Most chip failures are logic bugs from inadequate simulation– Some are electrical failures

• Crosstalk• Dynamic nodes: leakage, charge sharing• Ratio failures

– A few are tool or methodology failures (e.g. DRC)

• Fix the bugs and fabricate a corrected chip

ECE 261 Krish Chakrabarty 7

Shmoo Plots

• How to diagnose failures?– Hard to access chips

• Picoprobes

• Electron beam

• Laser voltage probing

• Built-in self-test

• Shmoo plots– Vary voltage, frequency

– Look for cause of

electrical failures

4

ECE 261 Krish Chakrabarty 8

Need for Testing• Physical defects are likely in manufacturing

– Missing connections (opens)– Bridged connections (shorts)– Imperfect doping, processing steps– Packaging

• Yields are generally low– Yield = Fraction of good die per wafer

• Need to weed out bad die before assembly• Need to test during operation

– Electromagnetic interference, mechanical stress, electromigration, alpha particles

ECE 261 Krish Chakrabarty 9

Manufacturing Test• A speck of dust on a wafer is sufficient to kill chip• Yield of any chip is < 100%

– Must test chips after manufacturing before delivery to customers to only ship good parts

• Manufacturing testers are very expensive– Minimize time on tester– Careful selection of

test vectors

5

ECE 261 Krish Chakrabarty 10

Testing Your Chips• If you don’t have a multimillion dollar tester:

– Build a breadboard with LED’s and switches

– Hook up a logic analyzer and pattern generator

– Or use a low-cost functional chip tester

Motivation for Testing: XBox 360 Technical Problems

• The "Red Ring of Death": Three red lights on the Xbox 360 indicator, representing "general hardware failure” (http://en.wikipedia.org/wiki/3_Red_Lights_of_Death)

• The Xbox 360 can be subject to a number of possible technical problems. Since the Xbox 360 console was released in 2005 the console gained reputation in the press in articles portraying poor reliability and relatively high failure rates.

• On 5 July 2007, Peter Moore published an open letter recognizing the problem and announcing 3 years warranty expansion for every Xbox 360 console that experiences the general hardware failure indicated by the three flashing red lights on the console.

6

XBox 360 Technical Problems and Test-Cost Projections

• July 5, 2007, Xbox issues to cost Microsoft $1 billion-plus. Unacceptable number of repairs leads to company extending warranties.

• Matt Rosoff, an analyst at the independent research group Directions on Microsoft, estimates that Microsoft’s entertainment and devices division has lost more than $6 billion since 2002.

ITRS

Test cost

Manufacturingcost

Cost of Test• “The emergence of more advanced ICs and SOC semiconductor devices is

causing test costs to escalate to as much as 50 percent of the total manufacturing cost.”– M. Kondrat, “Bridging design and ATE cuts test cost - Test & Measurement -

automatic test equipment”, Electronic News, Sept 9, 2002.

• “As a result, semiconductor test cost continues to increase in spite of the introduction of DFT, and can account for up to 25-50% of total manufacturing cost”. – T. Cooper, G. Flynn, G. Ganesan, R. Nolan, C. Tran, Motorola,

“Demonstration and Deployment of a Test Cost Reduction Strategy Using Design-for-Test (DFT) and Wafer Level Burn-In and Test”, (6/29/2001) Future Fab Intl. Volume 11.

• “Test may account for more than 70% of the total manufacturing cost - test cost does not directly scale with transistor count, dies size, device pin count, or process technology”, ITRS 2003.

7

Motivation for Testing• billion+

• Rule of Ten

Chip x1

Board System x100 x10

Cost escalates rapidly

Some Real Defects in ChipsProcessing defects

Missing contact windowsParasitic transistorsOxide breakdown . . .

Material defectsBulk defects (cracks, crystal imperfections)Surface impurities (ion migration). . .

Time-dependent failuresDielectric breakdownElectromigration. . .

Packaging failuresContact degradationSeal leaks. . .

8

ECE 261 Krish Chakrabarty 16

Testing Levels and Test Costs

• Wafer

• Packaged chip

• Board

• System

• Field

• Concurrent checking

• Cost to detect a fault (per chip)– Wafer: $0.01-$0.1

– Packaged chip: $0.1-$1– Board: $1-$10

– System: $10-$100

– Field: $100-1000

ECE 261 Krish Chakrabarty 17

Manufacturing TestingGoal: Detect manufacturing detects

Defects: layer-to-layer shorts discontinuous wires thin-oxide shorts to substrate or well

Faults: nodes shorted to power or ground (stuck-at) nodes shorted to each other (bridging) inputs floating, outputs disconnected (stuck-open)

Faultmodels

9

ECE 261 Krish Chakrabarty 18

Testing : The Buzzwords

• Errors– Permanent

– Intermittent

– Transient

• Faults– Physical

– Logical

• Test Evaluation– Fault coverage– Fault simulation

• Types of testing– Off-line, on-line

– Self-test vs external test

– DC (static) vc AC (at-speed)

– Edge-pin, guided-probe, bed-of-nails, E-beam, in-circuit

ECE 261 Krish Chakrabarty 19

Testing and Diagnosis

• Testing: Determine if the system (chip, board) is behaving correctly

• Diagnosis: Locate the cause of malfunctioning

10

ECE 261 Krish Chakrabarty 20

Testing and DiagnosisDesign

Fabrication(Physical defects)

Test patterngeneration(Fault model)

Wafer, IC, board

Test Equipment

0010010110

Pass Fail

RejectDiagnosis,repair

ECE 261 Krish Chakrabarty 21

Testing: The Inevitable Acronyms

• System under test– UUT: Unit Under Test

– CUT: Circuit Under Test

– DUT: Device Under Test

• The tester– ATE: Automatic Test

Equipment

• Test generation– ATPG: Automatic Test

Pattern Generation

• Fault Models– SSL: Single Stuck-Line

– MSL: Multiple Stuck-Line

– BF: Bridging Fault

• DFT: Design for Testability– BIST: Built-in self-test

– LFSR:Linear-Feedback Shift-Register

11

ECE 261 Krish Chakrabarty 22

Fault Models• Defects are too many and too difficult to explicitly

enumerate• Abstraction (technology independence): presence of

physical defect is modeled by changing the logic function (or delay)

• Reduced complexity: distinct physical defects may be represented by the same logical fault

• Generality: tests derived for logical faults may detect vaguely-understood or hard-to-analyze physical defects

• A test pattern detects a fault from the fault model

ECE 261 Krish Chakrabarty 23

Single Stuck-Line (SSL) Model• A single node in the circuit is stuck-at 1 (s-a-1) or 0 (s-a-0).

A

DC

Bz

s-a-0

Fault-free function z = AB+CDFaulty function zf = AB

A

DC

Bz

s-a-1

Fault-free function z = AB+CDFaulty function zf = AB+D

Number of possible stuck-at faults in a circuit with n lines?

Number of faults reduced by finding equivalent classes

12

ECE 261 Krish Chakrabarty 24

Stuck-At Faults

• How does a chip fail?– Usually failures are shorts between two conductors or

opens in a conductor

– This can cause very complicated behavior

• A simpler model: Stuck-At– Assume all failures cause nodes to be “stuck-at” 0 or 1,

i.e. shorted to GND or VDD

– Not quite true, but works well in practice

ECE 261 Krish Chakrabarty 25

Examples

13

ECE 261 Krish Chakrabarty 26

D: 1/0, D: 0/1

SSL Fault Detection• A test pattern for fault x s-a-d is an input combination that

1) places d on x (activation), 2) propagates fault effect (D or D) to primary output

A

EC

Bz

s-a-0

Good circuitBad circuit

ABCE = 0011 is a test pattern for C s-a-0

ECE 261 Krish Chakrabarty 27

Multiple Stuck-Line (MSF) Faults

• More than one line may be stuck at a logic valueA

DC

Bz

s-a-0

s-a-1

Fault: {C s-a-0, x s-a-1}

x

How many MSL fault can there be in a circuit with n nodes?

How to get test patterns for MSL faults?

Fault universe is too large, MSL fault model seldom used, especially since tests for SSL faults cover many MSL faults

14

ECE 261 Krish Chakrabarty 28

Observability & Controllability

• Observability: ease of observing a node by watching external output pins of the chip

• Controllability: ease of forcing a node to 0 or 1 by driving input pins of the chip

• Combinational logic is usually easy to observe and control

• Finite state machines can be very difficult, requiring many cycles to enter desired state– Especially if state transition diagram is not known to the test

engineer

ECE 261 Krish Chakrabarty 29

Test Pattern Generation

• Manufacturing test ideally would check every node in the circuit to prove it is not stuck.

• Apply the smallest sequence of test vectors necessary to prove each node is not stuck.

• Good observability and controllability reduces number of test vectors required for manufacturing test.– Reduces the cost of testing

– Motivates design-for-test

15

ECE 261 Krish Chakrabarty 30

Test Pattern Generation• Exhaustive testing: Apply 2n pattern to n-input circuit• Not practical for large n• Advantage: Fault-model independent

A

DC

B

s-a-0

Fault-Oriented Test Generation Algorithm:

x

yz

1) Set x to 1: activate fault2) Justify D on x, propagate D to z

Set C and D to 1 Set y to 0

Set either A or B to 0Example test pattern: ABCD = 0011• Backtracking may be necessary• Test generation is NP-complete

ECE 261 Krish Chakrabarty 31

Test ExampleSA1 SA0

• A3 {0110} {1110}• A2 {1010} {1110}• A1 {0100} {0110}• A0 {0110} {0111}• n1 {1110} {0110}• n2 {0110} {0100}• n3 {0101} {0110}• Y {0110} {1110}

• Minimum set: {0100, 0101, 0110, 0111, 1010, 1110}

16

ECE 261 Krish Chakrabarty 32

Bridging Faults• Models short circuits, pairs of nodes considered

• Number of bridging faults?

• Feedback vs non-feedback bridging faults

A

B z

bridgeA B z zf Wired-AND Wired-OR0 0 0 0 0 00 1 0 ? 0 11 0 1 ? 0 11 1 1 1 1 1

What are the test patterns in this example?

zf = ?

ECE 261 Krish Chakrabarty 33

Stuck-Open Faults

Gnd

VDD

a b

a

b

z

Floating nodeFault-free circuit: z = a+bFaulty circuit: zf = a+b + abz~

~z: Previous value of z

Case 1: a = b = 1, z pulled down to 0Case 2: a = 1, b =0, z retains previous state

A test for a stuck-open fault requires two patterns{ab = 00, ab = 10}

17

ECE 261 Krish Chakrabarty 34

Sequential Circuit Test Generation

Combinational

logic

Registers

Primary

inputs

Primary

outputs

(controllable) (observable)

State outputs

(not observable) State inputs

(not controllable) m

n

• Difficult problem!• Exhaustive testing requires 2m+n patterns (2m states and 2n

transitions from each state)• Every fault requires a sequence of patterns

Initializing sequence: drive to known stateTest activationPropagation sequence: propagate discrepancy to observable output

ECE 261 Krish Chakrabarty 35

Sequential Circuit Test Generation

• Iterative-array model (pseudo-combinational circuit)

A

C

B

x

yz

D Q

A

C

B

x

yz

y

y+

18

ECE 261 Krish Chakrabarty 36

Sequential Circuit Test Generation

A

C

B

x

yz

D Q

A

C

B

x

yz

y

y+

s-a-0

A

C

B

x

yz

y

y+

D1D

1

1

010

Assume initial stateof flip-flop is notknown

11

ABC = 11X ABC = 011

Backward traversalin time

Current time frameTest pattern sequence: {11X, 011}

ECE 261 Krish Chakrabarty 37

Summary

• Think about testing from the beginning– Simulate as you go

– Plan for test after fabrication

• “If you don’t test it, it won’t work! (Guaranteed)”