XDS100 1

What is the XDS100?

€ The XDS100 emulator is Texas Instruments' ultra-low-cost USB-interface JTAG hardware reference design.

€ The XDS100 emulator provides JTAG access to Texas Instruments' JTAG based devices.

€ It is compatible with Code Composer Studio™ development environment.

€ TI creates the reference design and our 3rd party partners create the JTAG emulator products for end use.

€ The XDS100s are available as discrete emulators, or can be embedded on a development card (DSK, EVM, etc.).

€ There are 3 versions of the XDS100. The XDS100v1 is the original XDS100 design. The XDS100v2 is an

The Texas Instruments' reference design for XDS100 has the following features (Please check your vendor for

hardware details):

€ Debug features (Emulation Connect/Disconnect, Read/Write memory, Read registers, Load program, Run, Halt,

Step, Software and Hardware Breakpoint support, Real-Time Mode)

€ Compatible with Code Composer Studio™.

€ Support for targets with 1.8v and 3.3v IO voltages.

€ Support for “JTAG reset”/"wait-in-reset" boot-modes using the two EMU pins sampled by the nTRST pin.

€ Support for “Power-on reset” boot-modes using the two EMU pins sampled by the TVD pin.

€ Support for the configuration of the EMU pin features through Code Composer Studio™ Setup “connection

mode for compatibility with Code Composer Studio v3.3.

€ XDS100v3 emulators are recommended for users who require support for IEEE 1149.7, most devices do not

require this.

€ XDS100v2 is the default recommended XDS100 emulator.

XDS100 2

XDS100v1 Features

The Texas Instruments' reference design for XDS100v1 has the following features. Please check with your vendor as

to whether the all of the below features are supported:

€ All of the XDS100 General Features

€ Support for USB Full Speed (12 Mbits/s)

€ Support for multiple FTDI devices (CCSv4 only)

€ All of the XDS100 General Features

€ Support for USB High Speed (480 Mbit/s)

€ Support targets with 14-pin TI JTAG connector or 20-pin TI JTAG connector as used by Texas Instruments

embedded processors. (Please check your vendor for hardware details)

€ Support for the following processor cores: TMS320C28x, TMS320C54x, TMS320C55x, TMS320C64x+,

TMS320C674x, TMS320C66x, ARM 9, ARM Cortex R4, ARM Cortex A8, ARM Cortex A9 and Cortex M3

(requires CCSv4.2.2 or later).

€ Supports cable-break detection

€ Supports target power loss detection

€ Support for multiple FTDI devices

The Texas Instruments' reference design for XDS100v3 has the following features. Please check with your vendor as

to whether the all of the below features are supported:

€ All of the XDS100 General Features

€ IEEE 1149.7 capable emulator with a USB interface.

€ Can function as an 1149.7 adapter for use with existing scan controllers.

€ Support for ARM Ltd's Single Wire Output (SWO).

€ Software compatible with XDS100v2 (except link delay and IEEE 1149.7 modes).

€ Physical jumper to select emulator or adapter mode.

€ Operates in 1149.7 Class 4, up to 25MHz.

€ LED to indicate IEEE 1149.7 Class 4 operation.

XDS100 3

Features NOT supported

€ It does not support Real Time Data eXchange (RTDX) or High Speed RTDX (HSRTDX)

€ It does not provide hardware support for TCLKR external clocking

XDS100 Installation Instructions

Installation for Code Composer Studio v5.1.x

Code Composer Studio v5.1.x Support (XDS100v1, XDS100v2 and XDS100v3•hardware)

Processor Family XDS100 Hardware

Code Composer Studio Release/Version Notes

TMS320C28xx v1, v2, v3 Code Composer Studio v5 page [1]•and

A. Install Code Composer Studio•5.1.x (XDS100v1 and XDS100v2 support is included)•as per the table above

C. Connect the XDS100 hardware

plugging in the XDS100 HW to the PC.

