IEEE Standard (JTAG) in the Axcelerator Family

Similar documents
JTAG Boundary- ScanTesting

Y. Tsiatouhas. VLSI Systems and Computer Architecture Lab. Boundary Scan (JTAG ) 2

Using the XC9500/XL/XV JTAG Boundary Scan Interface

Section 24. Programming and Diagnostics

11. JTAG Boundary-Scan Testing in Stratix V Devices

Section 24. Programming and Diagnostics

EMPTY and FULL Flag Behaviors of the Axcelerator FIFO Controller

12. IEEE (JTAG) Boundary-Scan Testing for the Cyclone III Device Family

Product Update. JTAG Issues and the Use of RT54SX Devices

Testing Sequential Logic. CPE/EE 428/528 VLSI Design II Intro to Testing (Part 2) Testing Sequential Logic (cont d) Testing Sequential Logic (cont d)

Chapter 19 IEEE Test Access Port (JTAG)

Using IEEE Boundary Scan (JTAG) With Cypress Ultra37000 CPLDs

3. Configuration and Testing

Device 1 Device 2 Device 3 Device 4

A Briefing on IEEE Standard Test Access Port And Boundary-Scan Architecture ( AKA JTAG )

8b10b Macro. v2.0. This data sheet defines the functionality of Version 1.0 of the 8b10b macro.

Overview of BDM nc. The IEEE JTAG specification is also recommended reading for those unfamiliar with JTAG. 1.2 Overview of BDM Before the intr

Comparing JTAG, SPI, and I2C

16 Dec Testing and Programming PCBA s. 1 JTAG Technologies

18 Nov 2015 Testing and Programming PCBA s. 1 JTAG Technologies

the Boundary Scan perspective

Ilmenau, 9 Dec 2016 Testing and programming PCBA s. 1 JTAG Technologies

7 Nov 2017 Testing and programming PCBA s

JRC ( JTAG Route Controller ) Data Sheet

Unit V Design for Testability

HCS08 SG Family Background Debug Mode Entry

UNIT IV CMOS TESTING. EC2354_Unit IV 1

SµMMIT E & LXE/DXE JTAG Testability for the SJ02 Die

Lecture 17: Introduction to Design For Testability (DFT) & Manufacturing Test

BTW03 DESIGN CONSIDERATIONS IN USING AS A BACKPLANE TEST BUS International Test Conference. Pete Collins

XJTAG DFT Assistant for

Digital Integrated Circuits Lecture 19: Design for Testability

Based on slides/material by. Topic Testing. Logic Verification. Testing

TMS320C6000: Board Design for JTAG

XJTAG DFT Assistant for

Chapter 10 Exercise Solutions

In-System Programmability Guidelines

XJTAG DFT Assistant for

XJTAG DFT Assistant for

Based on slides/material by. Topic 14. Testing. Testing. Logic Verification. Recommended Reading:

Introduction to JTAG / boundary scan-based testing for 3D integrated systems. (C) GOEPEL Electronics -

SN74ABT18502 SCAN TEST DEVICE WITH 18-BIT REGISTERED BUS TRANSCEIVER

SµMMIT E & LXE/DXE Built-In-Self-Test Functionality for the JA01 Die

NS8050U MICROWIRE PLUSTM Interface

Section 24. Programming and Diagnostics

Tools to Debug Dead Boards

Application Note PG001: Using 36-Channel Logic Analyzer and 36-Channel Digital Pattern Generator for testing a 32-Bit ALU

V6118 EM MICROELECTRONIC - MARIN SA. 2, 4 and 8 Mutiplex LCD Driver

SignalTap Plus System Analyzer

Scan. This is a sample of the first 15 pages of the Scan chapter.

Lecture 23 Design for Testability (DFT): Full-Scan

Lecture 23 Design for Testability (DFT): Full-Scan (chapter14)

of Boundary Scan techniques.

Raspberry Pi debugging with JTAG

