ScanWorks® JTAG IEEE 1532 Concurrent In-System Configuration

Product Overview

The IEEE 1532 Concurrent In-system Configuration product makes in-system configuration of programmable logic devices (PLD) easier and faster. Concurrent PLD configuration not only saves programming time, but it also simplifies the process by incorporating several operations into one. The total programming time for a board or system is often reduced from the sum of the times for programming each device individually to simply the longest time it would take to program any one device. The product is based on the IEEE std 1532™ -2002, Standard for In-System Configuration of Programmable Devices, in which ASSET InterTech played a key role in developing. Support for IEEE 1532 is seamlessly integrated into ScanWorks® so that PLDs from all major vendors can be configured concurrently on the same platform that performs boundary-scan test.

IEEE 1532

The IEEE 1532 standard was developed by a working group of experts from programmable logic vendors, the boundary-scan test industry and suppliers of in-circuit test systems. The mission of the group was “to define, document, and promote the use of a standardized process and methodology for implementing programming capabilities within programmable integrated circuit devices, utilizing (and compatible with) the IEEE 1149.1 communication protocol. This standard would allow the programming of one or more compliant devices concurrently, while mounted on a board or embedded in a system, known as "in-system configuration." Concurrent programming may often result in significant programming time efficiencies. The in-system feature would address the need to configure or reconfigure, read back, verify or erase programmable devices after they have been installed by manufacturing process. This eliminates handling damage and the need for manufacturing steps and inventory management related to preprogramming devices.”

The IEEE 1532 standard was adopted in 2001 and updated in 2002 to include a programming data file format. The standard requires that devices comply with the IEEE 1149.1 boundary-scan standard as an infrastructure for describing the algorithms for programming, erasing, verifying, securing and other programming operations for device families. This implies that these devices support the BSDL syntax necessary to describe IEEE 1532 and IEEE 1149.1 features to a boundary scan tools environment like ScanWorks. In addition, the IEEE 1532 standard defines a data format for the data that will be programmed into PLDs. For more detailed information about how IEEE 1532 is implemented, go to: http://grouper.ieee.org/groups/1532/p1532.PDF.

IEEE 1532 Concurrent ISC Support in ScanWorks

Support for IEEE 1532 concurrent ISC is an optional ScanWorks feature that is accessed through a distinct ScanWorks action. IEEE 1532 Concurrent ISC uses the same design description that is used by ScanWorks to perform boundary-scan testing, eliminating any need to re-work design descriptions for IEEE 1532 support. ScanWorks’ only requirement for IEEE 1532 is that the BSDL files for any IEEE 1532-compliant devices must include descriptions of the devices’ IEEE 1532 features. All PLD vendors that support IEEE 1532 provide such BSDL files on their web sites. Moreover, ASSET is creating a special web-based library for BSDL files for IEEE 1532 devices.

A ScanWorks IEEE 1532 ISC action has all of the features of every other ScanWorks action. It can be defined and applied on a ScanWorks development station or included in a test sequence that will be applied by a ScanWorks manufacturing station. An IEEE 1532 ISC action can also be called from a custom user interface developed with ScanWorksAPI or the Process Automation Scripting API. From the IEEE 1532 ISC action dialog, the user selects the devices to be programmed and the IEEE 1532 programming data files for each device. Then the programming operations to be executed for each device and any necessary preconditions are set. Lastly, if more than one scan path is present on the design, the scan path that will be activated for the ISC action is designated.

Previous : Next                    Page 1 of 2