47
1 NMI: 12 th May 2016 Using Test Access Standards Across The Product Lifecycle Andrew Richardson [email protected]

Using Test Access Standards Across The Product Lifecycle · Andrew Richardson [email protected] . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

  • Upload
    others

  • View
    0

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

1 NMI: 12th May 2016

Using Test Access Standards Across

The Product Lifecycle

Andrew Richardson

[email protected]

Page 2: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

2 NMI: 12th May 2016

Outline

• Background & Previous Work

• Revision - Boundary Scan

• Extension to iJTAG IEEE1687

• iJTAG Programing

• Case Studies

• Summary and References

Page 3: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

3 NMI: 12th May 2016

Background 2015/16

• 2015/16: Work for EC – ICT3 “Smart Systems” & ICT25 Nanoelectronics

• DfT Training: Singapore and Penang

• Research into prognostics & on-line test – Lancaster University

• Work on Prognostics (Pressure and Electrochemical Sensors)

– “Use of Self-Calibration Data for Multifunctional MEMS Sensor Prognostics, IEEE

Journal of Micromechanical Systems (JMEMS)

DOI:"10.1109/JMEMS.2016.2564499”, May 2016

– A “Housekeeping Prognostic Health Management” (HPHM) framework for a

Microfluidic Bio-MEMS" IEEE Transactions on Device and Materials Reliability,,

April 2016 TDMR-2015-12-0301-R.

WWW.EnablingMNT.com

Page 4: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

4 NMI: 12th May 2016

Through Life Support

• Need a method to test & monitor devices in application

• Ideally detect evolving faults

• Requires hardware monitoring

– Need to measure simple parameters

– No complex stimuli

• Needs simple integration into the device and system

(Test Access Standards!)

• Numerous self-test structures developed by little uptake

due to cost and complexity of integration

Page 5: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

5 NMI: 12th May 2016

Previous Work

Pass/Fail

Ref

TAP Controller & Interface electronics

Digital Circuitry

DBM

DBM

DBM

DBM

DBM

DBM

Analogue Circuitry

TMS

TCK

AT1 AT2

ABM

ABM

ABM

ABM

ABM

ABM

TDO

TDI TAP Controller

& Interface electronics

Digital Circuitry

DBM

DBM

DBM

DBM

DBM

DBM

Analogue Circuitry

TMS

TCK

AT1 AT2

ABM

ABM

ABM

ABM

ABM

ABM

TDO

TDI

Open

Test Access

Engine

Test

Master

HCS12 processor

Tes

t M

easu

rem

ent

Figure 3: on-line interconnect monitoring

Jeffrey, Richardson wt al: Online Monitoring for Automotive Sub-systems

Using 1149.4. Board Test Workshop 2003.

Page 6: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

6 NMI: 12th May 2016

Outline

• Background & Previous Work

• Revision - Boundary Scan

• Extension to iJTAG IEEE1687

• iJTAG Programing

• Case Studies

• Summary and References

Page 7: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

7 NMI: 12th May 2016

– Development started in 1985 by the Joint European Test Action Group and in 1986

became the Joint Test Action Group (JTAG) following North American involvement.

– In 1988, a proposal from this group for a boundary scan standard JTAG Version 2.0

was offered to the IEEE Testability Bus Standards Committee (P1149) for inclusion

in the standard being developed. This submission became the basis for the IEEE

standard and JTAG became the working group developing the standard.

– IEEE std. 1149.1 was accepted in 1990. The latest revision was published in 2012.

Boundary Scan is an IEEE standardised

architecture for test access to complex PCB’s and

the integrated circuits on those PCB’s, as well as

the control of on-chip test features such as scan

paths.

Maybe Revisit Boundary Scan?

Page 8: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

8 NMI: 12th May 2016

Core Logic

Test Data In (TDI)

Test Clock (TCK)

Test Mode Select (TMS)

Test Data Out (TDO)

PI

PO

SO SI

Each boundary-scan cell can: Capture data on its parallel input PI Update data onto its parallel output PO Serially scan data from SO to its neighbour’s SI Behave transparently: PI passes to PO

Principle Of Boundary Scan

Page 9: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

9 NMI: 12th May 2016

Boundary-Scan Register

TDI TDO

TMS

TCK

TRST* (optional)

TAP Controller

Instruction Register

Identification Register

Data register

Bypass register

Core Logic

Note: all digital logic must be contained inside the boundary-scan register

IEEE1149.1 Architecture

Internal scan

path

Page 10: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

10 NMI: 12th May 2016

IEEE 1149.1 Basics

• Internal scan paths are also connected via the test-bus to the pins