University of Arizona January 18, 2000 Joel Steinberg Rev. 1.6

Saving time & money with JTAG

Chenguang Guo, Lei Chen, and Yanlong Zhang

SMPTE-259M/DVB-ASI Scrambler/Controller

JTAG Test Controller

2.6 Reset Design Strategy

BABAR IFR TDC Board (ITB): system design

Registers and Counters

Using the XSV Board Xchecker Interface

BSDL Validation: A Case Study

BOARD TEST The powerful combination of flying probe test and JTAG test speeds up testing

Design Techniques for Radiation-Hardened FPGAs

D Latch (Transparent Latch)

Chapter 4. Logic Design

Testing Digital Systems II

IT T35 Digital system desigm y - ii /s - iii

SignalTap Analysis in the Quartus II Software Version 2.0

Concurrent Programming through the JTAG Interface for MAX Devices

MODULE 3. Combinational & Sequential logic

0 0/1 0/1 0/1 0/1 0/1 0/1 0/1 0/1 1 1 Stop bits. 11-bit Serial Data format

Remote Diagnostics and Upgrades

Microcontrollers and Interfacing week 7 exercises


Testability: Lecture 23 Design for Testability (DFT) Slide 1 of 43

Chapter 8 Design for Testability

L12: Reconfigurable Logic Architectures

Sequential Logic Basics

Laboratory Exercise 4

K.T. Tim Cheng 07_dft, v Testability

BUSES IN COMPUTER ARCHITECTURE

DIGITAL SYSTEM FUNDAMENTALS (ECE421) DIGITAL ELECTRONICS FUNDAMENTAL (ECE422) COUNTERS

CSE140: Components and Design Techniques for Digital Systems. More D-Flip-Flops. Tajana Simunic Rosing. Sources: TSR, Katz, Boriello & Vahid

L11/12: Reconfigurable Logic Architectures

Simulation Mismatches Can Foul Up Test-Pattern Verification

2. Logic Elements and Logic Array Blocks in the Cyclone III Device Family

Programmable Logic Design I

Using on-chip Test Pattern Compression for Full Scan SoC Designs

description SCAS668A NOVEMBER 2001 REVISED MARCH 2003 Copyright 2003, Texas Instruments Incorporated

CMOS Testing-2. Design for testability (DFT) Design and Test Flow: Old View Test was merely an afterthought. Specification. Design errors.

FPGA Design. Part I - Hardware Components. Thomas Lenzi

Digital Circuits 4: Sequential Circuits

CHAPTER1: Digital Logic Circuits

Logic Devices for Interfacing, The 8085 MPU Lecture 4

OpenOCD - Beyond Simple Software Debugging

Chapter 5 Flip-Flops and Related Devices

Why FPGAs? FPGA Overview. Why FPGAs?

Transcription:

Application Note AC27 IEEE Standard 49. (JTAG) in the Axcelerator Family Introduction Testing modern loaded circuit boards has become extremely expensive and very difficult to perform. The rapid development of surface-mount technology and the use of multi-layer boards has increased board complexity. Finer pin spacing and double-sided boards have also contributed to the increasing cost and difficulty of testing. Traditional testing uses methods such as in-circuit testing by bed-of-nails and functional testing. Although functional testing can cope with complex and dense boards, it is costly because different designs require different sets of test programs. The test architecture was developed by the Joint Test Action Group and later adopted by IEEE as the IEEE Standard Test Access Port and Boundary-Scan Architecture (also referred to as IEEE Standard 49. or informally known as JTAG). The standard provides a cost-effective method of board testing through use of the boundary-scan technique. Boundary scan provides the means to test each component's required performance, interconnections, and interaction. In addition to describing boundary scan, the standard also describes the design-for-test feature. Overview The Actel Axcelerator family devices are compliant with IEEE Standard 49.. Figure shows the major parts that make up the JTAG test logic circuit. The circuit provides the required components (Test Access Port controller and registers) to support all the mandatory boundary-scan instructions (EXTEST, SAMPLE/ PRELOA, and BYPASS) as well as six optional public instructions (INTEST, USERCOE, ICOE, iagnostic, HIGHZ, and CLAMP). The diagnostic instruction is very similar to the JPROBE instruction on Actel s legacy parts. Test ata Registers TI Instruction ecode Test Access Port Instruction Register TMS TCK TRST TAP Controller TO Figure JTAG Block iagram. There are two minor exceptions. See the"instructions" section on page 6 and the "Axcelerator I Code" section on page 7. February 25 25 Actel Corporation

