This page contains a Flash digital edition of a book.
June, 2016


www.us- tech.com


JTAG and Boundary-Scan Past, Present and Future


By Peter van den Eijnden, Managing Director, JTAG Technologies


prompted a group of production test engineers to consider the impact of these parts on the testing of their assemblies. They called themselves the Joint European Test Action Group (JETAG) and were made up of repre- sentatives from Philips, BT, GEC, Siemans, Plessey, and others. In most cases up to the mid-1980s, tests were accomplished by in-circuit testers (ICTs) for individual component and PCB testing, or function testers that mimic the environment of the UUT to send and receive stimulus and response signals. With advent of SMT and higher levels of integration, test access for ICTs was greatly dimin- ished. In addition, due to the higher integration levels, functional test became a more arduous process.


A


JTAG’s Beginnings It was at this point that the


JETAG committee started to think about a mechanism for embedding test capabilities into the devices themselves. Before long, the commit- tee gained more members from “The New World” and the group’s name became the simpler JTAG that we know today. The fruits of their labor, “The Test Access Port and Boundary- Scan Architecture”, described how a serial scan register could access digi- tal signal pins of a device to either capture an input signal or propagate an output signal through the pin of the part, while isolating the part’s regular function. A number of support registers, including the instruction register and bypass register, and a state-machine (TAP controller) com- pleted the picture. In 1990, the sys- tem was proposed to the IEEE com- puter standards authority, and a bal- lot approved the IEEE 1149.1 stan- dard. A few years later, IEEE std. 1149.1b, an addendum, described a precise syntax for a device modeling language, BSDL, which was based broadly on VHDL. With the ability to describe an


individual device’s boundary-scan capability in BSDL, along with CAD data that described the interconnec- tions between parts in a design, it became possible to develop automat- ic test program generators that could devise a test to detect 100 percent of shorts or opens in the interconnec- tions on a device supporting JTAG. One of the first of these, by Philips Test and Measurement, which later became JTAG Technologies, was known as BTPG_I (Boundary-Scan Test Program Generator for Inter - connects). This set the stage for a 25- year development program of im - proving JTAG-oriented test products built upon standards. Engineers working on the tools


to support IEEE std. 1149.1 (JTAG and boundary-scan) realized that the access provided by the principle boundary-scan register (BSR) could also be used to stimulate standard parts in the same way that ICT I/O pins had in the past. Soon they had added the capability to stimulate memory write and reads from the JTAG part to memories such as SRAMs, FIFOs and DRAMs. By


lmost 30 years ago, the change in device packaging from through-hole to surface-mount


applying a carefully devised, compact set of test vectors, a test could be made to detect opens and shorts on the signals to and from the memory cluster. An advanced diagnostics model gave a pin-level description of the fault.


Programmable Logic and Fault Coverage


The next major development in Timeline of JTAG test development.


harnessing JTAG for production was the introduction of programmable logic parts that used JTAG not only


Continued on page 55


Page 53


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84  |  Page 85  |  Page 86  |  Page 87  |  Page 88