Please note as of Wednesday, August 15th, 2018 this wiki has been set to read only. If you are a TI Employee and require Edit ability please contact x0211426 from the company directory.

XDS560v2 System Trace

From Texas Instruments Wiki
Jump to: navigation, search

This page is no longer maintained and is kept here for reference only! For the most current version, please visit:



The XDS560v2 System Trace Emulator is the second generation of the XDS560-class emulators. It provides cost effective real-time emulation, debugging, and high-performance System Trace (STM) for Texas Instruments devices over both USB and Ethernet PC interfaces.

The System Trace (STM) capability is a set of built-in capabilities on the device that monitors synchronization and timing between cores and on-chip peripherals either configured via the Trace features of Code Composer Studio or built into the application (by using the library Ctoolslib). This has multiple uses: the ability to track bus and peripheral activity, monitor and benchmark data throughput, transfer debug messages through the JTAG channel (via modified printf or putc routines) and more.

Note: this is different than Core Trace or Instruction Trace, which is the emulation technology that performs real-time gathering of all instructions being executed in a processor. For these types of traces please check the Trace page.

This is available with selected CTools enabled devices.

The System Trace capability is compliant to Mobile Industry Processor Interface System Trace Protocol or MIPI STP for short. See for more details.



  • Code Composer Studio
  • Native 60 pin MIPI HSPT target cable, with adapters to: 20 pin compact TI, 14 pin TI, and 20 pin ARM connectors
  • Target debugging with JTAG (IEEE 1149.1) and IEEE 1149.7
  • Up to 50 MHz TCLK
  • Control for power-up/boot-mode on EMU0/1 pins
  • Auto sensing target voltage range from 1.2 volts to 4.1 volts
  • Approx 50% faster code download than XDS560 (v1)
  • JTAG debug isolation mode - ability to disconnect the emulator connection and have this result in the debug subsystem power down. This blocks driving any JTAG signals by the emulator/cable when CCS is not connected.
    • When the last CCS core/node disconnects, all the emulator/cable output signals will be tri-stated (Hi-Z). This blocks driving any JTAG signals by the emulator/cable.
  • JTAG TCLK loop-back option - ability to select TCLK loop-back with user-specified limit from Target Configuration in CCS
    • This enables CCS to connect to targets with no return clock (RTCK) pin.
  • Map boot-mode pins (EMU0 & EMU1) - ability to map boot-mode pins to any of the following pins
    • EMU1 = Pin TRD0.2 and EMU0 = Pin TRD0.1
    • EMU1 = Pin TRD0.1 and EMU0 = Pin TRD0.0
    • EMU1 = Pin EXTF and EMU0 = Pin EXTE

System Trace (STM)

  • Support for 1-4 pin System Trace with up to 100 MHz export clock (System Trace is compliant to MIPI STP)
  • 128 MBytes System Trace buffer storage
  • Auto compensating calibration for edge jitter, channel skews and duty cycle for robust trace data capture
  • Adaptive receiver technology supporting setup/hold times up to 1.5ns
  • Available on selected CTools enabled devices

PC Interfaces

The interfaces available vary by model. Most offer a USB2.0 high speed interface and some additionally offer Ethernet.


Target Board Connector Requirements

  • The XDS560v2 System Trace Emulator utilizes the 60-pin MIPI HSPT connector. The connector and target board electrical requirements and recommandation for Trace and JTAG support can be found in XDS Target Connection Guide.
  • Also see your Emulator manufacturer's documentation for emulator specific information. Users may also want to read the "Common Trace Transmission Problems and Solutions" at tidoc:SPRAAK6.
  • MIPI Connector recommendation can be found here.
  • 20 pin compact TI connector can be used for System Trace as it has 4 pins for data and 1 pin for clock (EMU0-5).
  • TI 14 pin can be used, but can only carry 1 pin data and 1 pin clock (EMU0/1)
  • ARM 20 pin connectors should NOT be used for CTools System Trace enabled devices as it does not carry signals for System Trace.

Where to buy


Spectrum Digital




Frequently Asked Questions (FAQs)


Q: Where can I see the documents for the Spectrum Digital XDS560v2 System Trace Emulator?

Q: Spectrum Digital has multiple XDS560v2 Emulator offerings. What is the difference between them?