IEEE Standard 49. (JTAG) in the Axcelerator Family JTAG Mode Selection Enter JTAG test logic mode in Actel esigner software by selecting Tools > evice Selection. Click Next and the Variations dialog box appears, as shown in Figure 2. Click the Reserve JTAG check box to reserve pins for JTAG (dedicated mode). edicated mode is recommended if JTAG is to be used extensively. If the box is not checked, flexible mode is selected by default. The JTAG dedicated mode can also be selected when using TCL scripting by adding the command: set_device -jtag "yes" If the unshaded box, Reserve JTAG Test Reset, appears (SX-A or ex devices), the user also has the option of reserving a pin for the JTAG TRST signal (see the "Test Access Port (TAP)" section). The JTAG TRST pin can be reserved when using TCL scripting with the command: set_device -trst "yes" These can also be done with a single line: set_device -jtag "yes" -trst "yes" 2 Figure 2 SX-A evice Selection ialog Box Test Access Port (TAP) Each test logic function is accessed through the Test Access Port. The five pins associated with the TAP are listed in Table on page 3 with their corresponding descriptions. Four pins TMS, TCK, TI, and TO are always required for JTAG operation. The fifth pin, TRST, is optional. These pins are dedicated pins used only with the test logic. If flexible mode is selected, three of the pins TCK, TI, and TO are free to be used as regular I/O pin (Figure 3 on page 4). Note that TRST (if present) and TI are equipped with internal pull-up resistors. This means that these pins do not need to be terminated in either flexible or dedicated mode to ensure proper JTAG operation. In dedicated mode, the TMS pin is equipped with a pull-up resistor to place the TAP controller in the reset state (after a minimum of 5 TCK pulses) when no input is present. In flexible mode, there is NO pullup resistor; an external kω pull-up resistor is required. The test logic was designed to be in the reset state on power-up. 2. This has been tested in a simple ex64-t64 design and the only variables affected are the RESTRICTJTAGPINS and RESTRICTTRSTPIN, respectively. 2

IEEE Standard 49. (JTAG) in the Axcelerator Family Table Test Access Port escriptions Port TMS (Test Mode Select) TCK (Test Clock Input) TI (Test ata Input) TO (Test ata Output) TRST (Test Reset) escription Serial input for the test logic control bits. ata is captured on the rising edge of the test logic clock (TCK). An internal pull-up resistor is present in dedicated mode but not in flexible mode. See the "Test Access Port (TAP)" section on page 2 for more information. edicated test logic clock used serially to shift test instruction, test data, and control inputs on the rising edge of the clock, and serially to shift the output data on the falling edge of the clock. The maximum clock frequency for TCK is 2 MHz. Serial input for instruction and test data. ata is captured on the rising edge of the test logic clock. This pin is equipped with an internal pull-up resistor. Serial output for test instruction and data from the test logic. TO is set to an Inactive rive state (high impedance) when data scanning is not in progress. Active-low input which asynchronously resets the test logic. This pin is equipped with an internal pull-up resistor. TRST Pin The Axcelerator device is equipped with a dedicated TRST pin. The TRST overrides the behavior of TMS and TCK. In other words, asserting TRST will reset the TAP controller regardless of the states of TMS and TCK. Also, if the TAP controller is held in reset, asserting TMS and TCK will have no effect. The TAP controller will remain in the reset state. The TRST pin is equipped with an internal kω pull-up resistor. TAP Controller The 6 states of the tap controller state machine are shown in Figure 4 on page 4. The s and s shown adjacent to the state transitions represent the TMS values that must be present at the time of a rising edge at TCK for a state transition to occur. In the states that include the letters -IR, the instruction register operates; in the states that contain the letters -R, the test data register operates (bypass, boundary-scan, and XY-registers). The TAP controller receives two control inputs, TMS and TCK, and generates control and clock signals for the rest of the test logic architecture, as illustrated in Figure 5 on page 5. On power-up (or on the assertion of TRST), the TAP controller enters the Test-Logic Reset state. To reset the controller from any other state, TMS must be held high for at least five TCK cycles. After reset, the TAP controller's state changes at the rising edge of TCK based on the value of TMS. Note: The value shown adjacent to the state transitions in Figure 4 on page 4 represents the signal present at TMS at the time of the rising edge of TCK. 3

