This page contains a Flash digital edition of a book.
March, 2014 Continued from previous page


www.us-tech.com


Boundary Scan Integration on Flying Probe Testers Software integration typically requires spe-


perform tests for shorts on IC pins, flying probes must be placed on the pins first. Once shorts tests for a current group of pins have been performed, the probes must be moved to other pins to test for shorts.


Boundary-scan testing does not rely on any


physical movements, so shorts tests can be per- formed much faster than shorts tests performed using the flying probe approach. Generally speaking, boundary-scan testers


are equipped to detect lifted pins on ICs if a bound- ary-scan cell can sense a logic level coming from an external source. This external source in this case may be another boundary scan cell from another IC interconnected through a PCB trace. Other pos- sibilities include pull up, pull down circuit configu- rations, and also other non-boundary-scan devices that are capable of supplying a logic level to the boundary-scan cell. There are some general guide-


lines that a design engineer should use to increase testability on a PCB but, generally speaking, a lack of


Boundary-scan testers are equipped to detect lifted pins on ICs if a boundary-scan cell can sense a logic level coming from an external source.


Design for Test (DFT) on a circuit board is not a problem for a flying probe test. In contrast, boundary-scan testers depend heavily on DFT imple- mented on the circuit board and ICs to be tested. A design engineer needs to implement boundary-scan condi- tions on a circuit board by providing TAP connections and proper connec- tions for ICs, whereas a product engi- neer may need to ensure that the boundary-scan-compatible version of an IC is available and the connector for the TAP can be mounted. For measurements performed


with a flying probe tester, a benefit can be to speed up a test. When test speed is important, a flying probe test program may be optimized to take advantage of the shorts and open pins tests that are already performed by a boundary-scan tester.


Added Access For measurements performed


with a boundary-scan tester, a benefit may be in terms of added access and therefore increased nets and pins cov- erage. Flying probes in this case can be programmed to function as virtual boundary-scan cells to provide input signals to boundary-scan cells and to measure the output signals from the boundary-scan cells. In a typical test setup, bound-


ary-scan hardware will control all of the digital vectors involved in the boundary-scan test. The digital boundary-scan vectors include both the TAP port and the digital signals through flying probes. The TAP port signals are generated directly by the boundary-scan controller, whereas the digital signals on flying probes are generated and sensed by the fly- ing probe tester. Flying probe hardware must be


in control of the probe movements. This is done for safety reasons and also to avoid any probe collisions. If the boundary-scan controller must either drive or sense a signal on a net on a circuit board under test, the boundary-scan software will specify which net it needs and the flying probe will move and position an appropriate probe in that location.


See at APEX, Booth 324 cially written dynamic-link-library (DLL) files for


Page 67


the boundary-scan controller to communicate with the flying probe tester. The DLL files facilitate sev- eral aspects of integration including proper test flow, sharing of information to optimize the tests, test result reporting, and combined test coverage reporting.


Case Studies Several case studies have been performed on


Increase of coverage possible with flying probe and boundary-scan integration.


the integration of the two test approaches. These studies reveal that one technology may benefit more from the integration than the other, and also that the combined test time is not always faster than when performing the two tests separately. Either way, the studies reveal, the combined final test coverage is greater compared to each of the technologies used separately. In the first case study, the circuit board under


Continued on next page


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  |  Page 89  |  Page 90  |  Page 91  |  Page 92  |  Page 93  |  Page 94  |  Page 95  |  Page 96  |  Page 97  |  Page 98  |  Page 99  |  Page 100  |  Page 101  |  Page 102  |  Page 103  |  Page 104  |  Page 105  |  Page 106  |  Page 107  |  Page 108  |  Page 109  |  Page 110  |  Page 111  |  Page 112  |  Page 113  |  Page 114  |  Page 115  |  Page 116