The Critical Role of IEEE 1687 (IJTAG) in Modern Automated Test Equipment for Semiconductor Devices

The relentless progression of Moore’s Law has delivered semiconductor devices of staggering complexity. Modern system-on-chips (SoCs) integrate dozens of functional cores, high-speed SERDES lanes, analog mixed-signal blocks, and dedicated security and power management units. Testing these devices thoroughly while containing cost requires a fundamentally efficient approach to embedded instrumentation. The IEEE 1687 standard—commonly known as IJTAG (Internal JTAG)—has emerged as a foundational enabler for Automated Test Equipment (ATE), providing a standardized, hierarchical method to access and control the growing number of embedded instruments within a single chip. Unlike legacy JTAG, which is limited to boundary-scan operations, IEEE 1687 offers the scalability and flexibility that ATE systems require to validate, characterize, and diagnose today’s most advanced semiconductors.

Understanding IEEE 1687: Architecture and Operation

IEEE 1687 standardizes an access network for embedded test and debug instruments. It builds upon the IEEE 1149.1 JTAG test access port (TAP) but introduces key architectural innovations that make it far more suitable for internal instrument access.

The Instrument Access Network (IAN)

At the heart of IEEE 1687 is the Instrument Access Network (IAN). This is a configurable scan chain architecture that connects the TAP controller to multiple embedded instruments. The IAN relies on a small hardware element called the Segment Insertion Bit (SIB). A SIB acts as a gate: it can either include a sub-chain of instruments in the main scan path or bypass it entirely. By chaining SIBs in a hierarchical manner, designers can create a tree-like network that provides selective, serial access to any instrument.

How Data Transfer Works

When the ATE delivers a test pattern, the IAN is first configured through a sequence of SIB-addressable operations. Once the desired subnet is active, the ATE can shift in instrument-specific stimulus and shift out response data via the standard JTAG TDI/TDO pins. Crucially, the number of scan cycles used is proportional only to the length of the active path, not the total number of instruments in the device. This data reduction is the core of IJTAG’s efficiency. The standard defines a PDL (Procedural Description Language) for describing instrument behavior and a ICL (Instrument Connectivity Language) for describing the network topology. These languages are essential for tool interoperability, allowing ATE software to automatically generate IJTAG compliant patterns.

Why Automated Test Equipment Needs IEEE 1687

Traditional ATE systems rely heavily on prior testing methods such as functional testing, scan-based structural testing, and analog characterisation. As devices incorporate dozens of embedded instruments—like in-chip temperature sensors, voltage monitors, ring oscillators, and debug trace buffers—the test engineer faces a critical bottleneck: each instrument needs its own dedicated interface logic, or the test controller must be redesigned for every new device. IJTAG solves this by providing a universal, standardized access layer that the ATE can drive.

Limitations of Legacy JTAG (IEEE 1149.1)

  • No hierarchy: All boundary-scan cells are always in the shift path, making internal instrument access cumbersome.
  • Fixed scan path length: Any change in device integration requires a new boundary-scan register design.
  • Poor scalability: Adding more instruments forces longer serial test times.

IEEE 1687 overcomes these limitations by enabling the ATE to dynamically reconfigure the scan chain. This makes it possible to test deeply embedded analog and mixed-signal blocks without adding extra I/O pads—an invaluable capability for high-pin-count packages like BGA and chip-scale packages.

Reduction in Test Data Volume

One of the most quantifiable benefits of IEEE 1687 in ATE is the dramatic reduction in test data volume. In a traditional flat-scan approach, the entire scan path of a device might be hundreds of thousands of bits long. To access a single 32-bit temperature sensor, the ATE would have to shift through all other instruments. With IJTAG, the ATE configures the SIBs so that only the sub-chain containing the temperature sensor is included. The scan path becomes, for example, only 100 bits. The reduction in test time is proportional—often by orders of magnitude—which directly translates to lower cost of test and higher throughput. This is especially critical for high-volume manufacturing (HVM) where each second of test time matters.

Implementing IEEE 1687 in the ATE Test Flow

Integrating IJTAG into an ATE environment involves several steps, from design-for-test (DFT) insertion to final test program development.

Design Phase: ICL and PDL Generation

During chip design, EDA tools automatically insert SIBs and build the IAN. The tool outputs the ICL file describing the instrument network (hierarchy, segment lengths, SIB locations) and individual PDL files describing how to access and control each instrument. The ICL/PDL files are the key deliverables for the ATE engineer. They are vendor-neutral, meaning the same ICL/PDL set can be used with ATE systems from different suppliers (Teradyne, Advantest, Cohu, etc.) as long as the ATE software supports the standard.

Test Program Development

In the test program, the engineer uses the PDL procedures to build high-level tests. For example, to measure the on-chip voltage level, the ATE software can call a PDL procedure “measure_VDD_Sensor()” which automatically generates the correct sequence of SIB configurations and scan operations. This abstraction dramatically reduces code complexity and makes test patterns reusable across different hardware configurations.

Pattern Generation and Execution

Modern ATE systems incorporate IJTAG-aware pattern generators. They parse the ICL and PDL to produce optimized scan vectors. During execution, the ATE sends the vectors through the TAP, and the IAN automatically routes the data to the correct instrument. The ATE also expects the instrument to perform the required action (e.g., sample temperature) and then shift out the response. The ability to interleave configuration and data operations is a key strength of IEEE 1687.