IEEE Standard 49. (JTAG) in the Axcelerator Family TMS TCK TCK, TI, and TO act as regular I/Os JTAG Operation Exiting JTAG Mode TCK, TI, and TO act as regular I/Os Figure 3 Entering and Leaving JTAG Flexible Mode Test_Logic_Reset Run_Test/ Idle Select_ R_Scan Capture_R Select_ IR_Scan Capture_IR Shift_R Shift_IR Exit_R Exit_IR Pause_R Pause_IR Exit2_R Exit2_IR Update_R Update_IR Figure 4 TAP Controller State iagram 4

IEEE Standard 49. (JTAG) in the Axcelerator Family TMS TCK TRST Tap Controller SHIFT_R CLK_R UPT_R SELECT ENABLE BSEINB SHIFT_IR CLK_IR UPT_IR Figure 5 TAP Controller Block iagram Instruction Register The instruction register (IR) consists of five IR cells. Each cell has a shift-register stage and a latch stage (Figure 6). On the Capture_IR state, the shift register is loaded with bits, which are used for fault isolation of the board-level serial test data path. The TI-IR-TO path is established on the Shift_IR state. ata in the shift register is shifted toward TO, and data in the latch remains the same. The data in the shift registers is latched out and becomes the current instruction on the falling edge of the TCK in the Update_IR state. When the TAP controller enters the Test-Logic Reset state, bits are latched in the IR, which corresponds to the ICOE instruction, and the data in the shift register cell retain their previous values. Table 2 on page 6 shows the summary of the operation of the instruction register. Parallel Out Shift_IR Serial In Serial Out Clock_IR EN Update_IR Parallel In Current Instruction TI TO Status ata Figure 6 Instruction Register Block iagram 5

IEEE Standard 49. (JTAG) in the Axcelerator Family Table 2 Instruction Register Operation Controller State Shift-Register Stage Latch Stage Test_Logic_Reset Undefined ICOE Instruction (IR4 IR = ) Capture_IR is loaded Retain Previous State Shift_IR Shift ata Toward TO Retain Previous State Exit_IR Retain Previous State Retain Previous State Exit2_IR Pause_IR Update_IR Retain Previous State Latch ata from Shift Register All Other States Undefined Retain Previous State Instructions Table 3 lists the supported instructions with their corresponding IR codes and descriptions. Because some unused opcodes are employed during Actel testing, all unused opcodes should be considered reserved. Note that the INTEST instruction does not fully comply with rule 7.8.(b) of IEEE Standard 49.-99. No single-step capability for the three clock inputs HCLK, CLKA, and CLKB is provided because these are highperformance clock pins and only "observable" boundary-scan cells are included in the scan chain. The same comment applies to the quadrant clocks (CLKA/B/C/) on the A54SX72A and the RT54SX72S. Table 3 Supported Public Instructions Instruction IR Code (IR4 IR) Instruction Type escription EXTEST Mandatory Allows testing of off-chip circuitry and board-level interconnections SAMPLE/PRELOA Mandatory Allows a snapshot of the normal operation of the component to be taken and examined INTEST Optional Allows testing of on-chip system logic while component is assembled on the board USERCOE Optional -bit user-programmable identification code ICOE Optional -bit hard-wired Actel I, part number, and version number HIGHZ Optional Tristates all I/Os to allow external signals to drive pins. CLAMP Optional Allows state of signals driven from component pins to be determined from the Boundary-Scan Register. iagnostic Optional Allows microprobing of internal logic module's output logic state BYPASS Mandatory Provides minimum-length (-bit) serial path between TI and TO pins of component when no test operation of that component is required 6