2. Connect USB cable from the PC to the XDS100 hardware. Connect the JTAG to the target board (be careful to

XDS100 4

3. Select device.

Installation for Code Composer Studio v4.x

Code Composer Studio v4.x Support (XDS100v1 and XDS100v2 hardware)

Processor Family XDS100 Hardware Version Code Composer Studio Release/Version Notes

XDS100 USB hardware.

B. Connect the XDS100 hardware

2. Connect USB cable from the PC to the XDS100 hardware. Connect the JTAG to the target board (be careful to

plug it in correctly: pin 1 should go to pin 1. Red strip usually indicates the side of pin 1)

3. You will notice small popups to inform user that USB hardware is recognized and installed correctly. No input

are required.

C. Setup Code Composer Studio v4.x

1. Start Code Composer Studio and create a new target configuration. See Quick Tips#Target_Setup.C2.A0

2. Select XDS100 as connection type (either XDS100 v1 or XDS100 v2)

XDS100 5

supported on Code Composer Studio v3.3.

XDS100 6

XDS100 7

XDS100 8

€ Blackhawk offers a USB 2.0 HIGH-SPEED XDS100-class JTAG Emulator with dual headers (14 and 20cTI)

XDS100 9

€ A: This can happen if the FDTI USB driver have not been properly uninstalled / re-installed (i.e. if CCSv4

uninstall did not complete properly). I resolved it by going to Device Manager then right click on:

€ A: Yes. The TI XDS100v2 reference design uses the port A of the FTDI2232H to be for JTAG. This leaves the

port B available for use either to program the CPLD and/or for use as a UART. The XDS100v2 design puts the

CPLD JTAG programming on a selected number of pins (see XDS100v2 readme for details). This allows the

CPLD to be programmed via the FTDI device, greatly simplifying manufacturing.

€ Please note that there is a known issue with the current XDS100v2 reference design with the placement of the

BCBUS. If you plan to use the port B, please check the readme of the XDS100v2 reference design for details.

[27]. The FTDI driver gives each half of the FTDI chip a seperate USB handle and USB endpoint, so they are

essentially independent. The FTDI supplied software is the software that is needed to get this support; there is no

TI specific software needed for this support.

XDS100v1 (Legacy)

€ A: The C2000 control card schematics implement an XDS100 design optimized for C28x processors. The design

C:\ccsv4\ccsv4\common\uscif>dbgjtag -f "C:\ccsv4\ccsv4\DebugServer\bin\win32\BrdDat\ccBoard0.dat" -rv -S pathlength

-----[Print the reset-command software log-file]-----------------------------

This utility will use the original port address '0'.

The controller does not use a programmable FPGA.

The emulator adapter uses the JIO interface.

The emulator adapter is named 'jioserdesusb.dll'.

The emulator adapter is version '35.34.0.7'.

The controller has a version number of '4' (0x00000004).

The controller has an insertion length of '0' (0x00000000).

This utility will now attempt to reset the controller.

The controller cannot monitor the value on the EMU[0] pin.

The controller cannot monitor the value on the EMU[1] pin.

The controller cannot control the timing on output pins.

The controller cannot control the timing on input pins.

The scan-path link-delay has been set to exactly '0' (0x0000).

This utility will use the original port address '0'.

The emulator adapter uses the JIO interface.

The emulator adapter is named 'jioserdesusb.dll'.

The emulator adapter is version '35.34.0.7'.

The controller has a version number of '4' (0x00000004).

€ A: It may also be that the FTDI EEPROM is not properly progrmmed. Please contact your XDS100 vendor to

or the chip failed to return the expected number of bytes to Code Composer Studio. In practice, this has usually

the device open. In the case where a software process hasn't terminated, it may be that Code Composer Studio

may not have terminated properly. Check the Windows Task Manager that Code Composer Studio related

processes are terminated prior to re-starting.

€ A: With CCS 4.1.2 and newer, a bug was fixed so that the XDS100 software could properly connect only to a

€ Please see previous topic

to U3. U3 provides a buffer which performs the voltage translation.

€ A: You can find the VID/PID in windows by using the windows device manager and selecting details. You can

also use the FTDI utilities such as MPROG or FT_Prog. When using MPROG or FT_Prog, you need to scan

devices to read the ID.

€ A: For some 28x based cards, a similar problem may occur

with these simple steps

like the one pictured below.

7. Select Device->Erase to erase the existing programming

cpld code, so it cannot be determined by software.

XDS100v2 CPLD via SW. If your manufacturer did not follow the XDS100v2 reference design, please contact

ARM9) is included with the updated CPLD. The specific items implemented in this CPLD update are:

1. TCK loopback when a power loss is detected

€ Please note that this CPLD update is designed for use with CCS v4.1.1 and newer.

inadvertently disables this feature.• It will be corrected in the next•XDS100v3 Design Kit update.

Article Sources and Contributors 24

Article Sources and Contributors

Icalzada, JNannes, Jeraldinesewell, Jlhunter, Joebahar, John, Lheustess, Mariana, Piternoize, Rsjsouza, SDIDAN, Shailesh, Steve, Tonycoomes, Y595906642

THE WORK (AS DEFINED BELOW) IS PROVIDED UNDER THE TERMS OF THIS CREATIVE COMMONS PUBLIC LICENSE ("CCPL" OR "LICENSE"). THE WORK IS PROTECTED BY COPYRIGHT AND/OR OTHER

APPLICABLE LAW. ANY USE OF THE WORK OTHER THAN AS AUTHORIZED UNDER THIS LICENSE OR COPYRIGHT LAW IS PROHIBITED.

BY EXERCISING ANY RIGHTS TO THE WORK PROVIDED HERE, YOU ACCEPT AND AGREE TO BE BOUND BY THE TERMS OF THIS LICENSE. TO THE EXTENT THIS LICENSE MAY BE CONSIDERED TO BE

A CONTRACT, THE LICENSOR GRANTS YOU THE RIGHTS CONTAINED HERE IN CONSIDERATION OF YOUR ACCEPTANCE OF SUCH TERMS AND CONDITIONS.

1. Definitions

that constitutes a Collection will not be considered an Adaptation for the purpose of this License. For the avoidance of doubt, where the Work is a musical work, performance or phonogram, the synchronization of the Work in

timed-relation with a moving image ("synching") will be considered an Adaptation for the purpose of this License.

separate and independent works in themselves, which together are assembled into a collective whole. A work that constitutes a Collection will not be considered an Adaptation (as defined below) for the purposes of this License.

available under that license under this License or a Creative Commons jurisdiction license with the same License Elements as this License.

f. "Licensor" means the individual, individuals, entity or entities that offer(s) the Work under the terms of this License.

producer being the person or legal entity who first fixes the sounds of a performance or other sounds; and, (iii) in the case of broadcasts, the organization that transmits the broadcast.

including digital form, such as a book, pamphlet and other writing; a lecture, address, sermon or other work of the same nature; a dramatic or dramatico-musical work; a choreographic work or entertainment in dumb show; a

musical composition with or without words; a cinematographic work to which are assimilated works expressed by a process analogous to cinematography; a work of drawing, painting, architecture, sculpture, engraving or

lithography; a photographic work to which are assimilated works expressed by a process analogous to photography; a work of applied art; an illustration, map, plan, sketch or three-dimensional work relative to geography,

otherwise considered a literary or artistic work.

i. "You" means an individual or entity exercising rights under this License who has not previously violated the terms of this License with respect to the Work, or who has received express permission from the Licensor to exercise

j. "Publicly Perform" means to perform public recitations of the Work and to communicate to the public those public recitations, by any means or process, including by wire or wireless means or public digital performances; to

make available to the public Works in such a way that members of the public may access these Works from a place and at a place individually chosen by them; to perform the Work to the public by any means or process and the

