integrating physical test into the ic studio workflow

30
Integrating Physical Test into the IC Studio Workflow Harry Peterson Senior Director of IC Technology Pixelworks Inc Co-authors: Angus Tang Marc Ranger

Upload: edythe

Post on 18-Jan-2016

49 views

Category:

Documents


0 download

DESCRIPTION

Integrating Physical Test into the IC Studio Workflow. Harry Peterson Senior Director of IC Technology Pixelworks Inc Co-authors: Angus Tang Marc Ranger. Introduction. Trends: What we can build is limited by our ability to manage complexity Co-design is everywhere - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Integrating Physical Test into the IC Studio Workflow

Integrating Physical Test into the IC Studio Workflow

Harry Peterson

Senior Director of IC Technology

Pixelworks Inc

Co-authors:

Angus Tang

Marc Ranger

Page 2: Integrating Physical Test into the IC Studio Workflow

HWP, Integrating Physical Test into the IC Studio Workflow, March 2007

2

Introduction

■ Trends:— What we can build is limited by our ability to manage

complexity— Co-design is everywhere— Schedules keep shrinking— Interaction among disciplines becomes tighter— Simulators are more powerful— ATE becomes relatively more expensive

■ Focus of this presentation:— Methodology for co-design of test program and mixed-

signal chip

Page 3: Integrating Physical Test into the IC Studio Workflow

HWP, Integrating Physical Test into the IC Studio Workflow, March 2007

3

Objective: Minimize Time to (Profitable) Revenue

■ We must produce first-time-right mixed-signal designs that are testable and cost-effective.

■ At the same time, we must deliver first-time-right test capability that is comprehensive and cost-effective.

Page 4: Integrating Physical Test into the IC Studio Workflow

HWP, Integrating Physical Test into the IC Studio Workflow, March 2007

4

The Idea

■ Create two views for the testbench:— Virtual— Physical

■ By making it easy to flip between these two representations, we speed up the development and verification of mixed-signal test programs.

Page 5: Integrating Physical Test into the IC Studio Workflow

HWP, Integrating Physical Test into the IC Studio Workflow, March 2007

5

Methodology

■ Instantiate both the physical and virtual view of the testbench.

■ Create a pipe between these views.■ Use views interchangeably in order to

validate and optimize both.

Page 6: Integrating Physical Test into the IC Studio Workflow

HWP, Integrating Physical Test into the IC Studio Workflow, March 2007

6

Testbench, in the virtual world

■ Resources for generating stimuli:— Dozens of types of signal generators exist— For this session, we just look at PWL and

PULSE■ Resources for analyzing responses:

— EZWave— Third-party (Kimotion) software mines data so

that we can automate regression tests— Custom scripts bridge the gap between

Simulation software and ATE software

Page 7: Integrating Physical Test into the IC Studio Workflow

HWP, Integrating Physical Test into the IC Studio Workflow, March 2007

7

Testbench, in the real (ATE) world

■ Resources for generating stimuli:— AWG (Arbitrary Waveform Generator) — Pin Driver— Other

■ Resources for analyzing responses:— Waveform digitizer— Comparator

■ Other resources:— Active load— Active and passive circuits on load board or probe card

Page 8: Integrating Physical Test into the IC Studio Workflow

HWP, Integrating Physical Test into the IC Studio Workflow, March 2007

8

EDA Tool Selection

■ Why we chose ADMS:— Allows us to efficiently move between accurate

transistor-level analysis and fast top-level analysis.

— Efficient■ Why we chose IC studio:

— Good schematic-capture— Gracefully accommodates a variety of other

views and resources— Open

Page 9: Integrating Physical Test into the IC Studio Workflow

HWP, Integrating Physical Test into the IC Studio Workflow, March 2007

9

ATE Resource Selection

■ Credence D10— Powerful mixed-signal capability— Good analog performance— Open C++ style programming interface— Well-suited to characterization as well as to

production testing— Low cost

Page 10: Integrating Physical Test into the IC Studio Workflow

HWP, Integrating Physical Test into the IC Studio Workflow, March 2007

10

Test Generation Methodology / Digital

■ Digital designers figured this out long ago.■ But their problem was simpler:

— Simply translate simulation data files into test vectors for ATE tester

■ Examples of such vector translation tools:— VTRAN— V2SCO

Page 11: Integrating Physical Test into the IC Studio Workflow

HWP, Integrating Physical Test into the IC Studio Workflow, March 2007

11

Test Generation Methodology (Mixed-signal)

■ Transfer of simulation data to tester program is largely a manual process.