Q: I have a 20 pin compact TI header / 14 pin TI header on my board but the XDS560v2 System Trace cable has 60 pin MIPI HSPT header. How do I use the XDS560V2 emulator with my target?

  • Your emulator should have come with adapters. If not, please contact your manufacturer.

Q: If user1 has a XDS560v2 Ethernet debug session started and user2 tries to connect also, what will happen?

  • With more recent versions of XDS560v2 firmware user1 is unaffected and user2 will receive the "Error initializing emulator" message.
  • With older versions of XDS560v2 firmware user1 is disconnected.

Q: Does the XDS560v2 support HSRTDX?

  • A: No.

Q: What do the LEDs mean on the XDS560v2 System Trace Emulator enclosure?

LED Name      Color       



ON- Power ON

OFF - Power Off

STATE-1 Green

ON - CCS debugger connected

OFF- CCS debugger disconnected

STATE-2 Yellow

ON - XDS560v2 System Trace Emulator FPGA programmed

OFF- XDS560v2 System Trace Emulator FPGA not programmed


ON - XDS560v2 System Trace Emulator ready (see note 1)

OFF - XDS560v2 System Trace Emulator not ready

FLASH (momentary) - Ethernet connection refused (see note 2)


ON - XDS560v2 System Trace Emulator is booting

FLASH (momentary) - XDS560v2 System Trace Emulator configuration activity


ON - XDS560v2 System Trace Emulator to Host activity (trace upload)

OFF - No transfer


ON - Data capture by STM receiver

OFF - No capture




Flashing SAFE MODE.  When all three are simultaneously flashing this indicates safe mode.  The likely causes are a failed firmware upgrade, or multiple failed boot attempts. See here for instructions.


  1. While booting into SAFE MODE the green ACTIVITY-1 LED and the red STATE-3 LED will both be ON.
  2. Only one ethernet client may use the XDS560v2 System Trace Emulator at a time.  The ethernet connection will be refused if another client is already connected in CCS.  In this case the error message will be "Error initializing emulator".


Q: What version of Code composer Studio is supported?

  • A: The XDS560v2 System Trace emualtor supports Code Composer Studio v4.2 and newer.

Q: Is Code Composer Studio v3.3 supported?

  • A: No, the XDS560v2 System Trace emulator is supported by Code Composer Studio v4.2 and newer.

Q: What utility can I use to configure my Spectrum Digital XDS560v2 System Trace XDS560v2 System Trace Emulator? (SD560v2Config)

  • Spectrum Digital provides a utility which has much of the functionality as XDS560v2 System Trace Emulatorconf. This utility is called SD560v2Config.exe. This utility can be found in "...\ccsv4\common\uscif" directory. The manual is available via the HELP->Documentation from within the utility.


Q: How do I make sure that the XDS560v2 System Trace emulator is ready to use and functional?

  • Once the POWER, STATE-2 and the STATE-3 LEDs are ON (all of them), XDS560v2 System Trace emulator is ready to use.
  • You can also use the dtc_conf configuration utility. For example, dtc_conf get sd560v2u 0 will display all the XDS560v2 System Trace Emulator configuration variables of the connected XDS560v2 System Trace Emulator. Since the command will display an error if the XDS560v2 System Trace Emulator is not connected or hasn't finished booting, this command may be used to determine that the link between your PC and the XDS560v2 System Trace emulator is good.

Q: The LEDs are flashing and I can't connect to the XDS560v2 System Trace Emulator in CCS, what does this mean?

  • This means the XDS560v2 System Trace Emulator is in safe mode. This may occurr if ...
    • A XDS560v2 System Trace Emulator firmware update has failed.
    • The XDS560v2 System Trace Emulator fails to completely boot multiple times.
  • You can use the dtc_conf utility to boot back into normal mode. Issue the following two commands to reboot into normal mode ...
$ dtc_conf set sd560v2u 0 safeMode=false
$ dtc_conf boot sd560v2u 0
  • If the XDS560v2 System Trace Emulator fails to boot into normal mode the firmware may be corrupt or safe mode has been activated if power has been cycled repeatedly.
  • The above example shows USB. For Ethernet, change the above instructions for "sd560v2u" to "sd560v2e" and "0" should change to the IP address.