IEEE Standard 49. (JTAG) in the Axcelerator Family Axcelerator I Code The JTAG standard specifies that a JTAG compliant device must have the I Code register or the Bypass register connected between TI and TO immediately after a power-on reset, this allows a JTAG tester to obtain the device I code and any other information contained in the identification registers of the device. The Axcelerator device connects the I Code register after the power-on reset. This scheme allows a JTAG tester to shift out the I code of the device (or devices in a daisy-chain) and verify that the correct devices are soldered onto the board. The JTAG standard also specifies that an I Code must be bits, though the Axcelerator device has an expanded 33-bit I code to improve post programming verification of the charge pump. With testers that support user customization, such as Teradyne's J75, this 33-bit I code is not an issue. For these testers, the user simply configures the tester to shift out 33 bits instead of bits on the Axcelerator device. However, some testers have limited or restricted options for user customization and the Axcelerator 33-bit I Code may generate an error. Some testers perform a blind interrogation of the daisy-chain (a daisy-chain can contain one single device) to verify the devices in the chain. When a blind interrogation is performed, these testers default to a standard setting and assume all the devices in the chain contain -bit I codes; when reading out the Axcelerator 33-bit I code some tools will incorrectly recognize this as an invalid ICOE. Figure 7 is an example of a chain in which all devices have -bit I codes. When blind interrogation is performed, the software simply reads bits at a time to obtain the correct I code. Figure 8 on page 8 is an example of what happens when the 33-bit I code is introduced to the chain. The 33-bit I code may cause some tools to misread the I codes of the devices after the 33-bit I code device. In the event the tester in use will not allow the user to implement the previous solution, it is recommended to omit or bypass the Axcelerator I Code check in the test flow. Once the I Code check is bypassed, the user can perform complete functional JTAG testing on the chain. For some testers, such as JTAG technologies, simply removing the I Code register from the BSL file is sufficient. Removing the I Code register from the BSL file will enable the JTAG technology tester to automatically put the Axcelerator device into bypass mode. Once the Axcelerator device is in bypass mode, it will contribute only a single bit to the I code of the entire chain (Figure 9 on page 8). This will allow the user to verify the I codes of all other devices in the chain. The Axcelerator device supports all the necessary JTAG instructions and tests. The 33-bit I code will not prevent users from using any of the JTAG instructions and tests. Some JTAG testers may require some user customization to accommodate the Axcelerator 33-bit I code. To handles issues related to the 33-bit I code, Actel recommends contacting the manufacturer of the tester to obtain the most up to date solution. MSB LSB evice #3 evice #2 Axcelerator evice # Software and Actual Figure 7 Chain Containing -Bit I Code evices Only 7

IEEE Standard 49. (JTAG) in the Axcelerator Family evice #3 evice #2 evice # Actual MSB LSB 3 33 evice #3 evice #2 Axcelerator Actual Figure 8 Chain Containing 33-Bit I Code evice MSB LSB evice #3 evice #2 Axcelerator evice # Software and Actual Figure 9 Axcelerator evice in Bypass Mode Bypass Register The Bypass register is a single-bit register that provides a minimum data path between the TI and TO pins (Figure ). The bypass register is selected when the BYPASS, HIGHZ, or CLAMP instruction is the current instruction in the instruction register. On the Capture_R controller state, is loaded into the bypass register. Test data can then be shifted from the TI pin to the TO pin on the Shift_R state. ata movement throughout the bypass register is terminated when it moves into the Update_R controller state. Table 4 shows a summary of the operation of the bypass register. TI Bypass Register TO (Capture_R State) Figure Bypass Register iagram 8