■ We need a more automatic transfer mechanism.■ The concepts have been considered, but have not yet

been widely integrated into the workflow.■ References:

— [1] Viekko Loukusa. “Behavioral Test Generation Modeling Approach for Mixed-signal IC Verification,” Proceedings of International Mixed-Signal Testing Workshop 2002

— [2] Geert Seuren, et al, “Extending the Digital Core-Based Test Methodology to Support Mixed-Signal,” Proceedings of International Test Conference, 2004

Page 12: Integrating Physical Test into the IC Studio Workflow

HWP, Integrating Physical Test into the IC Studio Workflow, March 2007

12

Enabling technology for mixed-signal test

ICStudio ■ An integrated, user-friendly environment ■ Create, manage, and simulate design at

different levels of abstractions (Spice, schematics, HDL)

■ Facilitates behavioral modeling and mixed-level simulation

Page 13: Integrating Physical Test into the IC Studio Workflow

HWP, Integrating Physical Test into the IC Studio Workflow, March 2007

13

Approach

■ Create top-level testbench to verify design in simulation.

■ Top-level simulation is made possible through the use of behavioral models.

■ The test bench is then used to generate the main components of the ATE test program, these includes the test vectors and tester instrument setups.

Page 14: Integrating Physical Test into the IC Studio Workflow

HWP, Integrating Physical Test into the IC Studio Workflow, March 2007

14

Case Study: video AFE

■ Consists of the following blocks:— Signal pre-conditioning

■ Input buffers■ Clamps■ Gain/Offset DAC

— Three fast ADCs ■ 10-bit resolution■ 162MSPS

— Timing recovery circuit■ Line-locked PLL

Page 15: Integrating Physical Test into the IC Studio Workflow

HWP, Integrating Physical Test into the IC Studio Workflow, March 2007

15

DUT and the Simulation Testbench /1

ADC under Test

Spice & Verilog AMS

Digital stimulusVerilog

Analog stimulusVerilog AMS

Monitors

t

Page 16: Integrating Physical Test into the IC Studio Workflow

HWP, Integrating Physical Test into the IC Studio Workflow, March 2007

16

DUT and the Simulation Testbench /2

■ The top-level testbench allows us to characterize the ADC and extract important performance parameters such as INL, DNL, and ENOB.

ADC under Test

Spice & Verilog AMS

Digital stimulusVerilog

Analog stimulusVerilog AMS

Monitors

t

Page 17: Integrating Physical Test into the IC Studio Workflow

HWP, Integrating Physical Test into the IC Studio Workflow, March 2007

17

DUT and the Simulation Testbench /3■ The digital stimulus block generates the

necessary clock and control signals to the ADC.■ Digital stimuli are implemented as a Verilog

block.

ADC under Test

Spice & Verilog AMS

Digital stimulusVerilog

Analog stimulusVerilog AMS

Monitors

t

Page 18: Integrating Physical Test into the IC Studio Workflow

HWP, Integrating Physical Test into the IC Studio Workflow, March 2007

18

DUT and the Simulation Testbench /4

■ The analog stimulus block generates a ramp signal so that the output of the ADC can be measured for linearity. Analog stimuli are modeled behaviorally in Verilog AMS.

ADC under Test

Spice & Verilog AMS

Digital stimulusVerilog

Analog stimulusVerilog AMS

Monitors

t

Page 19: Integrating Physical Test into the IC Studio Workflow

HWP, Integrating Physical Test into the IC Studio Workflow, March 2007

19

Case Study: video AFE

Page 20: Integrating Physical Test into the IC Studio Workflow

HWP, Integrating Physical Test into the IC Studio Workflow, March 2007

20

■ The digital stimuli are translated into test vectors in ATE tester format.

■ The digital module of the D10 tester accepts test vectors in STIL format, which can be readily generated from simulation.

Mapping the simulation testbench to the ATE testbench /1

Page 21: Integrating Physical Test into the IC Studio Workflow

HWP, Integrating Physical Test into the IC Studio Workflow, March 2007

21

Mapping the simulation testbench to the ATE testbench /2

Analog stimulusVerilog AMS

t

v

