This standard defines a mechanism for the test of core designs within a system on chip (SoC). This mechanism constitutes a hardware architecture and leverages the core test language (CTL) to facilitate communication between core designers and core integrators.
Working Group Details
IEEE Standard for In-System Configuration of Programmable Devices
The communication protocol described by IEEE Std 1149.1 TM -2001 (Standard Test Access Port and Boundary-Scan Architecture) has been adopted by this standard for providing standardized programming access and methodology for programmable integrated circuit devices.Devices that implement this standard will first be compliant with IEEE Std 1149.1-2001, which isused for testing purposes. A device, or set of devices, implementing this standard can be pro-grammed (written), read back, erased, and verified, singly or concurrently, with a standardized setof resources. Sample implementation and application details (which are not part of this standard)are included for illustrative purposes.
IEEE Standard for Extensions to Standard Test Interface Language (STIL) (IEEE Std 1450-1999) for Semiconductor Design Environments
Replaced by IEC 62526 Ed. 1 (2007-11. Standard Test Interface Language (STIL) provides an interface between digital test generation tools and test equipment. Extensions to the test interface language (contained in this standard) are defined that (1) facilitate the use of the language in the design environment and (2) facilitate the use of the language for large designs encompassing subdesigns with reusable patterns.
IEEE Standard for Extensions to Standard Test Interface Language (STIL) (IEEE Std 1450-1999) for DC Level Specification
Define structures in STIL for specifying the DC conditions for a device under test. Examples of the DC conditions for device power supplies are: device power supply setup, power sequencing to the device, power supply limit
IEEE Standard for Extensions to Standard Test Interface Language (STIL) (IEEE Std. 1450-1999) for Tester Target Specification
The STIL environment supports transferring tester-independent test programs to a specific ATE system. Although native STIL data are tester independent, the actual process of mapping the test program onto tester resources may be critical, and it is necessary to be able to completely and unambiguously specify how the STIL programs and patterns are mapped onto the tester resources. TRC (which stands for either tester resource constraints or tester rules checking, depending on the usage) is an extension to the STIL language to facilitate this operation.