TDI & TDO.

• The normal I/Os of the core logic are connected via the boundary

scan cells to the same pads.

• The test bus itself consists of the boundary scan registers, a 1-bit

bypass register, an instruction register, several other registers and

the TAP.

• In addition to the TDI & TDO pins, a test clock and a test mode pin

have to be provided. TDI receives test instructions and test data,

test results are read via TDO, test control is applied via TMS & TCK.

Page 11: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

11 NMI: 12th May 2016

TAP Controller

Select DR Scan

Capture DR

Shift DR

Exit 1 DR

Pause DR

Exit 2 DR

update DR

Select IR Scan

Capture IR

Shift IR

Exit 1 IR

Pause IR

Exit 2 IR

update IR

Test logic

reset

Run test /

Idle

1

1

1

1 1

1 1

1

1

1

1

1

DR – Data Register

IR – Instruction Register

Page 12: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

12 NMI: 12th May 2016

Basic Boundary-Scan Cell

D

Clk

Q D

Clk

Q

Data In (PI)

Scan In (SI)

ShiftDR ClockDR UpdateDR

Mode

Data Out (PO)

Scan Out (SO)

Scan Cell Hold Cell

Normal: Mode=0: data passes from PI to PO to core logic; cell is transparent

Scan: ShiftDR=1: cells form scan path via SI/SO connected to TDI & TDO

Capture: ShiftDR=0: data on PI can be loaded into the scan path when ClockDR

Update: Mode=1: Content of Scan Cell (from scan or capture operation) is applied to PO when pulse on UpdateDR

SO

SI

PO PI

Page 13: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

13 NMI: 12th May 2016

Extensions of IEEE 1149.1

• IEEE 1149.1-2012 / 2013 extends the standard to:

– support a redefined initialisation data register to support

analogue parameters for configuring high speed I/O

– Enables on-chip PLL’s to be controlled

– See http://grouper.ieee.org/groups/1149/1/ieee-1149-1-2012-

changes.pdf for more details

• IEEE 1149.7 reduces the pin count to 2 and offers four selectable

power modes to enable ultra-low power devices.

Page 14: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

14 NMI: 12th May 2016

What about Adoption of Boundry Scan

• None of these standards are really optimised to

support embedded test structures and

monitoring instruments – previous work around

1149.4 has little infrastructure to build on.

Page 15: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

15 NMI: 12th May 2016

Outline

• Background & Previous Work

• Revision - Boundary Scan

• Extension to iJTAG IEEE1687

• iJTAG Programing

• Case Studies

• Summary and References

Page 16: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

16 NMI: 12th May 2016

Is IJTAG? (IEEE P1687) an option

• IJTAG was proposed to address the following shortcomings and weakness identified in both IEEE 1149.1 and IEEE 1500: – Identified weaknesses regarding test scheduling and

operating trade-offs

– Concerns with respect to limitations in scalability with growing number of embedded instruments

• Through life testing demands access to internal test resources within the application – iJTAG supports access to “embedded Instruments”

via a standardised JTAG interface

Page 17: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

17 NMI: 12th May 2016

What does iJTAG include?

• iJTAG 1687 is an IEEE Standard

• It is made up of 3 components

– A flexible instrument access architecture

leveraging a network of serial scan chains

– A programming language to describe the network

(Instrument Connectivity Language: ICL)

– An instrument vector language (Procedural

Description Language: PDL)

Page 18: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

18 NMI: 12th May 2016

Current Status

• Published as IEEE 1687-2014 on the 5th of December, 2014

• Active Committee Members included: – 12 Chip Providers (including TI, IBM, AMD,

Qualcomm, Broadcom etc.)

– 14 Tool Providers (including ASSET, Intellitech, Mentor, Cadence, Goepel etc.)

– 2 Instrument Providers (Tektronix and Agilent)

– 1 ATE provider (Teradyne)

– 5 End Users (including Cisco, Alcatel-Lucent etc. )

Page 19: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

19 NMI: 12th May 2016

iJTAG 1687 Solution

• Adds an interface to JTAG in the form of a Test Data Register –

“The Gateway”

– Routes TDI and TDO to instrument networks

– Enabled through IR scan then use of RD scans to load all data

TCK

TRST

TMS

TDI

TDO

JTAG IR

Gateway

Gateway

SEL

HIP

Inst

Inst

SEL

HIP

State Machine

Inst

JTAG Zone P1687 Zone

HIP – hierarchical interface

port

Page 20: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

20 NMI: 12th May 2016

The Gateway Structure

– The gateway contains one or more Segment Insertion Bits

(SIB’s) – acts as a switch that is controlled by the GWEN