. . .void AWG_setup(double amplitude, double offset, string signal...){ /*********************************** AWG SETUP ***************************************/ . . cscTester->AWG()->Signal(signal)->OutputCtrl()->setOptimization(OPTIMIZE_FOR_NOISE); cscTester->AWG()->Signal(signal)->OutputCtrl()->setAmplitude(amplitude); cscTester->AWG()->Signal(signal)->OutputCtrl()->setCommonOffset(offset); cscTester->AWG()->Signal(signal)->OutputCtrl()->setClockFrequency(awg_freq); cscTester->AWG()->Signal(signal)->WaveformCtrl()->setSource(AWG_WAVEFORM_MEMORY); cscTester->AWG()->Signal(signal)->WaveformCtrl()->setActiveWaveform(wfid); cscTester->AWG()->Signal(signal)->WaveformCtrl()->setWaveformRepeat(ULONG_MAX); . .} . .

Test_Bench_behavioral.va

. . .//ramp inputmodule single_ended_ramp (.amplitude(1.0), .offset(0.5)...) Ramp(Rin_0, VSSA); . . .

ADC_Test.cpp

Sapphire D-10AWG

Top-level Test Bench

Page 22: Integrating Physical Test into the IC Studio Workflow

HWP, Integrating Physical Test into the IC Studio Workflow, March 2007

22

Mapping the simulation testbench to the ATE testbench /3

■ Using the method described, the bulk of the ATE test program can be generated from the simulation testbench, before first silicon is available.

■ Test program development time and effort is reduced.

■ This flow bridges the communication gap between test engineers and designers.

Page 23: Integrating Physical Test into the IC Studio Workflow

HWP, Integrating Physical Test into the IC Studio Workflow, March 2007

23

Next steps

■ 1. Integrate the Kimotion ‘Breaker’ tool into this flow, in order to more tightly close the loop between ‘executable spec’ and verified Silicon.

■ 2. Adopt Mentor ‘Checkerboard’ tool in order to gain the efficiency and quality benefits of greater automation and faster simulation.

■ 3. Pull software development and validation into the co-design and product-verification loops.

■ 4. Integrate Yield Analysis and Product Engineering capabilities.

Page 24: Integrating Physical Test into the IC Studio Workflow

HWP, Integrating Physical Test into the IC Studio Workflow, March 2007

24

Next steps /1Use Kimotion ‘Breaker’ tool to help mine simulation data

so we can make specs more executable

Design variables Process and Environment

Performance models

Specifications

Optimized netlist Specification corners

EldoKtModelsAdvanceMS…

■ User-defined testbenches measure important circuit performances

■ Breaker exercises testbenches to find most likely and/or worst-case violations for each performance

Page 25: Integrating Physical Test into the IC Studio Workflow

HWP, Integrating Physical Test into the IC Studio Workflow, March 2007

25

Next steps /2Use Mentor ‘Checkerboard’ tool to greatly improve speed

and effectiveness of chip-level simulation

■ .Verification engineer traditionally has access to two types of block descriptions

Transistor-accurate netlistsslow, but capture all effects

Ideal behavioral models are fast, but modeling extra effects requires tuning

m4b

l={l4} w={w4} m={mout}

m4a

l={l4} w={w4} m={mout}

l={l2} w={w2} m={min}

m2b m2a

l={l2} w={w2} m={min}

m1a

l={l1} w={w1} m={min}

m1b

l={l1} w={w1} m={min}

m5a

l={l5} w={w5} m={mout}

m5b

l={l5} w={w5} m={mout}

m6a

l={l6} w={w6} m={mout}

m6b

l={l6} w={w6} m={mout}

m3b

l={l3} w={w3} m={mout+min}

m3a

l={l3} w={w3} m={mout+min}

C1

{cload}

C2

{cload}

X3vdd biasgbpvssinout

casgbpcasgbnbiasgbn

gainboostn

X4vdd biasgbpvssinout

casgbpcasgbnbiasgbn

gainboostn

X5vdd biasgbpvssinout

casgbpcasgbnbiasgbn

gainboostp

X6vdd biasgbpvssinout

casgbpcasgbnbiasgbn

gainboostp

X2

vdd biaspvssibiasbiasn2

caspcasnbiasn

BIASING

X7outpoutnref

reg

C3

{ccm}

C4

{ccm}

C5

{cgbn}

C6

{cgbn}

C7

{cgbp}

C8

{cgbp}

cmreg

n3a n3b

caspbcaspa

outn outp

outpoutn

cmout

inp inn

biasn2

vss

n2a

n2b

n1a

biasn2

vddvss

ibiasbiasn2 biasn

casncaspbiasp

casna casnb

vdd

biasp

vss vss

vdd vdd

outpoutn

vss

n3a

n3b

casna

casnb

vss

vssvdd

vdd

vssvdd

vssvdd

n2acaspa

n2bcaspb

biaspcaspcasnbiasn

biasp

biasp

biasp

caspcasnbiasn

caspcasnbiasn

caspcasnbiasn

outn outp

cmreg

vss vss

casna casnb

caspa caspb

vss

.param cload=2.5p

A

Checkerboard verification avoids the need for full spice simulation

m4b

l={l4} w={w4} m={mout}

m4a

l={l4} w={w4} m={mout}

l={l2} w={w2} m={min}

m2b m2a

l={l2} w={w2} m={min}

m1a

l={l1} w={w1} m={min}

m1b

l={l1} w={w1} m={min}

m5a

l={l5} w={w5} m={mout}

m5b

l={l5} w={w5} m={mout}

m6a

l={l6} w={w6} m={mout}

m6b

l={l6} w={w6} m={mout}

m3b

l={l3} w={w3} m={mout+min}

m3a

l={l3} w={w3} m={mout+min}

C1

{cload}

C2

{cload}

X3vdd biasgbpvssinout

casgbpcasgbnbiasgbn

gainboostn

X4vdd biasgbpvssinout

casgbpcasgbnbiasgbn

gainboostn

X5vdd biasgbpvssinout

casgbpcasgbnbiasgbn

gainboostp

X6vdd biasgbpvssinout

casgbpcasgbnbiasgbn

gainboostp

X2

vdd biaspvssibiasbiasn2

caspcasnbiasn

BIASING

X7outpoutnref

reg

C3

{ccm}

C4

{ccm}

C5

{cgbn}

C6

{cgbn}

C7

{cgbp}

C8

{cgbp}

cmreg

n3a n3b

caspbcaspa

outn outp

outpoutn

cmout

inp inn

biasn2

vss

n2a

n2b

n1a

biasn2

vddvss

ibiasbiasn2 biasn

casncaspbiasp

casna casnb

vdd

biasp

vss vss

vdd vdd

outpoutn

vss

n3a

n3b

casna

casnb

vss

vssvdd

vdd

vssvdd

vssvdd

n2acaspa

n2bcaspb

biaspcaspcasnbiasn

biasp

biasp

biasp

caspcasnbiasn

caspcasnbiasn

caspcasnbiasn

outn outp

cmreg

vss vss

casna casnb

caspa caspb

vss

.param cload=2.5p

m4b

l={l4} w={w4} m={mout}

m4a

l={l4} w={w4} m={mout}

l={l2} w={w2} m={min}

m2b m2a

l={l2} w={w2} m={min}

m1a

l={l1} w={w1} m={min}

m1b

l={l1} w={w1} m={min}

m5a

l={l5} w={w5} m={mout}

m5b

l={l5} w={w5} m={mout}

m6a

l={l6} w={w6} m={mout}

m6b

l={l6} w={w6} m={mout}

m3b

l={l3} w={w3} m={mout+min}

m3a

l={l3} w={w3} m={mout+min}

C1

{cload}

C2

{cload}

X3vdd biasgbpvssinout

casgbpcasgbnbiasgbn

gainboostn

X4vdd biasgbpvssinout

casgbpcasgbnbiasgbn

gainboostn

X5vdd biasgbpvssinout

casgbpcasgbnbiasgbn

gainboostp

X6vdd biasgbpvssinout

casgbpcasgbnbiasgbn

gainboostp

X2

vdd biaspvssibiasbiasn2

caspcasnbiasn

BIASING

X7outpoutnref

reg

C3

{ccm}

C4

{ccm}

C5

{cgbn}

C6

{cgbn}

C7

{cgbp}

C8

{cgbp}

cmreg

n3a n3b

caspbcaspa

outn outp

outpoutn

cmout

inp inn

biasn2

vss

n2a

n2b

n1a

biasn2

vddvss

ibiasbiasn2 biasn

casncaspbiasp

casna casnb

vdd

biasp

vss vss

vdd vdd

outpoutn

vss

n3a

n3b

casna

casnb

vss

vssvdd

vdd

vssvdd

vssvdd

n2acaspa

n2bcaspb

biaspcaspcasnbiasn

biasp

biasp

biasp

caspcasnbiasn

caspcasnbiasn

caspcasnbiasn

outn outp

cmreg

vss vss

casna casnb

caspa caspb

vss

.param cload=2.5p

m4b

l={l4} w={w4} m={mout}

m4a

l={l4} w={w4} m={mout}

l={l2} w={w2} m={min}

m2b m2a

l={l2} w={w2} m={min}

m1a

l={l1} w={w1} m={min}

m1b

l={l1} w={w1} m={min}

m5a

l={l5} w={w5} m={mout}

m5b

