Skip to content

5.3 Boundary Scan Essentials: JTAG

As component packaging has evolved from traditional through-hole pins to high-density Ball Grid Arrays (BGAs) and Chip-Scale Packages (CSPs), physical solder joints are increasingly hidden beneath the component bodies. This physical reality makes traditional “bed-of-nailsIn-Circuit Test (ICT) fixtures less effective in these areas; a connection cannot be probed if it cannot be reached. To address this, the industry developed Boundary Scan (IEEE 1149.1), commonly known as JTAG. Boundary Scan is not merely a debugging tool; it is a foundational testing method that allows for the electrical verification of hidden interconnects using just four dedicated signaling pins.

How Boundary Scan Works: The Virtual Probe

Section titled “How Boundary Scan Works: The Virtual Probe”

The strength of Boundary Scan lies in its elegant approach. Instead of using a physical metal probe to touch a copper pad on the board, Boundary Scan uses silicon logic inside the component itself to act as a “virtual probe.”

When a silicon vendor designs an IC compliant with IEEE 1149.1, they insert a microscopic shift register (a “boundary scan cell”) between the chip’s core logic and its physical external pins.

  1. The Test Access Port (TAP): The test station connects to the board via a 4-wire interface: TCK (Test Clock), TMS (Test Mode Select), TDI (Test Data In), and TDO (Test Data Out).
  2. Taking Control: By manipulating the TMS and TCK lines, the test station prompts the ICs on the board to momentarily disconnect from their normal internal core logic and hand control of their physical external pins over to the boundary scan cells.
  3. The Shift Operation: The test station shifts a sequence of 1s and 0s (data) serially into the TDI pin. This data ripples through the boundary scan cells of the connected chips on the board (the “scan chain”).
  4. The Update and Capture: Once the data is in place, the test station issues an “Update” command. The ICs force those 1s and 0s out onto the physical copper traces of the PCB. Simultaneously, the receiving ICs on the other end of those traces “Capture” the incoming signals.
  5. The Shift Out: Finally, the captured results are shifted serially back out through the TDO pin to the test station.

By comparing the data sent in versus the data shifted out, the test software can verify whether the copper trace connecting the two chips is intact, shorted to ground, or shorted to an adjacent trace—all without touching the trace with a probe.

The Strategic Value of JTAG on the Production Floor

Section titled “The Strategic Value of JTAG on the Production Floor”

Boundary Scan provides capabilities that transform how manufacturing testing is approached, moving beyond simple structural verification.

This is a primary reason Boundary Scan is utilized. While Automated X-Ray Inspection (AXI) can look for voids or misaligned balls under a BGA, AXI is an optical inference, not an electrical evaluation. Boundary Scan provides electrical confirmation that a BGA solder joint is conductive and properly formed. For boards containing complex digital ICs (Processors, FPGAs, large Memory), utilizing Boundary Scan coverage is highly recommended.

2. In-System Programming (ISP) at Line Speed

Section titled “2. In-System Programming (ISP) at Line Speed”

Boundary Scan is not limited to testing continuity. The same 4-wire JTAG bus can be used to write data directly into non-volatile memory (Flash, EEPROM) or to program microcontrollers and CPLDs after they have been soldered to the board.

  • The Advantage: This reduces the need to pre-program bare chips before SMT assembly, simplifying inventory management and ensuring the latest firmware version is flashed just before the board is functionally tested.

Every net tested via Boundary Scan is a net that does not require a physical spring-loaded probe on the ICT fixture. This reduces the mechanical complexity, node count, and upfront cost of the ICT fixture, while also freeing up physical space on the bottom of the PCB for more components.

Design for Testability (DFT) Rules for Boundary Scan

Section titled “Design for Testability (DFT) Rules for Boundary Scan”

Boundary Scan depends entirely on the PCB layout. The test engineering team relies on proper routing to implement it effectively.

Design RuleEngineering Rationale
Expose the TAPThe 4 JTAG signals (TCK, TMS, TDI, TDO) should be routed to accessible test pads or a dedicated header. Without physical access to the TAP, the methodology cannot be used.
Maintain the ChainTDO of Chip A should connect to TDI of Chip B, and so on, forming a continuous daisy chain. If the chain is broken by a missing component during assembly, testing cannot proceed smoothly.
Buffer the ClockThe TCK (Test Clock) should be distributed cleanly. If the chain is long, buffering TCK helps prevent signal degradation, ensuring all chips shift data reliably.
Compliance PinsSome ICs require specific pins (e.g., reset lines or boot mode selects) to be held High or Low to enable JTAG mode. These compliance pins should be manageable by the test station, rather than hard-tied to power or ground in a way that prevents overriding.

Final Checkout: Boundary scan essentials (JTAG)

Section titled “Final Checkout: Boundary scan essentials (JTAG)”
RequirementGoal / Verification PointResponsibility
Chain ArchitectureJTAG devices must be verified to be daisy-chained and the TDO-to-TDI order documented and stable.Design Engineer / Test Engineer
Physical AccessA dedicated 5-pin TAP header or robust test pad arrangement must be confirmed to be present, and the PCB layout must align with the fixture’s probe grid.Design Engineer
Coverage ScopeBSCAN must be guaranteed to verify the digital interconnects under BGAs. A structural test coverage report can confirm BGA net coverage.Test Engineer
Programming TaskIn-line programming of Flash/MCUs must be validated to execute successfully via the JTAG port, and test programming time must fit within the required Takt Time.Test Engineer
Golden DataThe Boundary Scan Description Language (BSDL) files for all JTAG components must be collected and archived. Files should match the exact chip stepping used in the BOM.Test Engineer