IEEE Standard 49. (JTAG) in the Axcelerator Family Table 4 Bypass Register Operation Controller State Test-Logic-Reset Capture_IR Shift_IR Exit_IR Bypass Register Retain previous state '' is loaded Shift data toward TO Retain previous state Exit2_IR Pause_IR Update_IR All Other States Retain previous state Undefined Boundary-Scan Register The boundary-scan register is used to observe and control the state of each system pin. Note that clock pins can only be observed, not controlled. Each boundary-scan cell consists of serial input (SI) and serial output (SO) that are connected to each cell, as shown in Figure 6 on page 5. In addition, each boundaryscan cell (BSC) consists of a parallel input (PI) and a latched parallel output (PO) that connect to the system logic and system output. Three cells are used for each I/O an input cell (BS2), an output cell (BS), and an output-enable cell (BS). The operation of the boundary-scan register during specific boundary-scan instructions is described in Table 5 on page and Table 6 on page. If the EXTEST instruction is not being used in conjunction with the SAMPLE/PRELOA instruction, the external test starts by shifting the desired test data into the boundary-scan register in the Shift_R controller state. By moving into the Update_R controller state, data shifting is terminated. The falling edge of the TCK, the data from the shift-register stage is transferred onto the parallel output of the latch stage. The external test results are loaded into the shiftregister stage from the system input in the next Capture_R controller state. These results are examined by shifting the data toward TO on the next Shift_R controller state. uring the SAMPLE/PRELOA instruction, the Shift_R state is used to shift out the data captured from the system input and output pins for examination during the Capture_R state. At the same time, the Shift_R state shifts in test data to be used by the next boundary-scan instruction (other than SAMPLE/PRELOA). The EXTEST instruction is usually initiated following the SAMPLE/PRELOA instruction. The data pre-loaded during the SAMPLE/ PRELOA instruction phase becomes available at the parallel output of the boundary-scan cells when the EXTEST becomes the current instruction on the rising edge of TCK in the Update-IR state. Similarly, the CLAMP instruction is usually initiated following the SAMPLE/PRELOA instruction. The latched data in the boundary-scan cell becomes available to the system output pins when CLAMP becomes the current instruction and when the bypass register is selected as the data path from TI to TO. uring the SAMPLE/PRELOA instruction, the parallel input and output of the boundary-scan cells are transparent (PI equals PO). 9