l={l5} w={w5} m={mout}

m6a

l={l6} w={w6} m={mout}

m6b

l={l6} w={w6} m={mout}

m3b

l={l3} w={w3} m={mout+min}

m3a

l={l3} w={w3} m={mout+min}

C1

{cload}

C2

{cload}

X3vdd biasgbpvssinout

casgbpcasgbnbiasgbn

gainboostn

X4vdd biasgbpvssinout

casgbpcasgbnbiasgbn

gainboostn

X5vdd biasgbpvssinout

casgbpcasgbnbiasgbn

gainboostp

X6vdd biasgbpvssinout

casgbpcasgbnbiasgbn

gainboostp

X2

vdd biaspvssibiasbiasn2

caspcasnbiasn

BIASING

X7outpoutnref

reg

C3

{ccm}

C4

{ccm}

C5

{cgbn}

C6

{cgbn}

C7

{cgbp}

C8

{cgbp}

cmreg

n3a n3b

caspbcaspa

outn outp

outpoutn

cmout

inp inn

biasn2

vss

n2a

n2b

n1a

biasn2

vddvss

ibiasbiasn2 biasn

casncaspbiasp

casna casnb

vdd

biasp

vss vss

vdd vdd

outpoutn

vss

n3a

n3b

casna

casnb

vss

vssvdd

vdd

vssvdd

vssvdd

n2acaspa

n2bcaspb

biaspcaspcasnbiasn

biasp

biasp

biasp

caspcasnbiasn

caspcasnbiasn

caspcasnbiasn

outn outp

cmreg

vss vss

casna casnb

caspa caspb

vss

.param cload=2.5pSystem block diagram

Captures impact ofblock’s effectson system behavior

Does not captureinteractions

Page 26: Integrating Physical Test into the IC Studio Workflow

HWP, Integrating Physical Test into the IC Studio Workflow, March 2007

26

Next steps /3 Pull software development and validation

into this codesign loop

■ In the virtual world: tools already support this.■ In fact, a few people have been doing this (with huge

success) for about twenty years.— Example: Andy Bechtolsheim’s team at Sun ran code and

booted the Sparc 1 chipset before they actually taped it out.■ In the physical world: ATE resources to support this flow

have been widely available for only about two years.— Example: D10 (Credence)— Trend: Open ATE initiative is gaining mainstream support

reference:http://www.semitest.org/news/articles/FF_19_Yuhai_Ma_05.pdf

■ The bottom line: for many products, it is possible to do validation (including software validation) at probe test. This speeds up development schedules.

Page 27: Integrating Physical Test into the IC Studio Workflow

HWP, Integrating Physical Test into the IC Studio Workflow, March 2007

27

Next steps /4Integrate yield-analysis and

product-engineering capabilities■ Yield Analysis Options

1. Corners Analysis■ Corners are based on digital performance criteria■ Requires many simulations■ Leads to overdesign – more so with newer processes

1. Classic Monte Carlo Analysis■ Best accuracy■ No overdesign■ Requires a prohibitive number of simulations

2. Monte-Carlo with KtModel Analysis■ Requires a limited number of simulations (user controlled)■ Model evaluations replace simulation in monte-carlo loop■ No overdesign

Page 28: Integrating Physical Test into the IC Studio Workflow

HWP, Integrating Physical Test into the IC Studio Workflow, March 2007

28

Next steps /4Integrate yield-analysis and

product-engineering capabilities■ KtModeler improves

the accuracy of behavioral models.

— Behavioral simulations can see issues previously caught only with spice simulation.

■ KtModeler can also be used instead of simulator in monte-carlo runs.

— Reduces the number of simulations required for monte-carlo by 10-100x

ADVance MSV-AMS Spice Fastspice Verilog

Page 29: Integrating Physical Test into the IC Studio Workflow

HWP, Integrating Physical Test into the IC Studio Workflow, March 2007

29

Acknowledgements■ Pixelworks executive support:

— Hans Olsen■ Pixelworks engineering team:

— Jenkin Wong, Thomas Nasralla, Mike Parrish, Jay Sulima, Pri Nallahandi, Liang Yuan

■ Insyte (ATE Consultant):— Peter Lindholm

■ Mentor: — Sam Wasche, Christian Mayer, Brandon Barnes,

Vamsi Rachapudi■ Credence:

— Ken Skala■ Kimotion:

— Bart De Smedt, Walter Daems

Page 30: Integrating Physical Test into the IC Studio Workflow

HWP, Integrating Physical Test into the IC Studio Workflow, March 2007

30