search.noResults

search.searching

dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
Page 60


www.us- tech.com


February, 2020


Eight reasons why you should use XJTAG to test your boards


Three simple letters – BGA


An increasing number of devices are supplied in BGA (Ball Grid Array) packaging. Each BGA device on a board imposes severe restrictions on the testing that can be done using traditional bed-of-nails or flying probe machines.


Using a simple four-pin interface, JTAG / boundary scan allows the signals on enabled devices to be controlled and monitored without any direct physical access.


Three more letters – NRE


The non-recurring engineering (NRE) costs of building test fixtures can be prohibitively high. In many cases using JTAG / boundary scanwill remove the need for such a fixture, in other cases the fixture can be dramatically simplified resulting in significant cost savings.


Shorter test times


For boards with low production volumes it has always been difficult to justify the cost of test fixture development. In these cases one alternative is flying probe testing; however the test cycle times tend to be high for this technology. JTAG / boundary scan test gives fast test times with no need for a costly fixture.


Lower test development costs


As different processors / FPGAs interact with peripherals in different ways,


traditional functional such development test requires costly


custom development for each board. JTAG / boundary scan significantly reduces


costs because it


provides a simplified interface to control the I/O pins used to interact with peripherals. This standard interface, which is the same for all JTAG enabled devices, means a generic set of test models can be used, and re-used, when building test systems.


XJTAG boundary scan tests can be run on any board with a working JTAG interface. Traditional functional tests cannot be run if


the board does not boot; simple faults on key


peripherals, such as RAM or clocks, would be found using JTAG but would prevent functional tests from providing any diagnostic information.


Take a free XJTAG trial and claim your XJAnalyser worth $7,900*


www.xjtag.com/giveaway *Terms and conditions apply.


enquiries@xjtag.com Try XJTAG free today & get a free Test Setup with your trial See at IPC APEX, Booth 1423 www.xjtag.com/giveaway One tool for test and programming


JTAG is often already used as one step in production: programming. By also using JTAG for boundary scan test it is possible to reduce the number of steps and handling operations in the production process.


Production level tests on the engineer’s bench for prototype boards


Traditional test technologies require very large and expensive equipment. The only test equipment required for JTAG / boundary scan testing is a JTAG controller – XJTAG’s XJLink2 controller is a similar size to a PC mouse.


Excellent fault diagnostics JTAG /


functional


boundary test,


scan, provides


unlike high


precision fault information to help with rapid repair. XJTAG also provides the capability to view both the physical location of a fault on the layout of the board and the logical design of the area of the circuit in which the fault exists on the schematic.


Most likely short locations


Recover ‘dead’ boards where functional test would not work


Identified short


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  |  Page 117  |  Page 118  |  Page 119  |  Page 120  |  Page 121  |  Page 122  |  Page 123  |  Page 124  |  Page 125  |  Page 126  |  Page 127  |  Page 128  |  Page 129  |  Page 130  |  Page 131  |  Page 132  |  Page 133  |  Page 134  |  Page 135  |  Page 136  |  Page 137  |  Page 138  |  Page 139  |  Page 140  |  Page 141  |  Page 142  |  Page 143  |  Page 144