JTAG/Boundary Scan – a method for eliminating access problems in electronic assembly development
JTAG/Boundary Scan has become an increasingly valuable application, in particular in the development departments of small and large companies. On the one hand, this is due to the enormous potential the technology provides and, on the other hand to the problems increasingly compact assemblies and components place on test technologies with respect to mechanical access. Modern BGA packaging and high-speed transmission lines long for new approaches.
JTAG/Boundary Scan provides excellent and efficient utilization opportunities. But what are the extraordinary benefits for designers? What must be considered in assembly design to apply Boundary Scan? These topics are dealt with in the following article.
JTAG/Boundary Scan in development?
Is this really necessary? Isn’t it enough that designers – under consideration of some restrictions ? must plaster their boards with test points? Must designers now write tests themselves? What is the return on this effort? To fully understand, a few things must be made clear.
What is required for test generation? It is essential to know what component types are used, and how the component pins are interconnected. Each component type must be assigned to a related model. For example, there is a model for each Boundary Scan component describing the IC’s Boundary Scan structure, a so called BSDL (Boundary Scan Description Language) model. Depending on the vendor, there are additional models describing non-Boundary Scan components such as RAM or driver ICs. But that’s the only precondition to generate board tests.
The test system provides the models, and the required CAD data are limited to a net list and a component list. These can be found in the schematic that is usually available at an early board development stage. The advantage: problems that may occur in test generation can be solved easier, and test-depth-inconvenient designs can be changed extremely fast and simple. However, this is not all.
Generated tests are available already for the first prototypes. They can be tested with the same quality as the 0-series and finally the serial product – the same test depth, the same pin-level fault information. Now that the test bus necessary for Boundary Scan is available on the UUT (unit under test), e.g. via a connector, this interface can be used to load FPGA or CPLD components or to put the boot loader into the program flash. The resulting savings are apparent.
That doesn’t sound that bad, does it? But why are the designers to generate tests? These are test engineering tasks, incl. all associated problems!
1. The designer knows the board best!
• Starting with the component designations...
• Where are the focal points?
• Is high test effort justified?
• Design changes for test depth increase are quickly implemented – resulting in an assembly ideally designed for test
This is all leading to efficient test generation and finally efficient testing.
2. The first prototype can already be tested by the same methods as the serial product.
• Therefore, the test depth is the same
• Additionally, the same pin-level fault information is provided
This leads to an efficient initiation of prototypes and 0-series under serial conditions.
3. Ideal interface for EMS
• The tes archive is simply passed to the EMS. The contract manufacturer doesn’t have to coordinate or balance test generation and test scope.
• Test changes are implemented very fast.
For contract manufacturers, there is an extremely small amount of test effort (only the test equipment must be provided) leading to minimal costs.
All in all, there are a significant number of advantages a designer benefits from to a large extent. That obviously compensates the manageable effort in test generation.
What is JTAG/Boundary Scan?
JTAG/Boundary Scan is the world’s only standardized electric test method (IEEE Std. 1149.x). Stimulating and measuring the single circuitries on assemblies is no longer executed via predetermined test points and its connected metrology, but rather Boundary Scan cells integrated into a component. The IC architecture is shown in Figure 1.
Necessary information transmission between test system and Boundary Scan component is executed via a standardized four-wire test bus. The test bus must be considered in board design, sort of replacing the test points that would have been determined for an In-Circuit Test (ICT) or Flying Probe Test (FPT). Consequently, a test system must only provide a port for this test bus.
As test points are no longer required, there aren’t the same access problems as for ICT or FPT. Upon closer examination of Figure 1, it can clearly be seen that the Boundary Scan cells are located between the component’s pins and its inner logic. Hence, the core logic no longer plays a role for testing board circuitries. It doesn’t matter whether it is a processor or PLD.
How does a Boundary Scan test work? Image 2 is meant to illustrate this. First of all, a Boundary Scan component is switched to the external test mode (EXTEST). This is done by means of a signal interchange at Test Clock (TCK) and Test Mode Select (TMS) as well as setting a respective command via Test Data Input (TDI). From this moment on, the IC’s inner logic is separated from the pins. Now the Boundary Scan cell is exclusively responsible for the signal level at the component pin. Loaded with 1 or 0, a high level or low level is driven, respectively. Generally, at each pin there is a Boundary Scan cell for level measurement. It helps to verify test pattern and therefore check interconnections. It’s that simple.
Boundary Scan ? like any other test technology ? requires design rules that must be considered. If such design rules are disregarded, the achievable test depth might be considerably affected or in extreme cases completely lost. Nothing is “sadder” than a board that cannot be tested because of one missing interconnection. But there’s no need to worry about possibly “many” design rules. Convenient software provides support for rule compliance. Moreover, it once again demonstrates that it makes sense to start with test generation at a very early stage of product design. Once the layout is finalized, things are relatively hard to change.
JTAG/Boundary Scan is not only the most efficient test method for digital components, in particular at the design stage it provides a number of advantages enabling completely new test approaches and previously unobtainable high quality. The following aspects are worth noting:
• High-value test as early as the first prototype stage in series quality
• In-system programming and test utilizing the same interface
• Ideal interface for EMS
Compared to technological benefits, the requirements Boundary Scan puts on equipment, know-how and Design-for-Testability seem insignificantly small. With trends towards more and more compact packaging that restricts mechanical pin access and increasing integration density, the future belongs to Boundary Scan. And that future starts in the design divisions and the designers’ heads.