It's the future of advanced design validation, test and debug
Why Embedded Instruments?
The necessities that are driving the invention of embedded instrumentation arise from several imperatives. First, the speed and complexity of technology today, starting at the chip level, has escalated geometrically. Chip-to-chip interconnects and input/output (I/O) buses have blown past the gigabits-per-second (Gbps) and are pushing into the five to eight Gbps range. Moreover, the hundreds of millions and billions of gates now present on chips have increased the complexity of devices exceedingly. This has lead to multi-core devices, multi-chip devices, new complex packaging with multiple dies and other technologies, all of which complicate the design validation, test and debug process. Happily for system developers, manufacturers and support organizations, embedded instrumentation is much more cost-effective, efficient, agile and better suited to today’s emerging computer and communications technologies than are other alternatives. Embedded instruments are able to do certain aspects of design validation, test and debug that the technologies now deployed in the industry simply can not do. Necessity, of course, has had a lot to do with the invention of embedded instruments, but straightforward business sense will certainly carry it a long way in the marketplace as it becomes a critically important design validation, test and debug technology in the future.
Why is Embedded Instrumentation Needed?
Since the very beginning of the electronics industry, designers and manufacturing engineers have relied upon standalone, external instruments like oscilloscopes and logic analyzers to validate designs, verify the signal integrity on chip-to-chip interconnects and input/output (I/O) buses, test manufactured assemblies and diagnose failures. These external instruments, which invariably relied upon physical probes to determine what was happening on the chip or circuit board and in the system, performed their tasks with admirable distinction. But, as the complexity and speed of chips, buses and systems increased, as well as the sheer density and integration of semiconductor devices on boards escalated, the inadequacies of external and modular instrumentation have become immediately apparent. Moreover, new multi-core and multi-die chip packaging techniques such as system-in-package (SiP), package-on-package (PoP) and others are only exacerbating the chip-level validation, test and debug situation.
Consider these facts:
As a result of these and other instances of crippling deficiencies, design and test engineers have turned to embedded instrumentation because they need the solutions only embedded instrumentation can provide.
What are Embedded Instruments?
Embedded instruments can take many shapes and forms. Some experts in the industry expect that soon the capabilities of a complete oscilloscope will be embedded as an additional resource on a chip. The types of instruments that will be embedded will be determined by many factors, such as the needs of the application, the resources of the system and the ingenuity of the chip’s design team.
An IEEE working group is developing the Internal JTAG (IJTAG) standard (P1687). When ratified, this standard will specify methods for managing the configuration, operation, and collection of data from embedded instrumentation. This group defines embedded instrumentation as: “Any logic structure within a device with a purpose for Design-for-Test (DFT), Design-for-Debug (DFD), Design-for-Yield (DFY), Test...” This document goes on to say: “There exists the widespread use of embedded instrumentation (such as BIST Engines, Complex I/O Characterization and Calibration, Embedded Timing Instrumentation, etc.)…”
How Do Engineers Use Embedded Instrumentation?
At least initially, the ASSET ScanWorks platform will automate, acces and analyze instruments embedded at the chip level through the JTAG (boundary scan or IEEE 1149.1) port on chips and the JTAG infrastructure on circuit boards and in systems. Given the fact that ScanWorks is the leading tool for accessing JTAG resources and applying tests, this is a natural place to start for ASSET. However, future generations of the ScanWorks platform will likely incorporate the access method best suited to the application, chip technology and/or the embedded instruments involved in the application. In addition, ASSET’s MicroMaster CPU emulation system can also utilize the debug port found on many processors.
What does ScanWorks do?
ScanWorks automates, accesses and analyzes embedded instrumentation.
For example, pattern generation and checking is a basic functionality for the ScanWorks platform. This capability provides the basis for several instrumentation applications such as bit error rate testing (BERT) and margining. With pattern generation and checking, ScanWorks can validate the transfer of basic, user-definable test patterns across buses and even individual lanes on buses.
ScanWorks’ BERT testing capabilities can test individual lanes or multiple lanes simultaneously, accelerating design validation time as well as stressing a significant portion of the system to identify interrelated or dependent faults and failures. Margining gives the designer a push-button tool to generate graphical eye diagrams that visually demonstrate the signal integrity on high-speed channels in the system. An example of a graphical margining diagram appears below.

Where and When Is Embedded Instrumentation Used?
Embedded instrumentation can be called upon during every phase of a system’s life cycle. For example, design validation has a critical need for the capabilities of embedded instrumentation. Without it, the design team can not test and validate the signal integrity on high-speed buses. As the circuit board, sub-assembly or system move into manufacturing, embedded instrumentation will be used to perform at-speed tests and diagnose failures. And once the product has been deployed in the field, embedded instrumentation could be accessed and engaged locally or remotely by service technicians to diagnose performance issues and troubleshoot failures.
Who’s Doing What with Embedded Instruments?
ASSET InterTech has taken a leadership position in developing tools that automate, access and analyze embedded instrumentation. The ScanWorks environment is the only tool available today for Intel®’s Interconnect Built In Self Test (IBIST), an embedded instrumentation technology that Intel is designing into its next-generation processor chips and server platforms.
In addition to Intel’s IBIST, several other embedded instrumentation initiatives are underway at this time. These include the following:
Many companies are active in embedded instrumentation. Some of their initiatives are listed below:
The list above is by no means complete or comprehensive. Several others companies, including Tundra, Texas Instruments, LSI, Avago and others are also providing embedded instrumentation technology.
How Will Embedded Instruments Change the Design Validation/Test/Debug Landscape?
Over time, embedded instruments will have a profound effect on design validation, manufacturing test and other aspects of a system’s lifecycle, including debug. Embedded instruments give designers a cost-effective and software-driven alternative to external and modular test instruments. Greater agility and flexibility will result. Validation routines and tests can be applied practically anywhere and at any time because the needed instruments are already present in the system and application tools like ScanWorks are software-based.
Moreover, the thoroughness and comprehensive nature of design validation and manufacturing test will only be enhanced by embedded instrumentation. Not only will this accelerate the delivery of new products to market, but it will also improve the reliability, durability and overall quality of electronic systems.
What is the Industry Saying about Embedded Instruments?
“As the industry continues to expand high speed serial signal architecture demands, a growing dependency on IBIST is required for validating and testing the technology within Intel Corporation.”
Gene Pitts, Director Server Platforms, Technical Marketing, Intel Corporation
“With the growing complexity of SOC designs, leading design teams report that they are dedicating more and more planning, implementation, and silicon area to circuitry that supports debugging rather than test.”
Ron Wilson, Executive Editor, EDN Magazine in an article entitled: “Design for debugging: the unspoken imperative in chip design”, June 21, 2007
Boundary-Scan Products:
Interconnect Development Station
Emulation Products
ICT Products
ScanWorks for Agilent's Medalist ICT
IBIST Products
Hardware Products