IEEE Standard 49. (JTAG) in the Axcelerator Family Table 5 Operation Summary of EXTEST Instruction Controller State Boundary-Scan Shift-Register Stage Boundary-Scan Latch Stage Parallel Output (PO) Test_Logic_Reset Undefined Undefined Parallel In = Parallel Out Capture_R ata at PI Is Loaded Retain previous state Latched ata Shift_R Shift ata Toward TO Retain previous state Latched ata Exit_R, Exit2_R, Pause_R Retain Previous State Retain previous state Latched ata Update_R Retain Previous State Latches ata from Shift Register Latched ata = Parallel Out All Other States Retain Previous State Retain previous state Latched ata Table 6 Operation Summary of SAMPLE/PRELOA Instruction Controller State Boundary-Scan Shift-Register Stage Boundary-Scan Latch Stage Parallel Output (PO) Test_Logic_Reset Undefined Undefined Parallel In = Parallel Out Capture_R Retain Previous State ata at PI is loaded Parallel In = Parallel Out Shift_R Shift ata Toward TO Retain previous state Parallel In = Parallel Out Exit_R, Exit2_R, Pause_R Retain Previous State Retain previous state Parallel In = Parallel Out Update_R Retain Previous State Latches data from Shift Parallel In = Parallel Out Register All Other States Retain Previous State Retain previous state Parallel In = Parallel Out Note: uring the SAMPLE/PRELOA instruction, the parallel input and output of the boundary-scan cells are transparent (PI equals PO). iagnostic Instruction The diagnostic instruction (IR code ) allows microprobing of internal module outputs. This is done via an XY-register. The scan chain structure is illustrated in Figure on page. The XY-register consists of a shift register whose length depends on the specific part. The registers that are darkened are not parts of the XY-register. The presence of the XY-register and the diagnostic instruction permits the use of the internal probe circuitry to observe and analyze any signal inside an Actel chip via JTAG. The desired probe address is shifted into the XY-register by first selecting the diagnostic instruction and then moving to the Shift_R controller state. Shifting is discontinued by entering the Update_R controller state. The probe results are loaded into the XY-register on the rising edge of TCK in the next Capture_R controller state. The probe results can be examined by moving back to the Shift_R controller state and shifting the result toward TO. Table 7 on page shows the summary of the diagnostic instruction's operation. The probe results may also be observed in real time at the probe pins (PRA and PRB), provided that these pins have been reserved for probe use.

IEEE Standard 49. (JTAG) in the Axcelerator Family Figure Functional Schematic of the XY-Register Table 7 Operation Summary of iagnostic Instruction Controller State XY-REG Register XY-REG Latch Stage Test_Logic_Reset Logic '' Logic '' Capture_R Probe Result Loaded when Valid Probe Register Address Retain Previous State Shift_R Shift In New Address and Shift Out Probe Result Toward TO Retain Previous State Exit_R, Exit2_R,Pause_R Retain Previous State Retain Previous State Update_R Retain Previous State Latch ata from Shift Register All Other States Undefined Undefined TI XY-REG (White Registers) /4 Array /4 Array /4 Array /4 Array TO

IEEE Standard 49. (JTAG) in the Axcelerator Family Boundary-Scan escription Language (BSL) File Conforming to the IEEE Standard 49. requires that the operation of the various JTAG components be documented. The BSL file provides the standard format to describe the JTAG components that can be used by automatic test equipment software. The file includes the instructions that are supported, instruction bit pattern, and the boundary-scan chain order. Note that if a general-purpose I/O in a customer design is configured as either an output (OUTPUT) or a tristate buffer (TRIBUF), the input for that pad and hence the JTAG input boundary-scan cell (the lower cell in Figure on page ) is disabled. This cell does not exist in the BSL file generated by esigner Software. References. Colin M. Maunder & Rodham E. Tulloss. The Test Access Port and Boundary-Scan Architecture. IEEE Computer Society Press, Los Alamitos. 2. "IEEE Std 49.-993, IEEE Standard Test Access Port, and Boundary-Scan Architecture." IEEE, Inc., New York. 3. Kenneth P. Parker. The Boundary-Scan Handbook. Kluwer Academic Publishers, Norwell. 2

Actel and the Actel logo are registered trademarks of Actel Corporation. All other trademarks are the property of their owners. www.actel.com Actel Corporation 26 Stierlin Court Mountain View, CA 9443-4655 USA Phone 65.38.42 Fax 65.38.46 Actel Europe Ltd. unlop House, Riverside Way Camberley, Surrey GU5 3YL United Kingdom Phone +44 () 276 4 45 Fax +44 () 276 4 49 Actel Japan www.jp.actel.com EXOS Ebisu Bldg. 4F -24-4 Ebisu Shibuya-ku Tokyo 5 Japan Phone +8.3.3445.767 Fax +8.3.3445.7668 Actel Hong Kong www.actel.com.cn Suite 24, Two Pacific Place 88 ueensway, Admiralty Hong Kong Phone +852 285 646 Fax +852 285 6488 5992-/2.5