1 Daikus

Xds100 Xds510 Comparison Essay

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 updated XDS100 design with more capability. The XDS100v3 is an updated XDS100v2 design with support for the 1149.7 protocol.
  • Performance of the XDS100 is lower than the XDS510 and XDS560. This means that program and data downloads will take a longer time than with XDS510 and XDS560 emulators. Also, stepping in "C" and "Assembly" will be slower with XDS100 when compared to XDS510 or XDS560 emulators.

General Features

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 properties” dialogs similar to those for the XDS560 Rev-D cable.
  • Support for “target power-loss detection” via the TVD pin even when Code Composer Studio™ is not running, and applying boot-modes at Code Composer Studio™ start-up.
  • Supports ETB trace

Which XDS100 is right for me?

  • XDS100v1 emulators are only recommended for users who need to use Code Composer Studio v3.3, anyone using Code Composer Studio v4 or later should consider an XDS100v2 or later emulator due to the increased performance.  Some of our 3rd Party partners have implemented XDS100v2 emulators that can also operate in v1 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.

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)
  • Support targets with 14-pin TI JTAG connector used by Texas Instruments embedded processors.
  • Support for the following processors cores: TMS320C28x, TMS320C54x, TMS320C55x, TMS320C64x+, TMS320C674x and TMS320C66x.

XDS100v2 Features

The Texas Instruments' reference design for XDS100v2 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 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 cores: A (A8, A9 and A15), M (M0, M3 and M4) and R (R4 and R5). Support for the cores was incrementally added across the releases - check the release notes for the version you are using.
  • Supports cable-break detection
  • Supports target power loss detection
  • Support for multiple FTDI devices
  • Adaptive clocking
  • LED light to indicate active USB connection
  • Support for Code Composer Studio v4 and newer (Does not support Code Composer Studio v3.3)
  • Note: As of 4/28/2010, the CPLD update was issued. Please see XDS100#Q:_How_can_I_update_the_CPLD_on_my_XDS100v2.3F

XDS100v3 Features

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.
  • 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.
  • LED to indicate operation in adapter mode.

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
  • Cores NOT supported: ARM 7, ARM 11, TMS320C24x, TMS320C55x+, TMS320C670x, TMS320C671x, TMS320C672x, TMS320C64x (note that TMS320C64x+ is supported) and other cores not listed as supported.
  • It cannot read the value of the EMU0/1 pins, so long profiling operations that use the EMU0/1 pins to handle counter overflows will not be possible.
  • JTAG Clock (TCLK) frequency other than default JTAG frequency (1Mhz)

XDS100 Installation Instructions

Installation for Code Composer Studio v6

All drivers are installed when XDS100 is selected during installation.

Installation for Code Composer Studio v5

For CCSv5.5 all drivers are installed when XDS100 is selected during installation. For CCSv5.1, 5.2, 5.3 and 5.4 make sure to check for updates in CCS and install the latest TI Emulation update if support for XDS100v3 is needed.

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

Processor FamilyXDS100 Hardware VersionCode Composer Studio Release/VersionNotes
TMS320C28xx                v1, v2, v3                                                          Code Composer Studio v5 page and newer Additional SW patch required for XDS100v3 support
TMS320C54xx v1, v2, v3 - as above - - as above -
TMS320C55xx v1, v2, v3  - as above - - as above -
TMS320C674x v1, v2, v3 - as above - - as above -
TMS320C64x+ v1, v2, v3  - as above - - as above -
TMS320C66x v1, v2, v3  - as above - - as above -
ARM9 v2, v3  - as above - - as above -
ARM Cortex A9 v2, v3 - as above - - as above -
ARM Cortex A8 v2, v3 - as above - - as above -
ARM Cortex M3/M4 v2, v3 - as above - - as above -
ARM Cortex R4 v2, v3  - as above - - as above -

A. Install Code Composer Studio 5.1.x (XDS100v1 and XDS100v2 support is included) as per the table above before  connecting XDS100 USB hardware.

B. Install the EmuPack with XDS100v3 support.

C. Connect the XDS100 hardware

  1. Make sure the Code Composer Studio 5.1.x and EmuPack with XDS100v3 support is installed FIRST before 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 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.

D. Setup Code Composer Studio v5.1.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, XDS100 v2 or XDS100v3)
  3. Select device.

Installation for Code Composer Studio v4.x

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

Processor FamilyXDS100 Hardware VersionCode Composer Studio Release/VersionNotes
TMS320C28xx                v1, v2                                                            Code Composer Studio v4.1 and newer No additional SW required for XDS100 support
TMS320C54xx v1, v2 - as above -
TMS320C55xx v1, v2 - as above -
TMS320C674x v1, v2 - as above -
TMS320C64x+ v1, v2 - as above -
TMS320C66x v1, v2 - Code Composer Studio 4.2.2 and newer -
ARM9 v2 - as above -
ARM Cortex A9 v2 Code Composer Studio v4.2 and newer
ARM Cortex A8 v2 - as above -
ARM Cortex M3 v2 - as above -
ARM Cortex R4 v2 - as above -

A. Install Code Composer Studio 4.x (XDS100 SW support is included) as per the table above before  connecting XDS100 USB hardware.

B. Connect the XDS100 hardware

  1. Make sure the Code Composer Studio 4.x is installed FIRST before 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 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)
  3. Select device.

Installation for Code Composer Studio v3.3 (XDS100v1 Hardware Only)

Code Composer Studio v3.3 Support (XDS100v1 HW only)