performance or phonogram in digital form or other electronic medium.

2. Fair Dealing Rights

Nothing in this License is intended to reduce, limit, or restrict any uses free from copyright or rights arising from limitations or exceptions that are provided for in connection with the copyright protection under copyright law or other

3. License Grant

a. to Reproduce the Work, to incorporate the Work into one or more Collections, and to Reproduce the Work as incorporated in the Collections;

4. Restrictions

The license granted in Section 3 above is expressly made subject to and limited by the following restrictions:

Publicly Perform. You may not offer or impose any terms on the Work that restrict the terms of this License or the ability of the recipient of the Work to exercise the rights granted to that recipient under the terms of the License.

You may not sublicense the Work. You must keep intact all notices that refer to this License and to the disclaimer of warranties with every copy of the Work You Distribute or Publicly Perform. When You Distribute or Publicly

Perform the Work, You may not impose any effective technological measures on the Work that restrict the ability of a recipient of the Work from You to exercise the rights granted to that recipient under the terms of the License.

This Section 4(a) applies to the Work as incorporated in a Collection, but this does not require the Collection apart from the Work itself to be made subject to the terms of this License. If You create a Collection, upon notice from

the terms of the Applicable License.

publishing entity, journal) for attribution ("Attribution Parties") in Licensor's copyright notice, terms of service or by other reasonable means, the name of such party or parties; (ii) the title of the Work if supplied; (iii) to the

extent reasonably practicable, the URI, if any, that Licensor specifies to be associated with the Work, unless such URI does not refer to the copyright notice or licensing information for the Work; and (iv) , consistent with

Ssection 3(b), in the case of an Adaptation, a credit identifying the use of the Work in the Adaptation (e.g., "French translation of the Work by Original Author," or "Screenplay based on original Work by Original Author"). The

which any exercise of the right granted in Section 3(b) of this License (the right to make Adaptations) would be deemed to be a distortion, mutilation, modification or other derogatory action prejudicial to the Original Author's

honor and reputation, the Licensor will waive or not assert, as appropriate, this Section, to the fullest extent permitted by the applicable national law, to enable You to reasonably exercise Your right under Section 3(b) of this

License (right to make Adaptations) but not otherwise.

5. Representations, Warranties and Disclaimer

6. Limitation on Liability

OR EXEMPLARY DAMAGES ARISING OUT OF THIS LICENSE OR THE USE OF THE WORK, EVEN IF LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

however, will not have their licenses terminated provided such individuals or entities remain in full compliance with those licenses. Sections 1, 2, 5, 6, 7, and 8 will survive any termination of this License.

license terms or to stop distributing the Work at any time; provided, however that any such election will not serve to withdraw this License (or any other license that has been, or is required to be, granted under the terms of this

b. Each time You Distribute or Publicly Perform an Adaptation, Licensor offers to the recipient a license to the original Work on the same terms and conditions as the license granted to You under this License.

agreement, such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable.

d. No term or provision of this License shall be deemed waived and no breach consented to unless such waiver or consent shall be in writing and signed by the party to be charged with such waiver or consent.

be bound by any additional provisions that may appear in any communication from You. This License may not be modified without the mutual written agreement of the Licensor and You.

f. The rights granted under, and the subject matter referenced, in this License were drafted utilizing the terminology of the Berne Convention for the Protection of Literary and Artistic Works (as amended on September 28, 1979),

the Rome Convention of 1961, the WIPO Copyright Treaty of 1996, the WIPO Performances and Phonograms Treaty of 1996 and the Universal Copyright Convention (as revised on July 24, 1971). These rights and subject

matter take effect in the relevant jurisdiction in which the License terms are sought to be enforced according to the corresponding provisions of the implementation of those treaty provisions in the applicable national law. If the

standard suite of rights granted under applicable copyright law includes additional rights not granted under this License, such additional rights are deemed to be included in the License; this License is not intended to restrict the

license of any rights under applicable law.