instruction and shifted in data to either open (scan-in to HIP scan

in), Scan-out to HIP scan out) or closed – Scanin to Scanout.

– Also must route clock, select, shift-enable, capture-enable and

update-enable to each lower level SIB

Page 21: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

21 NMI: 12th May 2016

Operation

• Opening and Closing SIB’s in the gateway: – In Shift-DR, each control bit is placed into the

register of each SIB in the gateway.

– Update-DR state: The control bit for each SIB is

transferred into the SIB’s State Register,

– back to Shift-DR - shift out the output vector and

shifting in the next input

• The above represents one control cycle which

takes 6 TCK cycles.

Page 22: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

22 NMI: 12th May 2016

TDR(s)

ScanOut1

ScanIn

Select

ScanOut

CaptureEn

GlobalRst

ScanIn

ShiftEn

UpdateEn

TCK

TCK

TMS

TDI

TDO

SIB

control[1..n]

run

enable

Response

(Pass/fail)

reset

ScanIn

ScanOut

TAP

A Simple 1687 Network

Controller

• Access Link Instruction

• Not Part of the 1687 Standard

• Used 1149.1 TAP Controller

Network

• Instrument Interface & Instrument Vectors

• Scan Path Network & Plug-n-Play Features

• Scan Path Management (SIBs, NIBs, LRs)

• Local Selection & Configuration Decode

Instrument

• Embedded Instrument (or

device)

• Not Part of the 1687

Standard

ICL Description

PDL

Vectors

Page 23: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

23 NMI: 12th May 2016

Test Data Registers

• The Instrument Interface Register is a variable length IEEE1149.1 TDR

• Each instrument in a 1687 Compliant architecture should be paired

with a “size appropriate” TDR

• The cells can be Read-Only, Write-Only or Read-Write

TDR(s)

ScanOut1

ScanIn

Select

ScanOut

CaptureEn

GlobalRst

ScanIn

ShiftEn

UpdateEn

TCK

TCK

TMS

TDI

TDO

SIB

control[1..n]

run

enable

Response (Pass/fail)

reset

ScanIn

ScanOut

TAP

Page 24: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

24 NMI: 12th May 2016

Test Data Registers: organisation

• TDR’s can be organized in different ways

to minimize the Access Time overhead

Ibrahim A, Kerkhoff, HG: IJTAG Integration of Complex Digital Embedded Instruments, 9th International Design and Test Symposium, 2014

Page 25: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

25 NMI: 12th May 2016

• SIB is a single bit TDR

• Any number of them can be placed anywhere

in the network

• SIBs are used to include scan-paths, allowing

dynamic reconfiguration of a P1687 network

• SIB acts as a gateway with two states, open or

closed

Scan Insertion Bit (SIB)

Page 26: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

26 NMI: 12th May 2016

When closed the

“select” is de-asserted

and freezes the TDR

Scan Insertion Bit (SIB)

To TDI

2

TDI

TCK

Update

En

Select

ShiftE

n

TDO

Shif

t Updat

e

From

TDO 2

Select

Page 27: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

27 NMI: 12th May 2016

0

When Closed

The SIB represents

a single bypass bit

To TDI 2

TDI

TCK

UpdateEn

Select

ShiftEn

TDO

Shift Updat

e

From TDO 2

Select

Scan Insertion Bit (SIB)

Page 28: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

28 NMI: 12th May 2016

To TDI 2

TDI

TCK

UpdateEn

Select

ShiftEn

TDO

Shift Update

From TDO 2

Select

1 When Open:

A pre-SIB inserts

the added scan

path in front of the

control cell

A post-SIB inserts

the added scan

path after the

Control cell

Scan Insertion Bit (SIB)

Page 29: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

29 NMI: 12th May 2016

Reset

0

Variable length

scan path

closes on Reset

Scan Insertion Bit (SIB)

To TDI 2

TDI

TCK

Update

En

Select

ShiftE

n

TDO

Shif

t Updat

e

From TDO

2

Select

Page 30: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

30 NMI: 12th May 2016

• Types of Embedded Instruments: – Design-Ware

– Reused legacy design

– 3rd Party IP

– EDA-Generated

• Embedded Instruments Access for: – Test: Scan, BIST etc.

– Debug: Trace, Buffer Capture, Triggers etc.

– Monitor: I/O monitoring etc.

– Functional Configuration: Bus Configuration, IO Tuning, PLL Settings etc.

Network; Embedded Instruments

Page 31: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

31 NMI: 12th May 2016

Outline

• Background & Previous Work

• Revision - Boundary Scan

• Extension to iJTAG IEEE1687

• iJTAG Programing

• Case Studies

• Summary and References

Page 32: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

32 NMI: 12th May 2016

1687 Procedural Language

• Why not extend BDSL (Boundary Scan Description

Language? – BSDL provides only a static structural view of the system.

– The boundary scan chain is detailed as an ordered

succession of bits.

– Internal chains are defined only by name and fixed length.

– BSDL has no procedural or algorithmic capabilities.

– BSDL can define new rules through language extensions.

Page 33: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

33 NMI: 12th May 2016

Procedural Description Language

• Two languages have been developed – hardware description language (ICL) that contains the

hierarchical connectivity of the scan network between the IEEE

1149.1 Test Access Port (TAP) and the instruments

– procedure description language (PDL) that contains the patterns

used to interact with the instruments.

Page 34: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

34 NMI: 12th May 2016

Instrument Connectivity Language (ICL)

• The ICL is used to describe the access mechanisms and network of embedded instruments

• ICL documents and describes Instruments, their interfaces and documents their pathways

• The “soft” knowledge of the pathways allows for dynamic reconfiguration of test vectors

• The ICL can be (informally) perceived of being of two types:

– instrument-ICL (i-ICL) describing the instrument and its interface(s)

– network-ICL (n-ICL) describing the network and pathways

Page 35: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

35 NMI: 12th May 2016

Procedural Description Language (PDL)

• PDL documents the operations of embedded instruments

• The instrument whose operations are described can be at any network level. PDL is used in conjunction with ICL.

• PDL allows automated tools to retarget the instrument’s procedures and test vectors

• There are two levels of PDL programming:

– Level 0 PDL: Allows for static programming. There are no loops, conditional branching commands or interactive features.

– Level 1 PDL: This is essentially “Tool Control Language” (TDL) that has all the features of a fully mature programming language. It is a widely used in EDA.

Page 36: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

36 NMI: 12th May 2016

iPDLLevel 1;

iProcsForModule adc_bist;

##This declaration binds all following commands to adc_bist module

iProc BIST_Stim{{mode default}{

iClock clk; ## Clock

set cycles(default) 5000;

set cycles(thorough) 20000;

iRead status[2]; ##read power status

iRunLoop $cycles($mode) –sck -clk; ##wait for n clock cycles

iApply;

iWrite enable 1; ##enable the device

iApply;

iWrite data 0xA5; ##write an 8bit test sequence equal to mt_b

iApply;

iWrite trigger 1; ##initiate signal stimulus

iApply;

iRead testEnded 1; ##testEnded expected value ‘1’ (test ended)

iWrite enable 0; ##disable the device

iApply;

}

Example of PDL for an adc_bist module

Module Set

Procedure to run BIST_Stim in

default mode

Clk is set

Setting mode specific run cycles

Wait for n clock cycles

Enable Device

Load “mt_b” test values as stimulus

Trigger test based on stimulus

Read Test output, Disable instrument

Page 37: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

37 NMI: 12th May 2016

Outline

• Background & Previous Work

• Revision - Boundary Scan

• Extension to iJTAG IEEE1687

• iJTAG Programing

• Case Studies

• Summary and References

Page 38: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

38 NMI: 12th May 2016

Using IJTAG digital Islands to Perform

Trim and Test (2015)

• Dialog Semiconductor, Germany

– Demonstrates the use of IJTAG islands to hold

test and trim functions.

– These digital islands were integrated with

analogue circuits with minimal digital overhead

– Demonstrates the use of a hardwired mapping

between the legacy I2C and TAP allowing the use

of I2C to access IJTAG resources

von Staudt, H. M., & Spyronasios, A. (2015, June). Using IJTAG digital islands in analogue circuits to perform trim and test functions. In Mixed-Signal

Testing Workshop (IMSTW), 2015 20th International (pp. 1-5). IEEE.

Page 39: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

39 NMI: 12th May 2016

Fig 1: Initialization

Data flow for digital

core registers

Fig 2: Proposed IJTAG

island architecture with

address register bank

Fig 3: I2C mapped to

TAP controller

connected to IJTAG

chain

Using IJTAG digital Islands to Perform

Trim and Test (2015)

Page 40: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

40 NMI: 12th May 2016

An MPSoC demonstrator using IEEE

P1687 (2014)

• Ericson AB, Lund University & Semcon Sweden (2014)

– MPSoC demonstrator developed to enable Fault Injection and Fault

Handling experiments

– Instrument Access Infrastructure (IAI) defined using IEEE P1687. It

defines a network of instruments equipped with fault detection

features on the MPSoC

– Use of IEEE P1687 to inject faults in targeted instruments

– Use of IEEE P1687 to assist in fault handling

– Demonstrated:

• Improvement at the rate of component level fault detection

• Improved system-level fault action

• Flexible access to all components on the network

Petersen, Kim, et al. "Fault injection and fault handling: An MPSoC demonstrator using IEEE P1687." On-Line Testing Symposium

(IOLTS), 2014 IEEE 20th International. IEEE, 2014.

Page 41: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

41 NMI: 12th May 2016

Tree-like “Instrument

Access Infrastructure” &

“Fault Indication and

Propagation Infrastructure”

An MPSoC demonstrator using IEEE

P1687 (2014)

Error Indication Flag

Page 42: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

42 NMI: 12th May 2016

Case Study – Agilent / Avago

• Bit Error rate Testing and Eye Mapping for a

HSSIO.

• Use of P1687 to control, seed, execute and

capture outputs from the test resource

• Targets portability and access via standard TAP

and P1687 interface

Page 43: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

43 NMI: 12th May 2016

Traditional v Embedded

• Traditional BERT:

– no externally accessible point at which to probe

the post-equalized signal in the receiver

• Embedded BERT

– not necessarily well-calibrated compared to a lab

instrument since it resides on the same silicon as

the circuit it is measuring.

Page 44: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

44 NMI: 12th May 2016

HSSIO Instrument

• Target is a digital BIST for BER and Eye mapping

• Potential to generate compensation feedback

• Features margin analysis for rapid generation of low BER metrics

Page 45: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

45 NMI: 12th May 2016

Case Study – Agilent / Avago

• complete register based interface to all HSSIO

instrument resources

• third latch controlled by an Update signal, so that the act

of shifting the scan chain is not destructive to the Q-

outputs of the flip-flops.

Page 46: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

46 NMI: 12th May 2016

Conclusion

• iJTAG Well suited to the control of many structural test &

monitoring solutions in Digital and Mixed Signal systems.

• Support for use of the standard is good – eg. Mentor

Graphics “Tessent”

• Interest in building solutions including Bias Superposition

into industrial demonstrators using iJTAG.

• If hardware can be monitored on-line, can prognostics

and self-repair also be implemented? – leading to a

complete through life solution.

Page 47: Using Test Access Standards Across The Product Lifecycle · Andrew Richardson A.Richardson@enablingMNT.co.uk . NMI: 12th May 2016 2 Outline • Background & Previous Work • Revision

47 NMI: 12th May 2016

References

• IEEE Std. 1149.1 IEEE Standard Test Access Port and Boundary-Scan Architecture, DOI

10.1109/IEEESTD.2001.92950, Aug. 2002

• IEEE Std. 1149.7TM Standard for Reduced-Pin and Enhanced-Functionality Test Access Port and Boundary-Scan

Architecture, DOI 10.1109/IEEESTD.2010.5412866 Feb. 2010.

• JTAG Development tools and products see for example

– http://www.xjtag.com/, http://www.jtag.com/, http://www.jtagtest.com/

• IJTAG, “IJTAG - IEEE P1687,” 2010, http://grouper.ieee.org/groups/1687.

• J. Rearick and A. Volz, “A Case Study of Using IEEE P1687 (IJTAG) for High-Speed Serial I/O

Characterization and Testing,” in Proc. ITC, 2006, pp. 1–8.

• Larsson, E.; Zadegan, F.G., "Accessing Embedded DfT Instruments with IEEE P1687," Test Symposium (ATS),

2012 IEEE 21st Asian , vol., no., pp.71,76, 19-22 Nov. 2012. doi: 10.1109/ATS.2012.74

• F. G. Zadegan, U. Ingelsson, G. Carlsson, and E. Larsson, ”Access Time Analysis for IEEE P1687,” in

Computers, IEEE Transactions on, vol. 61, nr. 10, pp. 1459–1472, October 2012.

• F. Ghani Zadegan, U. Ingelsson, E. Larsson, G. Carlsson, ”Reusing and Retargeting On-Chip Instrument

Access Procedures in IEEE P1687,” in Design Test of Computers, IEEE, vol. 29, nr. 2, pp. 79–88, April 2012.

• von Staudt, H. M., & Spyronasios, A. (2015, June). Using IJTAG digital islands in analogue circuits to perform trim

and test functions. In Mixed-Signal Testing Workshop (IMSTW), 2015 20th International (pp. 1-5). IEEE.

• Petersen, Kim, et al. "Fault injection and fault handling: An MPSoC demonstrator using IEEE P1687." On-Line

Testing Symposium (IOLTS), 2014 IEEE 20th International. IEEE, 2014.