Processor FamilyXDS100 Hardware VersionCode Composer Studio Release/VersionNotes
TMS320C28xx v1 CCS v3.3 Platinum Edition (TI part #: TMDSCCSALL-1) Included with CCS Service Release 12 and newer.
TMS320C28xx v1 CCS v3.3 for C2000 Full Version (version #3.3.78.2) (TI part #: TMDSCCS2000-1) XDS100 SW required. Download here.
TMS320C28xx v1 CCS v3.3 for C2000 DSK Version (version #3.3.81.28, 3.3.83.16 or newer) XDS100 SW included in CCS Installation. No additional SW required.
TMS320C674x v1 CCS v3.3 Platinum Edition (TI part #: TMDSCCSALL-1) Included with CCS Service Release 12 and newer.

Note: Code Composer Studio v3.3 ONLY supports XDS100v1 hardware emulator. XDS100v2 hardware is NOT supported on Code Composer Studio v3.3.

Note: Blackhawk has a model D version of XDS100v2 which can be configured to work as a v1 or v2 product. They provide a utility to re-program the device to act as a xds100v1, so the same product can be used with both CCS3.3 and CCS4. The firmware update utilities can be found on their Blackhawk XDS100 Support Page.

A. Install Code Composer Studio and XDS100 Software before connecting XDS100 USB hardware.

  1. Install the Code Composer Studio version, service release and/or XDS100 SW as detailed in the table below prior to connecting the XDS100 SW.

B. Connect the XDS100 hardware

  1. Make sure the XDS100 Software is installed FIRST per the table above before 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 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 v3.3

  1. Select CC Setup icon from the desktop.
  2. From the filters panel, select the platform "xds100usb emulator". This will give you a list of predefined configurations. Select the one appropriate for your device
  3. Save your configuration and exit CC Setup
  4. Start Code Composer Studio
  5. In Code Composer Studio, go Debug-->Connect. Note: "connect to target" may take long time (>5 seconds) for the first time XDS100 USB is connected to target. It is not the case with subsequent "connect" operations.

What are the known issues?

  • XDS100 debuggers suffer a severe performance impact when using Virtual Machines (VMware, Virtualbox, Parallels, etc.) and Linux as a guest OS. Additional details are shown at this page.
  • While loading a large program or program section, the file load status bar may appear frozen when it is not frozen. The status bar is showing section load start and completion.
  • When a second FTDI device is plugged in (ex: FT232RL), and it receives a lower chain number, the XDS100 SW will address it instead of the FT2232 used by the XDS100. Solution: only plug the XDS100 HW into the PC. This has been fixed with Code Composer Studio v4 support for the XDS100v2 ONLY (XDS100v1 still has this issue).
  • XDS100 SW Driver does not install properly under Windows Vista 64 bit using CCSv3.3
  • If "Option" under CCSv3.3 “connect to target at CCS startup” is enabled and c674x target board is connected, then the following error is reported when you try to "Disconnect" for the 1st time. It works fine on 2nd attempt to disconnect. Note, this has been fixed for CCS v4.
Error: Error 0xA0002020/-150 Error during: Execution, Control, This error was generated by TI's USCIF driver. SC_ERR_POD_FAIL <-150> This utility failed to operate the adapter for a custom emulator. The adapter returned an error for unknown reasons.
  • When selecting OMAPL137 configuration in CCS 4.0.2, the GEL files cause the connection to be hung. Remove the GEL file from the target configuration. This has been fixed in CCSv5.2 and newer.
  • ETB for OMAPL137/8 is not working. Error of "ETB definitions cannot be loaded. Device not supported." is reported. ETB11 for OMAPL137/138 is not supported at this time. This has been fixed in CCSv5 and newer.
  • When installating XDS100v2 patch via update manager, CCS says that the feature is not digitally signed. Continue installation. This has been fixed in CCSv5 releases.
  • Target power loss detection is not working in CCS v4.1/v4.1.x. This has been fixed in CCS v4.2.
  • Adaptive clocking use with OMAPL138/ARM9 cores connection reliability varies by card. This results in connection errors. A fix has been identified by upgrading the CPLD on XDS100v2 designs. Please see XDS100#Q:_How_can_I_update_the_CPLD_on_my_XDS100v2.3F

Troubleshooting

  • Check whether the installation process was followed.
  • Please check the FAQ questions below. (Troubleshooting FAQ)
  • Please check the section regarding Troubleshooting CCS.
  • Check your Windows System Devices. When properly installed, the XDS100 should look like the below image. If the XDS100 does not show up in the Windows device manager or shows with an error, then it is likely that the XDS100 was not programmed properly (contact manufacturer), there is a conflict with another FTDI based USB device (see FAQ below for details) or the drivers became corrupt (check the reinstall section above the screenshots)
    • You can run the utility <xds100serial.exe> to find out which VID/PID are programmed in the device. This utility is typically located at the directory
  • Check USB cable or change the USB port the emulator is connected
  • Power cycle your target
  • You may want to check the VID/PID EEPROM was programed correctly
  • Sometimes the use of different drivers such as libFTDI (used by OpenOCD, for example) or a simple corruption on other Windows .inf files may cause an improper initialization of the XDS100 device drivers. Please check this forum thread for details.

To reinstall the Windows device drivers:

  • Right-click on node XDS100 Channel A
  • Select Update Driver SoftwareBrowse my computer for driver software
  • Select Let me pick from a list of device drivers on my computer. If the drivers are already installed, the XDS100 Class Debug Port drivers will show. Select this one. Otherwise, repeat but skip this step.
  • Click on Browse and select the directory C:\ti\ccsv7\ccs_base\emulation\windows\xds100_drivers
  • Repeat for XDS100 Channel B

That should get you the same driver as installed by CCS.

If Windows refuses to update the driver, they need to be fully removed.

  • Right-click on node XDS100 Channel A
  • Select Uninstall...
  • Check the box Delete the driver software for this device and click OK
  • Repeat for XDS100 Channel B
  • Do the procedure above to reinstall the drivers



Roadmap

  • SW Update for improved performance.
  • Lower cost design.

Where to get an XDS100 / Where to buy an XDS100

XDS100v3

  • Spectrum Digital, Inc., offers an XDS100v3 USB CJTAG/JTAG Emulator here
  • Olimex LTD, manufactures and sells a low-cost XDS100v3 here
  • 00ic.com offers an XDS100v3 in china mainland with black plastic shell here
  • Embest offers one here

XDS100v2

  • Ashling's Opella-XDS100v2 is now available. Check it out here and buy here
  • Blackhawk has one available (and our latest model supports both CCS v3.3 and v4., so no more deciding which model to buy)
  • Olimex manufactures and sells an XDS100v2 debugger here
  • Embest has one here
  • Spectrum Digital, Inc., offers an XDS100v2 USB JTAG Emulator here
  • TI Estore has a lifetime buy of the 20 pin compact TI version available.

XDS100v1

How to make an XDS100 / How to build an XDS100 hardware emulator

  • You can make your own XDS100 by using the schematic and programming instructions below.

XDS100v3 (only recommended for cJTAG based devices)

Q: Where can I get the design / schematic / BOM for the XDS100v3?

  • A: It is available from here (registration required).
  • The design files (schematic, gerbers, etc.) are provided. Scrambled FPGA VHDL is also included.
  • Please read the included readme for details.

Q: What should the USB device's UID (VID/PID) be?

  • A: The EEPROM needs to be programmed for a VID=0403 PID=A6D1. The device name string should be, “Texas Instruments Inc.XDS100 Ver 3.0”.
  • A: FTDI has a utility called MProg. See here. To program the FTDI chip you will need a MPROG template file that can be downloaded from this link.

Q: I want to put an XDS100v3 on my EVM / DSK / card. Can I do this?

  • A: Yes, but please make sure to re-use the entire XDS100 design as-is to ensure compatibility with the existing software!

XDS100v2 (Recommended)

Q: Where can I get the design / schematic / BOM for the XDS100v2?

  • A: It is available from here (registration required).
  • The design files (schematic, gerbers, etc.) are drawn in the program KiCAD. PDF schematic is included. Bill of Materials (BOM) is included. MPROG script file is included. CPLD VHD and JED sources are included.
  • Please read the included readme for details.
  • Note as of 4/28/2010, the design package was updated with new CPLD source code. This is to fix the issues related to Adaptive Clocking on ARM9.

Q: What should the USB device's UID (VID/PID) be?

  • A: The EEPROM needs to be programmed for a VID=0403 PID=A6D0. The device name string should be, “Texas Instruments Inc.XDS100 Ver 2.0”.
  • A: FTDI has a utility called MProg. See here. To program the FTDI chip you will need a MPROG template file that can be downloaded from this link.

Q: XDS100-based C5505 and C5515 EzDSP USB Stick does connect when using "Target Connect"

I get: "Error connecting to the target: Error 0x80000240/-600 Fatal Error during: Initialization, OCS"

  • 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:

TI XDS100 Channel B -> Uninstall then TI XDS100 Channel A -> Uninstall Then it re-installed itself when re-connecting the XDS100-based USB stick and "Target Connect" worked afetr re-starting CCSv4

Q: I want to put an XDS100v2 on my EVM / DSK / card. Can I do this?

  • A: Yes, but please make sure to re-use the entire XDS100 design as-is to ensure compatibility with the software! Removing the CPLD implementing with discrete logic will result in a design that is just as complex and expensive as using the CPLD.

Q: Can I use port B as a UART?

  • 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. Generally, a serial port on BCBUS should connect the CPLD as follows: BCBUS1 -> CPLD TCK, BCBUS2 -> CPLD TDI, BCBUS5 -> CPLD TDO, BCBUS6 -> CPLD TMS.
  • Please note that using UART mode simultaneously with Code Composer Studio v4 has NOT been tested on the XDS100v2 design and is not officially supported. Experience with C2000 ControlCards which implement this functionality indicate the FTDI driver can handle such an interaction. *The C2000 control card does implement a serial port simultaneous with JTAG, but it is done with an XDS100v1 design. There is a thread on the forum at [1]. 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.

Q: I see both 14 pin and 20 pin compact TI headers. Do I need both?

  • A: Both are in the reference schematic for testing Code Composer Studio support. In the TI prototypes, we populate just one of the 2 headers. This allows use to test the extended capability available with the 20 pin connection. Please use the header that is needed for your target card.

XDS100v1 (Legacy)

Q: Where can I get the schematic for the XDS100v1?

  • A: It is available from here (registration required).
  • A: The C2000 control card schematics implement an XDS100 design optimized for C28x processors. The design is available as part of their baseline SW packages. These can be downloaded here

Q: What should the USB device's UID (VID/PID) be?

  • A: The EEPROM needs to be programmed for a VID=0403 PID=A6D0. The device name string should be, “Texas Instruments Inc.XDS100 Ver 1.0”.
  • A: FTDI has a utility called MProg. See here. To program the FTDI chip you will need a MPROG template file that can be downloaded from this link.
    • For 28x development cards, you may want to see this [| post]

Frequently Asked Questions (FAQ)

General FAQ

Q: Where can I find out more about Emulators which are compatible with TI devices?

  • A: A general overview of TI emulation capabilities is here. For additional performance and capabilities, you may wish to review the XDS510 and XDS560 product lines which support TI devices.

Q: I would like to purchase a faster emulator, which one is recommended?

  • A: TMS320C28x: The Spectrum Digital C2000 XDS510LC JTAG emulator is available, details may be found here. The Blackhawk C2000 USB controller (TI part #TMDSEMU2000U) is available from TI here.
  • A: TMS320C674x: The Blackhawk XDS560 (TI part #TMDSEMU560U  for USB and TI part #TMDSEMU560PCI for PCI) are available from TI here. The Spectrum Digital XDS510 (TI part #TMDSEMU510U for USB) is available from TI here.

Q: On the c28x, C674x, and C64x+ processor, does the XDS100 support Real-Time Mode?

Q: How to maximize performance of XDS100 under CCS?

A: A couple of things can be done to improve performance under CCS. Generally, the goal is to minimze the amount of information transferred for every action

  • Make the disassembly window smaller or close the disassembly window. Stepping and general performance are better in the "C" language environment if the disassembly window is closed.
  • Minimize the number of registers shown.
  • Minimize the number of watch windows/variable windows.
  • Turn off mixed C/disassembly mode.
  • Make sure you are plugged into a High Speed USB2.0 port (XDS100v2)
  • Single step debugging is rather slow, therefore a better performance is obtained by running straight to specific points in your code by setting breakpoints in these locations.

Q: Does the XDS100 support debugging the C672x processor?

Q: Does the XDS100 support debugging the C24x processor?

Q: Does DSP/BIOS Real Time Analysis with RTDX work?

  • Q: When using DSP/BIOS and the Real Time Analysis setup for RTDX, I get the cpu graph and real time logs updating. Does this mean RTDX is working/supported on the XDS100?
  • A: RTDX is not supported on the XDS100. Please see the seciton What features does the XDS100 NOT support

Q: Can I use Advanced Event Triggering with XDS100?

Q: Can I plug more than one XDS100 (multiple XDS100) into a PC?

  • With CCS v4.1 (with the XDS100v2 SW) and above you can plug more than one XDS100 on a single PC. This is not supported with CCSv3.3.
  • Each XDS100 must have a unique serial number. Run xds100serial.exe installed under CCSv4.1 "<install_dir>/ccsv4/common/uscif/utility" to get the serial number of each connected XDS100 emulator. Create Target Configuration for 2 emulators, Under “connection properties”, change “emulator selection” to “select by serial number” option. Enter the corresponding serial number for each emulator. Save and launch debugger.
  • With CCSv5, the xds100serial.exe utility is located in the folder "<install_dir>/ccsv5/ccs_base/common/uscif"
  • With older versions of CCS (ex: CCS v3.3), there is a known issue (see above) which prevents the CCS XDS100 driver from seeing more than one XDS100 in a system. If more than one is in a system, only the first one is recognized.
  • xds100serial.exe can detect both XDS100v1 and XDS100v2 emulators.

Q: Can I use the XDS100 with Stellaris Cortex M3 devices?

Q: Can I use the XDS100v2 as JTAG simultaneously with the second port being a serial port (UART)?

Q: How can I use the XDS100v2's second port as a serial port (UART)?

  • A: Ensure that there is a physical connection between the FTDI Port B TX and RX pins and your target serial device and then follow these steps:
  1. Click Start, Right click on My Computer, and select Properties
  2. Navigate to the Hardware tab of the System Properties dialog box and select Device Manager
  3. In the list of devices, expand the group titled Universal Serial Bus controllers and look for a device named TI XDS100 Channel B
  4. Right click on this device and select Properties
  5. On the Advanced tab of this dialog box, ensure that the box labeled "Load VCP" (virtual COM port) is checked. Click OK when you are done.
  6. Unplug and replug the XDS100v2
  7. After the XDS100V2 has been re-connected, look for a group called Ports (COM & LPT) in Device Manager. Expand this group and look for an entry labaled USB Serial Port (COMXXX).
  8. The COM number associated with this port is the one you want to use in Hyperterminal, PuTTy, or your favorite terminal application.

Q: How can I turn on adaptive clocking?


  • You can change the timeouts from the target as well. This is helpful if you get many timeout messages.

Q: My XDS100v2 does not work reliabily with the OMAPL138 / DM365 / ARM926 core

  • A: This can be caused by a variety of issues such as where the PLL is programmed to the use of Adaptive Clocking emulator. Usually, it is seen as a problem around the PLL setup. This is because the core PLL clock is changing. Example error message:
ARM9: GEL Output: Setup PLL0... ARM9: Trouble Writing Memory Block at 0x1c40900 on Page 0 of Length 0x4: 0x00000004/-2030 @ marker 1026 Error during: Register, Access to an unknown or invalid register was attempted. ARM9: GEL: Error while executing OnTargetConnect(): target access failed.

A couple of things to try:

  1. Setup the PLL by executing code (ex: UBoot, etc.) instead of using the GEL file. (preferred)
  2. Turn on adaptive clocking XDS100#Q:_How_can_I_turn_on_adaptive_clocking.3F and setup the timeouts to very slow. In this mode, it is still better to "run" the code and not "step" it.
  3. Make sure you have the latest CPLD version. To update the XDS100v2 CPLD, please see XDS100#Q:_How_can_I_update_the_CPLD_on_my_XDS100v2.3F

Q: Can I use the XDS100 with OMAP-L138/C6748 EVM board?

Q: Does XDS100 work with Window 7 64 bit?

  • The current driver in XDS100v2 works with Windows 7 (64 bit).

Q: Can I use the XDS100 without CCS? Is there an API to access it's functions?

  • Not at this time.
  • We have some requests for an API to read/write targets, run/halt/step, load memory and handle STDIO. If you have requests, please post them in the support forum.
  • If you need API for accessing CCS, without a GUI, you may want to consider Debug Server Scripting

Q: Can I use the XDS100v1/v2 with CC13xx/CC26xx SimpleLink ULP devices?

  • A: No, only XDS100v3 supports the CC13xx/CC26xx device family. See CC13xx CC26xx Tools Overview for more details on debugger support for these devices.

Installation FAQ

Q: Where are the drivers for the hardware? Windows is asking for the drivers.

Q: What operating systems are supported?

  • A: You have an older version of the XDS100 SW/CCS. The F28x Piccolo device configuration files are included in the latest versions of the SW. Please see the installation notes above.

Q: What does the windows messages look like in Windows XP upon successful installation?

  • A: See here. Note that after the first installation, there are no subsequent messages in Windows XP from the USB driver.

Q: I am using CCSv3.3 today. Can I get a driver to support XDS100 for my processor?

A: All new XDS100 development is being done on Code Composer Studio v4. Existing processors supported by XDS100 in CCSv3.3 will continue to be supported, but newer processors will not be added.

Q: Can I use Code Composer Studio v4 with XDS100?

A: There is a free license for Code Composer Studio v4 when used with XDS100. Code Composer Studio v4 can be downloaded from the Code Composer Studio v4 page. When you install CCS, you need to select the correct license. See below on how to select the correct license. This license is designed to be use with XDS100 only, and not XDS510 or XDS560 emulators. Please see Activating CCS#Generate_and_Install_a_License_File for details.

Troubleshooting FAQ

Q: Why is the download frozen?

  • A: While loading a large program or program section, the file load status bar may appear frozen when it is not frozen. The status bar is showing section load start and completion.

Q: Windows is recognizing the XDS100 as "Dual RS232 USB Serial Bridge" instead of the TI XDS100 JTAG emulator.

  • Q: I have a C2000 Experimenter kits/Piccolo USB Stick that includes the onboard USB JTAG emulation, but the onboard USB JTAG emulation is being recognized by Windows as "Dual RS232 USB Serial Bridge" instead of the TI XDS100 JTAG emulator.
  • A: See this post on the forums.

Q: I used the FTClean utility on my computer and now I can't connect to the XDS100! What can I do?

  • A: Running FTClean will remove the windows FTDI drivers for the XDS100. The TI XDS100 FTDI drivers were installed with the CCS installation or service patch. The XDS100 drivers are signed for the VID/PID combination. To recover, please re-install the CCS version/path you were last using before running FTClean which included the TI signed XDS100 drivers.

Q: My XDS560 stopped working when I installed the XDS100...

  • A: Note that the XDS100 software is included and installed with CCS v3.3 SR12 or newer and/or CCSv4. For CCS v3.3 and SR12, it is recommended that users install the new Blackhawk XDS560 driver from Blackhawk website. There is no need to install a new Blackhawk driver with CCS v4.

Q: My JTAG is not working with CCS...

A: Please check: Debugging JTAG Connectivity Problems

Q: I see in my Windows Device Manager an error for a TI XDS560 emulator.

A: The XDS100 will not be affected by this. Please see XDS560#Q:_Why_does_my_Windows_Device_Manager_show_a_warning_for_the_TI_XDS560_PCI_Emulator.3F

Q: I see a Windows device manager problem with Texas Instruments XDS560 PCI JTAG emualtor. Does this affect the XDS100?

A: No. This error is caused by the Texas Instruments XDS560 PCI JTAG emulator not being installed. This service may be used by other XDS560 emulators. A proper setup in Windows device manager will look like the image in XDS100#Troubleshooting.

Q: Can I use an XDS100v2 hardware with a older version of Code Composer Studio? (Ex: CCS v3.3)

  • A: No. The XDS100v2 will not work with older versions of Code Composer Studio that do not support the XDS100v2. Code Composer Studio v3.3 is not supported by the XDS100v2 hardware. For Code Composer Studio v4 users, please upgrade to the latest software versions as listed in the software installation section. If you use a XDS100v2 hardware unit with a version of CCS which does not support it, the software will just see a zero-bit scan chain. If you use DBGJTAG to test the JTAG scan path, it will look like the below, with a zero-bit scan path on both IR and DR.
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. This utility has successfully reset the controller. -----[Print the reset-command hardware log-file]----------------------------- The scan-path will be reset by toggling the JTAG TRST signal. The controller is the FTDI FT2232 with USB interface. The link from controller to target is direct (without cable). The software is configured for FTDI FT2232 features. 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). The controller has an insertion length of '0' (0x00000000). The local memory has a word capacity of '1048576' (0x00100000). -----[Perform the standard path-length test on the JTAG IR and DR]----------- This path-length test uses blocks of 512 32-bit words. The test for the JTAG IR instruction path-length succeeded. The JTAG IR instruction path-length is 0 bits. The test for the JTAG DR bypass path-length succeeded. The JTAG DR bypass path-length is 0 bits.

Q: On connecting the USB, I get the error message "The file FTDIBUS.SYS on FTDI USB Drivers Disk is needed"

  • A: The USB drivers are likely missing. Please see the installation instructions above to install the software before trying to connect the XDS100.
  • A: It may also be that the FTDI EEPROM is not properly progrmmed. Please contact your XDS100 vendor to have the problem corrected. You could also see the section on Xds100#How_to_make_an_XDS100 to program the EEPROM.

Q: I got a -150 SC_ERR_POD_FAIL error, what does this mean?

  • For an XDS100, this means that Code Composer Studio is having a problem talking to the XDS100. The problem is with the communication between the adapter and the FTDI chip. Either the FTDI driver has returned an error, or the chip failed to return the expected number of bytes to Code Composer Studio. In practice, this has usually been found to be a problem with the FTDI drivers. Either the wrong drivers were installed, or there is a conflict with FTDI drivers used for another device, or a software process that hasn’t completely terminated and is holding 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.

Q: I got an "Error connecting to the target: Error 0x80000240/-151 Fatal Error during: Initialization, OCS" when trying to connect to the target in Code Composer Studio v4

Q: I was following Debugging JTAG Connectivity Problems and I a -151 SC_ERR_POD_OPEN error with Dbgjtag.

Q: What happens when I plug a XDS100v2 in to my card but select XDS100v1 or XDS100 as the emulator?

  • A: The output from a path length test will look like it is passing, with a zero - bit path length. This is because the XDS100v2 has a loopback mode which is used in testing. When the XDS100v1 software is used, it invokes this loopback mode.
-----[Perform the standard path-length test on the JTAG IR and DR]----------- This path-length test uses blocks of 512 32-bit words. The test for the JTAG IR instruction path-length succeeded. The JTAG IR instruction path-length is 0 bits. The test for the JTAG DR bypass path-length succeeded. The JTAG DR bypass path-length is 0 bits.
  • From Code Composer Studio, the error may look like an unrecoverable emulation error:
Error connecting to the target: Error 0x00001200/-1135 Error during: OCS, Target, Unrecoverable emulation error

Q: What happens when I plug a XDS100v1 into a card but select an XDS100v2 in CCS?

  • A: The output from path length test will vary with the target device. This is because the XDS100v2 uses the pins on the communications chip different from how it was used on the XDS100v1. On some devices such as c28x, it may cause the device to enter an unexpected bootmode. For the example with a 28x core, a 3-bit path length was seen vs a 38-bit path lengh (expected). This was because a bootmode was selected.

Q: I just upgraded to CCS 4.1.2 and now my XDS100 is not working. It was working before!

  • A: Check your VID/PID value. If it does not match, you need to contact your manufacturer, or get the VID/PID EEPROM programmed properly.
  • A: With CCS 4.1.2 and newer, a bug was fixed so that the XDS100 software could properly connect only to a XDS100 VID/PID values. In older versions of CCS, the XDS100 software would connect to any VID/PID value causing incompatibilties with non-XDS100 FTDI based devices plugged into the same PC.

Q: I was using CCS v3.3 SR12 before and upgraded to CCS 4.1.2 (or newer) and now my XDS100 is not working. It was working before!

Hardware FAQ

Q: Where can I find out about pinout of JTAG connectors?

Q: What if I need electrical isolation?

  • A: If you are working with a target which has high voltages, you may want to use an isolation adapter.
  • There is an isolation adapter available here and a usb isolation adapter available in china mainland here

Q: What device voltages are supported by the XDS100v1?

  • A: The XDS100v1 reference design supports 1.8V and 3.3V targets. The SN74CBT3125 (U3) and SN74LVC2T45 (U5) perform the voltage buffering. The MCP6041 (IC5) and TLC393 (IC1B) are used for voltage sensing. The 74HC74(IC3A) and TLC393 (IC1A) form the power detect circuit by reaching the TVO pin.

Q: I work with high voltages, where can I get an isolation adapter?

  • A: TI offers an isolation adapter (TI part #: TMDSADP1414-ISO) here.

Q: Can I change the serial number on my XDS100v2?

  • A: Yes, using the FTDI MProg utility and one of the configurations in Media:Xds100v2serial.zip so you can change the serial number of an XDS100v2 product if desired.
  • NOTE: Support for MProg is being deprecated in favor of FT_Prog (also available on the same site). If you are having issue with MProg, try FT_Prog
  • If you plan to use 1 or more XDS100v2 emulators in CCSv4 simultaneously then each XDS100v2 must have a unique serial number.
  • For ease of use Spectrum Digital generally programs the XDS100v2 with a fixed serial number as this is the most common use case and is consistent with other low cost Spectrum Digital products.
Steps: 1) Launch MProg. 2) Load the desired configuration. For Fixed Serial Number: File->Open SDXDS100v2_FIXED.EPT For Autogenerated Serial Number: File->Open SDXDS100v2.EPT 3) Enable programming of pre-programmed devices if needed. File->Edit and uncheck "Only Program Blank Devices" 4) Program the ROM Device->Program

Q: What frequencies are supported by XDS100v2? Can I change it?

  • A: The default frequency is 1Mhz. Other frequencies can be selected, but they are not supported.

Q: On XDS100v1 design, what does the OE signal do? (pin 12 of FTDI)

  • A: On the XDS100v1 design, this OE signal on pin 12 of the FTDI chip comes from the ICA3A device (74HC74, flip flop). The ICA3A/IC1A section of the circuit samples the TVD signal to detect whether there is target power. This signal is read by the debugger via the GPIO on the FTDI. This signal has an opposite signal /OE which goes to U3. U3 provides a buffer which performs the voltage translation.

Q: How can I check if the VID/PID for the EEPROM are programmed correctly?

  • 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.

IMPORTANT! This is not applicable for BeagleBone Rev A5 and greater (which uses a XDS100). Check this FAQ entry.

  • Expected XDS100 VID/PID should be as described in the sections how to make an XDS100
  • A: If your hardware VID/PID does not match what is described in How to make an XDS100, please contact your hardware manufacturer.

Note:It is possible to reprogram the EEPROM using MPROG or FT_Prog and the .ept file. The .ept file depends on the type of device you have. If you have a FT2232C device download the following FT2232C EPT file. If you have a FT2232H device download the following FT2232H EPT file. Refer to the instructions in the How to make an XDS100 section

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

Q: How do I reprogram the VID/PID EEPROM if it has not been programmed correctly?

  • A If your VID/PID EEPROM has been programmed incorrectly, or not programmed at all, you can reprogram it with these simple steps
  1. Download and Install MPROG from FDTI. You can get MPROG 3.5 from here
  2. Download and extract the ept file from here
  3. Connect your XDS100 to the PC via the USB Cable
  4. Execute MProg.exe from within the directory structure where you installed MPROG. You should see a screen like the one pictured below.
  5. Select File->Open, and select the XDS100_wUART.ept file you extracted
  6. Select Device->Scan to verify that it will talk to your XDS100
  7. Select Device->Erase to erase the existing programming
  8. Select Device->Program to program the correct settings
  9. Close MPROG

You should now be able to follow the directions Here to verify that it has been programmed correctly. If it has, you should now be able to use your XDS100 with CCS.

Q: Does the XDS100v2 latch data on the rising or falling edge?

Q: How do I tell what the CPLD version is on my XDS100v2?

  • A: Please contact your manufacturer. They may be able to tell from the manufacturing ID. There is no ID in the cpld code, so it cannot be determined by software.

Q: How can I update the CPLD on my XDS100v2?

  • A: If your manufacturer built the XDS100v2 according to the reference design, you will be able to upgrade the XDS100v2 CPLD via SW. If your manufacturer did not follow the XDS100v2 reference design, please contact your manufacturer directly.
  • As of 4/28/2010, an enhancment to improve reliability with devices which require Adaptive Clocking (ex: 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
  2. Fixed definitions of certain signals from "inout" to "output" (EMUs and TMS). T_SRST remains "inout".

This document contains General JTAG emulator information that may not be found in the product Technical Reference or quick start guide. Also included is troubleshooting information that can be used to help troubleshoot questionable JTAG Emulator connection.

Initial emulator specifications and emulator installation details can be found in the emulator 'Technical Reference', 'Quick Start Guide', and

1. Preliminary Checks

2. SDConfig Utility

3. Emulator Connection Troubleshooting

4. Emulator Specific

5. Code Composer Studio Configuration and Spectrum Digital Emulators

6. Emulator Memory Summary

Here is a list of Operating systems supported by our JTAG emulators and Code Composer Studio v3.x:

    *-USB drivers for Vista 32 and 64 bit versions are included in the standard emulation installation (CCS 3.3 and later). After installation, the drivers can be found in a directory that looks like:
    • 32 bit: C:\CCStudio_v3.3\specdig\xds510usb
    • 64 bit: C:\CCStudio_v3.3\specdig\xds510usb_win64
  • Windows 7, 32 and 64* (requires CCS v4.1 or later)

SDconfig Utility

The SDConfig utility is installed with the standard JTAG Emulation driver installation. It can be launched from the 'SDConfig' icon on the Desktop or by double-clicking the 'sdconfig.exe' file in the installation path of C:\

SDConfig does not support the XDS560R USB JTAG Emulator at this time.


2.1 SDConfig Test Suggestions

2.1.1 SDConfig Host Computer Port Test

SDConfig can test to determine if the Host Computer port (Parallel POrt or USB) is available for use by the Spectrum Digital JTAG emulator. Highlight the port address (port list is in the column in the left panel) you wish to test. The test can be run by clicking "Configuration", then "Ports Avialable", then "Printer, USB". The SDConfig output window will tell you if a suitable port has been found.


2.1.2 SDConfig Emulator Connection Verification

SDConfig can test the connection between the Host Computer and Emultor. Connect the emulator to the computer and power the emulator (if external power is required). Highlight the port address (port list is in the column in the left panel) you wish to test. Now click "Configuration", then "Verify". The SDConfig output window will tell you if a Spectrum Digital JTAG Emulator has been found.

If the Configuration-->Verify fails, then it may be necessary that the emultion drivers be re-installed. Alternatively, this may be a result of faulty emulator hardware. Try connecting another emulator (if one is available) to the computer and test the Verify again. If the new emulator is found by SDConfig, then the questionable one may need to be returned for repair.


2.1.3 SDConfig Emulator/Target Connection test

The JTAG connection between the emulator and Target DSP can be tested using the SDConfig "Emulator Test". Highlight the port address (port list is in the column in the left panel) you wish to test. Now click "Emulator", then "Test. The SDConfig output window will tell you if the Spectrum Digital JTAG Emulator has successfully connected to a valid JTAG scan chain.


If the Emulator Test fails, this may be a result of faulty emulator hardware or possibly faulty target JTAG connection. Try connecting another emulator (if one is available) to the same target and run the test again. If the new Emulator Test passes with the new emulator connected, then the questionable one may need to be returned for repair. Alternatively, try connecting a different Target board to the emulator. If the Test passes when connected to the new target, then the original target board may need repair.

2.1.4 SDConfig Scan Chain Connection Diagnostics

Once you have verified the PC to emulator connection you can perform advanced scan chain diagnostics. These diagnostics can aid in finding scan chain problems related to integrity, signal quality and other failures that would prevent CCS or other debug products from starting and running reliably. To run diagnostics, connect the emulator to the computer and target, power the emulator and target, then launch SDConfig. Select the port address that is appropriate for the emulator being used, then click Emulator->Diagnostics. A new window will appear as follows:


  • Scan Verify: Uses an incrementing scan pattern. This pattern will have varying numbers of ones and zeroes.
  • Scan Pattern: User selectable pattern. Best selection for probing the JTAG TDI/TDO signals.
  • Stop Error Count: Determines the number of failures that can accumulate before the test stops. If set to zero then all errors are ignored. Set to zero when probing with scope.
  • Test Loop: Number of iterations to run the test. If set to zero then loop until user selects the stop button. Set to zero when probing with scope.


  • Emulation Connection Troubleshooting

    The Emulator must have valid communication with the Host Computer and have valid connection with the target processor board. It is not always easy to determine where the communication failure has occured. Is the emulator communicating with the computer? Is the emulator communicating with the target board? This section should help pinpoint the cause of the failing communication.

    3.1 Connection Between Emulator and Host Computer

    3.1.1 Verify the USB drivers are properly installed

    USB communication to the host computer is used by many of Spectrum Digital's JTAG Emulators, EVMs, DSKs, and eZdsp boards. The USB drivers must be correctly installed and registered in Windows. This installation is done during the initial setup of the USB device. The USB installation may be verified as follows:

    • Plug in the Emulator (DSK, EVM, or eZdsp) to the USB port of the computer.
    • Go to the Windows 'Control Panel' and click 'System'.
    • Click the 'Hardware' Tab.
    • Click 'Device Manager'
    An entry named "SD USB Based Debug Tools" should appear in the root. Expand the entry and the name of the device should appear. For example: "Spectrum Digital XDS510 USB". If the device entery does not appear or does not appear correctly, then the USB drivers may need to be re-installed or there is possibly a hardware problem with the emulator. Try installing the emulator on a second computer. If the problem persists, then the unit may need to be returned for repair.

    3.1.2 Verify the emulator connection to the Host computer

    • Check the cable (USB or Parallel port) connection to the computer. The connection should be secure.
    • If using a Parallel port emulator, verify +5V is applied to power the emulator. This may be done using an external +5V power supply or through the PD pin on the target board's JTAG connection.
    • If using a USB hub for a USB emulator, make sure the hub is a powered hub. If not, then the proper power may not be supplied to the USB emulator.
    • Use the SDConfig "Configuration Verify" to verify the connection. See Section 2 of this document.

    3.1.3 Parallel Port Adapters

    Spectrum Digital parallel port drivers (XDS510PP PLUS JTAG Emulator and eZdsp boards) require a port using standard LPT1 port addresses such as 0x378, 0x278, and 0x3bc. If the computer does not have a parallel port, the use of a parallel port adapter may be considered, however the adapter MUST allow being mapped to the standard LPT1 port addresses mentioned previously.

    We have found only one adapter that will allow the LPT1 addresses. It is a PCMCIA to Parallel Port adapter. The manufacturer is Quatech and the part number is SPP-100.


    3.2 Connection between Emulator and Target

    3.2.1 Emulator JTAG Scan Test

    The SDConfig JTAG Scan Test is the quickest way to test the connection between emulator and target. See Section 2 above about the SDConfig for more details.

    3.2.2 Code Composer Studio Failure to lauch or Connect

    Code Composer Studio does not automatically "Connect" once the application is launched. After launching CCS, the connection must be made. Click "Debug" then "Connect".

    If the connection still cannot be made, or errors appear, there might be a Configuration problem in the CCS Configuration utility. Close the CCS and launch back into the CCS Setup Tool. Verify the proper connection is being used, the JTAG Scan chain is defined poperly, and a suitable GEL file is being used. Spectrum Digital JTAG emulator installations include many pre-built configurations using Spectrum Digital Emulators and targets. The CCS Setup utility uses 3 drop-down menus to narrow the search for a suitable pre-built configuration. Make sure the correct Emulator Selection (Platform) is selected for a SD Emulator.

  • XDS510PP, XDS510PP PLUS, or SPI515 JTAG emulators ---> "PP emulator"
  • SPI525 PCI JTAG Emulator ---> "SPI 525 emulator"
  • XDS510USB, XDS510SUB PLUS or C2000 XDS510LC USB JTAG Emulators ---> "XDS510SUB Emulator"
  • ** PLEASE NOTE: DO NOT SELECT 'XDS510 EMULATOR' IF YOU ARE USING A SPECTRUM DIGITAL EMULATOR. ** 'XDS510 Emulator' corresponds to the Texas Instruments XDS510ISA JTAG Emulator, not a Spectrum Digital emulator.
  • 3.2.3 Potential Hardware Causes for Failure

    Faulty hardware is also a potential cause for failure with the CCS connection. The SDConfig utility can be used as an initial test to verify if the hardware is a potential cause of the failure. See Section 2 above regarding the "Emulator Test" for more detail.

    The emulator hardware may have become faulty. The cable may be bad or possibly components on the emulator board are failing. If the emulator hardware is suspected to be faulty, it may be returned to Spectrum Digital for repair. The repair process is handled on our website at www.spectrumdigital.com, by clicking on "Return Merchandise Authorization".

    The Target board JTAG connection may be suspect as well. Proper JTAG connection and signal integrity is very important to allow communication with a JTAG emulator. Custom JTAG connections that do not comply to the standare JTAG header pinouts are extremely suspect. A noisy system, noisy environment, poor signal integrity, etc. will create problems with the emulation connection.

    • It is recommended to use the standard Texas Instruments JTAG header (14-pin, 20-pin, 60-pin) design and pin out. Any deviation from the standard may pose potential communication problems
    • The JTAG signal trace length on the target board, between the JTAG header and DSP must be less than 2 inches. Otherwise the signals must be buffered.
    • The 'EMU' Must be pulled high to the target voltage to allow for emulator debugging.

    Emulator Specific

    4.1 XDS510USB JTAG Emulator

    Here is a list of XDS510USB JTAG emulator specific Notes

  • The JTAG Tclock generated by the XDS510USB is fixed at 12MHz. This clock value may be divided to slow the clock if needed. This might help improve JTAG connection with marginal systems. The clock value divider can be changed in the Driver Options file "SDOpts.cfg". SDopts.cfg is locate in the C:\Windows\system32 directory of the computer. Open the SDOpts.cfg in a text editor and change the value of the 'EmuTckDiv' option to geve the necessary TCK value. Below is a screenshot example what the SDopts.cfg change looks like:

  • Up to 4 XDS510USB JTAG emulators can be used simultaneously on one computer. Details how this can be acheive can be found in the Tech Note: Using Multiple XDS510USB Emulators
  • 4.2 XDS510USB PLUS JTAG Emulator

    Here is a list of XDS510USB PLUS JTAG emulator specific Notes.

  • The XDS510USB PLUS is supported by the SDConfig utility. However, additional support for the XDS510USB PLUS Features is available using the "SDConfigEX" utility. The SDConfigEX utility is included with the emulation driver installation. It can be accessed by launching the 'SDConfiEX.exe'executable. The executable may be found in the installation directory that looks similar to "C:\CCStudio_v3.3\specdig\sdconfigex". SDConfigEX offers the same support for the XDS510USB PLUS as the SDConfig does, but with added options. Details can be found in the SDConfigEX PDF documentation found in the same path where the executable is located (C:\CCStudio_v3.3\specdig\sdconfigex).
  • Up to 4 XDS510USB PLUS JTAG emulators can be used simultaneously on one computer. Details how this can be acheive can be found in the Tech Note: Using Multiple XDS510USB Emulators
  • 4.3 C2000 Series XDS510LC USB JTAG Emulator

    Here is a list of C2000 XDS510LC USB JTAG emulator specific Notes.

  • The C2000 Series XDS510LC JTAG Emulator supports only the C2000 family of DSCs from Texas Instruments. Development support for other Texas Instruments DSPs and TMS470 parts will require one of our other JTAG Emulators.
  • Only 1 C2000 XDS510LC can be used on a single computer at a time.
  • 4.4 XDS510PP PLUS JTAG Emulator

    Here is a list of XDS510PP PLUS JTAG emulator specific notes.

  • The Parallel port cable should be connected directly to the host computer's parallel port using the parallel port cable included with the XDS510PP PLUS package. Docking Stations, Parallel port Switch boxes, Extender cables, security dongles, etc., can cause communication problems between the emulator and computer and should be avoided.
  • The parallel port mode settings in the computer's BIOS should be Bi-Directional, SPP-8, ECP, or EPP. Modes of normal, automatic, or SPP-4 will not allow communication with the XDS510PP PLUS.
  • USB or PCI to parallel ports generally will NOT work with our parellel port emulators. Please refer to 3.1.3 Parallel Port Adapters above for more details
  • 4.5 XDS560R USB JTAG Emulator

    Here is a list of XDS560R USB JTAG emulator specific notes.

  • The XDS560R has a variable JTAG Tclock. The user can adjust the clock value to help improve JTAG communication. Slowing the clock can help remedy a marginal or intermittent JTAG connection.
      This can be done in the CCS configuration properties:
    • Launch the Setup CCS utility and Right Click on the configuration/connection name under 'My System' in the CCS System Configuration. Then click Properties
    • A new window will appear. In the new window click the tab labeled 'connection properties'.
    • Change the "JTAG TCLK Frequency (MHz)" to 'Automatic with user specified limit'.
    • Leave the value of 10.368 in the Value field.
    • Click finish and Save the configuration. Now launch into CCS.
    • If the connection can be made, then things should be fine and you are running. You may now go back into the configuration and increase the TCLK value from 10.368 to try and achieve faster JTAG Communication.
  • The SDConfig utility and SDFlash utility do not suppor the XDS560R USB JTAG Emulator
  • 4.6 XDS100 USB JTAG Emulator

  • A complete and up to date support source for the XDS100 emulator technology may be found on the Texas Instruments XDS100 Wiki web page at XDS100 Wiki

  • Code Composer Studio Configuration and Spectrum Digital Emulators

    5.1 CCS Configurations included with Driver installation

    Spectrum Digital emulation driver installations include a number of 'pre-built' configurations for Code Composer Studio. The installation includes configurations for connections to Spectrum Digital EVM, DSK, and eZdsp boards and common, single DSP (or SoC) device scan chains using Spectrum Digital emulators. Please note there may not be a configurtion with the exact naming convention that corresponds to every device. For example, in the screenshot below, there is not a configuration using the XDS510USB with a TMS320F2809, however the F2808 configuration is the closest. The emulation driver used in the F2808 configuration example also supports the F2809, as well as other F28xxx devices from TI. The only change to be considered in the CCS configuration is the GEL file. Modify the configuration to use a GEL file that more closely reflects the DSP or target board being used.




    5.2 Custom Board Configurations

    Custom configurations may be created using the Setup CCS utility. This is useful when the target has multiple JTAG devices in the JTAG scan chain. Please refer to the Help Menu in the Setup CCS utility for instruction how to create a custom CCS Configuration.

    The first step in creating the custom board requires to select the 'connection' that will be used. The 'connection' is the emulator connection that is being used. The 'Available Connections' in the Create Board tab and their associated Spectrum Digital emulators are as follows:

    "SD XDS560R USB Emulator" ---> XDS560R USB JTAG Emulator.

    "SD510 Emulator" ---> XDS510PP PLUS (parallel port), SPI525 PCI JTAG Emulators, and eZdsp boards using on-board parallel port / JTAG emulation.

    "SD510USB Emulator" ---> XDS510USB, XDS510USB PLUS, C2000 XDS510LC USB JTAG Emulators.

    "SDDSKUSB Emulator" ---> DSK, eZdsp, and EVM using on-board USB / JTAG emulation connections.


    5.3 XDS560R and CCS v4

    XDS560R support is included with the CCS v4 installation. However, the XDS560R setup installation is not executed during the current CCS v4 installation. The installation can be run manually. The setup executable is located in the following default install directory: "C:\Program Files\Texas Instruments\ccsv4\common" (your install directory may vary if you did not install in the default directory). Close the CCS v4 application and run the 'SetupSDXDS560R.exe' file. When it finishes, launch CCS v4 and you will now find the 'Spectrum Digital XDS560R USB Emulator' option populated in the connection list.


    Emulator Memory Summary

    6.1 Emulator Memory Summary

    The Following is a summary of memory types on SD emulators and usage. The XDS510USB and SPI530 emulators contain an emulation processor and memory for storage of the emulation application as well as data storage for the user�s target application. At no time would there ever be greater then 64K bytes of a user�s application code resident in the emulator at one time.

    XDS510PP:

    • 64byte EEPROM for ID storage. Cannot be modified in the field.

    XDS510PP PLUS:

    SPI515:

    • Serial ROM for FPGA boot. This ROM cannot be modified in the field.
    • 8Mbytess SDRAM for F28xx data logging buffer. The SDRAM is not used by any other processor.
    Once you unplug the power cable to the unit is lost and the SRAM and SDRAM are gone. Leaving the unit unpowered for 15 minutes would render the SRAM and SDRAM cleaned.

    XDS510USB and C2000 XDS510LC USB:

    • 8Mbytes External SDRAM (not present on C2000 XDS510LC USB)
    • 256K Internal SRAM
    • 16K EEPROM
    Once you unplug the XDS510USB/XDS510LC USB cable, power to the unit is lost and the SRAM and SDRAM contents are gone. Leaving the unit unpowered for 15 minutes would render the SRAM and SDRAM cleaned.

    The XDS510USB/XDS510LC includes an EEPROM which is a secure boot loader for the on board DA255 processor. This EEPROM is secured via TI boot loader encryption and NOT modified in the field. SD does not provide any SW or means to wipe this EEPROM in the field. In fact doing so would effectively render the XDS510USB/XDS510LC useless. Once wiped clean (erased) then the unit would have to be returned to factory to have the EEPROM replaced.

    SPI530 MPSD:

    • 56K External SRAM
    • 256K Internal SRAM
    • 512K Flash
    On power up, Flash boots to internal SRAM, external SRAM is data storage. Flash is not modified during normal operation but can be upgraded in the field when new firmware is required. Leaving the unit unpowered for 15 minutes would render the SRAM cleaned.

    SPI525 PCI:

    • 8Mbytess SDRAM for F28xx data logging buffer. The SDRAM is not used by any other processor.
    • 64bytes EEPROM for PCI enumeration.
    Leaving the host PC unpowered for 15 minutes would render the SDRAM cleaned.

    XDS510USB-PLUS:

    • 8Mbytes External SDRAM
    • 384K Internal SRAM
    • 16K EEPROM
    When USB cable is unplugged the SDRAM and SRAM loose contents. The EEPROM contains the emulator boot code which is not modified in the field.

    XDS560R:

    • 32Mbytes External SDRAM
    • 1M Internal SRAM
    • 16K EEPROM
    • 8M FLASH
    When power is removed the SDRAM and SRAM loose contents. The 8M FLASH contains the emulator boot code. The EEPROM contains emulation configuration settings. The FLASH and EEPROM are not modified in the field under normal operation. There are utilities included in the distribution that do all both the FLASH and EEPROM to be updated in the field but have to be run outside of the debug environment.

    XDS560v2 STM and XDS560v2 Traveler STM JTAG Emulators:

    • 256M DDR2
    • 64M NAND
    • 32K EEPROM
    • 210K On-Chip RAM main cpu
    • 8K On-Chip ROM main cpu
    Here are a few options to scrub the memories. The 'Sd560v2Config' utility is needed for the following steps. Sd560v2Config utility is the XDS560v2 configuration utility and is installed with our driver installation (which is run during the CCS v4 and later software installation).:
    1. Clean RAM: Power Cycle the emulator pod or us the 'Sd560v2Config' utility to reboot the emulator pod. In Sd560v2Config utility, click the "Dtc Conf" tab and select 'boot' from the COMMAND dropdown menu. Click 'RUN DTC_CONF'.
    2. Clean NAND: Reload factory firmware image using the Sd560v2Config utility. Click the "Dtc Conf" tab and select 'Update' from the COMMAND dropdown menu. Click 'RUN DTC_CONF'.
    3. Clean EEPROM: Use the Sd560v2Config Utility. Click the "Dtc Conf" tab and select 'restore' from the COMMAND dropdown menu. Click 'RUN DTC_CONF'.

    XDS200, XDS220, and XDS220ISO JTAG Emulators:

    • 8Mbyte SPI Flash for boot, non-volatile
    • 8Mbyte SDRAM for emulation execution, volatile
    • 128K Bytes SRAM on-chip for emulation execution, volatile
    The SRAM and SDRAM contents are lost when USB and/or external power input is removed. The SPI Flash contains boot firmware and operation parameters. These can be restored to factory defaults using the xds2xx_conf utility included with the product.

    Leave a Comment

    (0 Comments)

    Your email address will not be published. Required fields are marked *