Q: When I launch CCS and try to connect, I see "Emulator not initialized" error message. What could be wrong?

  • USB connection
    • Make sure that USB cable is plugged in, drivers are installed correctly, and its functional.  Hint: in Windows use the device manager to see the USB device is recognized/removed when the USB cable is plugged/unplugged respectively.
    • Also, check if the USB port is correctly selected. There could be an issue if you are trying to use another USB emulator at the same time from the same PC.  Please disconnect the USB cable of any emulator that is not in use.
  • Ethernet Connection:
    • Check the IP address of the XDS560v2 System Trace Emulator entered in the CCS board configuration. You can read the IP address via a USB connection using the configuration utility  Note: it is possible for the XDS560v2 System Trace Emulator's IP address to change if it is configured for DHCP.  This is more likely if the XDS560v2 System Trace Emulator has been powered off for an extended period of time or moved to another location.
    • Make sure another CCS user isn't already connected.  The XDS560v2 System Trace Emulator limits ethernet connections to one CCS client at a time.  You can use the configuration utility to determine if another user is connected and what IP address they are using.
    • Look at the LED on the emulator ethernet connection. These should be blinking indicating network connection.
  • General Troubleshooting

Q: I keep getting a USB error, what do I do?

  • If you see a USB error such as:
C:\ccsv4\common\uscif\dtc_conf get sd560v2u 0 ipAddress
E_RPCENV_IO_ERROR(-6) No connection
ERROR: 1 : dtc_conf_utils_rpc.cpp(54) : operation failed : sd560v2u:0
  • It might be due to the USB connection on your PC. Try a different USB port (If in front, move to back. Try different USB cable). If using Spectrum Digital XDS560v2 then try the SD560v2Config utility and under the USBStatus tab run USB TestLoopBack. This runs a simply USB packet test to verify basic drivers and hardware connections.

Q: How can I check if the USB driver is setup correctly?

  • You shold be able to look in Windows Devices to see if it is setup properly. It should look like below when USB is setup correctly.


Q: When I try to start the Trace Control I get the "Target is disconnected" error message, what could be wrong?

  • This usually means that a device that was previously connected has been disconnected. Ensure that all the devices are connected by selecting the device in the tree list and pressing the Connect button.

Q: I get the "failed to calibrate channel : no signal on clock : check external pin manager settings and clock circuit connection" error message from the Trace Control, what could be wrong?

  • The message indicates that no target transmitter clock was detected during the receiver calibration. This usually means that the external pin manager has not been enabled. To enable it run the appropriate GEL script commands for your device.

Q: I do not see the STM node in the CCS debug view even if I have this setup in the CCS setup configuration.

  • This is probably caused by not turning on option to view non-debuggable devices. This option can be turned on from CCS debug view options. Once the option is checked, you need to re-launch the debugger.

Q: What if someone is already using the emualtor via ethernet? / What does "SC_ERR_OCS_ALREADY_OPEN" mean?

  • A: If someone is already using the emulator on ethernet, you may get an error message like SC_ERR_OCS_ALREADY_OPEN. This means someone already has a connection to the emulator.

Q: How can I confirm the IP address of the 560v2 unit I am trying to access?

  • A: When using DTC_CONF, the ACTIVITY-1 LED should blink briefly.
  • A: For example, using DTC_CONF get x.x.x.x will blink ACTIVITY-1 LED.

Q: When trying to use SD560v2Config.exe I get the message "Application Error: The application has failed to initialize properly (0xc0000135). Click on OK to terminate the application."

Q: Ethernet isn't working but USB is what could be wrong with ethernet?

  • A: Versions prior to and including epkRev=5.0.329.0 have a bug that can cause certain values of the dtcName variable to prevent ethernet from starting (hint: dtc_conf get sd560v2u 0 epkRev).  Change the dtcName to all alpha-numeric characters and reboot the DTC (hint: dtc_conf set sd560v2u 0 "dtcName=Abc_123"). See dtc_conf.
  • A: Certain settings of the dtcConfig variable will prevent ethernet from starting. If your network supports DHCP (or you aren't sure), change the dtcConfig to "dhcp" and reboot the DTC (hint:  dtc_conf set sd560v2u 0 "dtcConfig=dhcp").  If your network does not support dhcp you may set dtcConfig to a static IP address instead.See dtc_conf.
  • A: If a network connection is not present while the DTC is booting ethernet will not be started. Connect the network first, then reboot the DTC.

Q: Where do I learn more about system trace?