SEARCH:
JTAG  
View Leadership Video
New to JTAG/Boundary Scan?

PRODUCTS

BSDL Services:
BSDL Validation Service
ScanWorks®
Boundary-Scan Products:

Interconnect Development Station
Interconnect Repair Station
Test Development Station
Diagnostic & Repair Station
Manufacturing Station
Programming Stations
IEEE 1149.6
Emergency License Tokens
Hardware Overview

IBIST Products:
ScanWorks® Intel® IBIST
Emulation Products:
MicroMaster
ICT Products:
ScanWorks® for Agilent's Medalist ICT
Technology:
Test Automation
System-Level JTAG


FREE RESOURCES & VIDEOS

Free Resources & Videos

 

TRAINING

ASSET ScanWorks Training Classes

 

SUCCESS STORIES

View all our Success Stories

 

 

Boundary-Scan Tutorial:

RunBist Instruction

An important optional instruction is RunBist. Because of the growing importance of internal self-test structures, the behavior of RunBist is defined in the Standard. The self-test routine must be self-initializing (i.e., no external seed values are allowed), and the execution of RunBist essentially targets a self-test result register between TDI and TDO. At the end of the self-test cycle, the targeted data register holds the Pass/Fail result.

Clamp Instruction

Two new instructions introduced in the 1993 revision, 1149.1a-1993, were Clamp and HighZ. Clamp is an instruction that uses boundary-scan cells to drive preset values established initially with the Preload instruction onto the outputs of devices, and then selects the Bypass register between TDI and TDO (unlike the Preload instruction which leaves the device with the boundary-scan register still selected until a new instruction is executed or the device is returned to the Test_Logic Reset state.

Clamp would be used to set up safe guarding values on the outputs of certain devices in order to avoid bus contention problems, for example.

Previous : Next                    Page 15 of 28          Back to Page 1

Free Hit Counter Code