Debug and Diagnosis

When a device fails, the ATE can use IJTAG to perform detailed diagnosis. By accessing internal scan chains, logic BIST results, or analog voltage monitors, the engineer can pinpoint the failing block. IJTAG’s hierarchical structure allows isolation of faults to specific cores, reducing the volume of data that needs to be dumped and analyzed. Many ATE systems now include automated IJTAG-based diagnostics that can produce a report showing the exact location of a stuck-at fault in a logic block.

Key Features of IEEE 1687 Supporting ATE Efficiency

  • Hierarchical access: SIB-controlled subnetworks allow testing of individual modules without affecting others, reducing pattern complexity.
  • Scalability: The same architecture works for a small MCU or a massive SoC with a thousand instruments.
  • Standardized interface: ICL/PDL are universal—ATE software from different vendors can consume the same files.
  • Reduced test time: Shorter active scan paths mean faster pattern execution and lower test cost.
  • Low pin count: Access to many instruments requires only the existing JTAG interface (TCK, TMS, TDI, TDO).
  • Instrument abstraction: PDL procedures hide hardware details, making test programs easier to maintain and port.

Benefits for Semiconductor Testing

Enhanced Test Coverage

IJTAG enables the ATE to reach instruments that were previously inaccessible in-package. For example, internal analog monitors can be used to measure power supply integrity during manufacturing, catching subtle weak spots that would escape traditional digital testing. The coverage improvement is especially valuable for safety-critical automotive and aerospace devices (e.g., ISO 26262 compliance).

Reduced Test Development Costs

With the ICL/PDL standard, teams do not need to rewrite instrument drivers for each new device. The same PDL can be reused across device families. This reduces the effort for test program development from months to weeks. The standardization also reduces the cost of diagnostic tool development because the interface is predictable.

Improved Diagnostic Capabilities

IEEE 1687 supports on-chip instrumentation for failure analysis. The ATE can run parametric measurements on internal nodes (voltage, temperature, frequency) during the test environment. If a device fails at a specific temperature corner, the engineer can program the on-chip temperature sensor to trigger a fault flag, then use IJTAG to read out the digital data. This correlation between environmental conditions and internal behavior is critical for root-cause analysis.

Future-Proofing Test Infrastructure

As semiconductor nodes shrink and devices become more heterogeneous (e.g., chiplets in advanced packages), IJTAG’s hierarchical nature becomes even more valuable. The standard already works across multiple die within a single package via the IEEE 1687.1 extension for die-to-die links. This ensures that the same ATE methods can scale to the 3D-IC era.

Challenges in IEEE 1687 Adoption for ATE

Integration with Existing ATE Architecture

Many ATE platforms were originally designed for IEEE 1149.1 primitives. Upgrading the software to handle ICL/PDL parsing and dynamic scan chain reconfiguration requires significant investment. Some vendors have responded by building IJTAG-specific pattern formats (e.g., Teradyne’s IJTAG pattern format), but interoperability is still an issue when moving between different ATE families.

Design Complexity for SIB Insertion

Inserting SIBs into a design consumes area and adds routing complexity. DFT engineers must balance the test access granularity with chip area. Over-zealous SIB insertion (too many segments) can make the IAN cumbersome; too few segments can limit the test time savings. Optimizing the SIB topology for the ATE test flow is a non-trivial task that requires collaboration between DFT and test engineering teams.

Ease-of-Use for Test Engineers

While the PDL abstraction helps, many test engineers are not hardware description language authors. They must learn PDL syntax and understand how their ATE software interprets it. The ecosystem of IJTAG-aware test development tools is still maturing, and some engineers find themselves writing low-level JTAG operations anyway, negating some of the standard’s benefits.

Future Outlook: Where IEEE 1687 Is Going

IEEE 1687 continues to evolve. The industry is actively working on extensions for per-pin control (allowing independent timing of TAP signals), support for asynchronous instrument access, and tighter integration with the IEEE 1838 standard for 3D-IC test access. The emergence of chiplet-based designs in high-performance computing (HPC) and AI accelerators will rely heavily on IJTAG to test inter-die interconnects and embedded instruments across the package.

Automated test equipment vendors are increasingly embedding IJTAG processing in their pattern controllers, enabling real-time SIB configuration at pattern-rate speed. This will allow IJTAG to be used not only for static configuration but also for dynamic frequency and voltage scaling tests.

For test engineers, the future points toward even deeper integration: ATE systems that can automatically import ICL/PDL from a design database and generate a complete test suite without manual coding. This vision—“plug-and-test” instrumentation—is the ultimate goal of IEEE 1687. Overcoming the remaining integration challenges will solidify IJTAG as the de facto standard for embedded instrument access in ATE for decades to come.

Conclusion

IEEE 1687 (IJTAG) has transformed the way automated test equipment interacts with complex semiconductor devices. By establishing a standardized, hierarchical instrument access network, it enables ATE to test more thoroughly in less time, with lower data volume and reduced development cost. The standard’s architecture of SIBs and ICL/PDL languages provides a scalable path for future multi-die packages. While adoption challenges remain—especially in ATE software integration and design optimization—the benefits in test coverage, diagnostics, and cost far outweigh the hurdles. As the semiconductor industry moves toward ever more integrated systems, IEEE 1687 will remain a critical enabler for quality and reliability in semiconductor manufacturing.

External links: