- 1 Overview
- 2 Adapters
- 3 Frequently Asked Questions
- 3.1 Q: I have an XDS560 right now, but it is an older one (ex: XDS560 v1 but not revision D). How do I upgrade my XDS560 cable to gain the additional features such as wait in reset, additional connection types, etc. (i.e. revison D)
- 3.2 Q: What if I want to use the XDS560 Trace capability to collect trace from the pins?
- 3.3 Q: Do any XDS560-class Emulators support Linux Operating Systems?
- 3.4 Q: Does the XDS560 support ARM Adaptive clocking?
- 3.5 Q: What is the difference between XDS510 and XDS560?
- 3.6 Q: Where to get an XDS560
- 3.7 Q: Problems with XDS560.sys Loading
- 3.8 Q: I have a Blackhawk XDS560 USB/Lan560. What does the LED indicate?
- 3.9 Q: My JTAG is not working with CCS...
- 3.10 Q: Are there lower cost options?
- 3.11 Q: Why does my Windows Device Manager show a warning for the TI XDS560 PCI Emulator?
- 3.12 Q: I am a TI 3rd party, and I want to create my own XDS510. What do I do?
- 3.13 Q: How do I get looback in a TI XDS560 Rev D cable to work?
- 3.14 Q: How do I get loopback in a Blackhawk XDS560 with a 20 pin cable (Rev D) cable to work?
- 3.15 Q: Can I use Boundary Scan with XDS560?
- 3.16 Q: Is RTDX supported with C2000 processors on the XDS560?
- 4 Related
- The XDS560 Emulator is a high speed JTAG connection between Code Composer Studio and the target device.
- More information can be found here: 
- The XDS560 Emulators support High Speed RTDX (HSRTDX)
|Warning:||As of 6/24/2010 RTDX and HS-RTDX are no longer supported. Alternative transports should be considered for the acquision of data, such as serial ports and ethernet. If you are currently using the technology and have no issues, there is no need to change. However, no action will be taken for support inqueries.|
- The XDS560 Emulators support Advanced Event Triggering
- The XDS560 Emulators support IEEE 1149.1 (JTAG)
- A general overview of TI emulation capabilities is here.
- For information about JTAG headers, please check the WIKI page JTAG Connectors.
- For debugging issues with JTAG, you may want to check the topic Debugging JTAG Connectivity Problems
- An XDS560 with Ethernet LAN support is available from here
- XDS560v2 System Trace
XDS560v2 System Trace
- The XDS560v2 System Trace emulator is now available. It offers increased performance and features.
XDS560 Rev D Cable
In addition to the standard XDS560 features, the XDS560 Rev D cable also supports:
- Compact TI 20-pin target card connector
- Adaptive clocking for TI devices with ARM processors
- EMU pin boot modes
- Remote system reset System Reset (Emulation)
- RTCK/TCK looback
Rev D cables can be identified by their "00D" at the end of the cable serial number.
The TI 20-pin target card connector reduces the PWB foot print over the traditional TI 14-pin target connector while expanding the number of EMU pins supported. See JTAG Connectors Wiki page for the TI 20-pin cable's pin assignments and target card connector part number. The board requirements provided in XDS560 Emulator Technical Reference are valid except in the adaptive clocking case. The additional EMU pins are treated electrically identical to EMU0 and EMU1. See below for SYSRST board requirment.
Adaptive clocking for ARM devices can be enabled through CCSetup’s Connection Properties page (see “JTAG TCKL Frequency (MHz)” selection options). See the Adaptive Clocking Wiki page for more information and board requirements. Generally, in CCS 3.3 Setup, you may need to select the create board option to enable the rev D capabilities. This can be seen in the screen shot below.
Once this is done, in the connnection properties, it is possible to select the "Adaptive Clocking" options.
For devices that support EMU Boot modes the XDS560 Rev D cable drives the selected EMU pin polarity on the rising edge of nTRST or TVD. The EMU pin polarity selection is enabled through CCSetup’s Connection Properties page (see “JTAG nTRST Boot Mode” or “Power on-Reset Boot Mode” selection options).To determine if your device supports boot modes, which modes are supported and the proper polarity for each boot mode see your device’s data sheet.
The XDS560 Rev D cable supports a remote system reset capability. The SYSRST signal from the 20-pin Emulator header on your board must be pulled up (we suggest a 4.7 ohm pull-up) to the target voltage level required by your board’s power-up-reset circuit. You can then remotely through CCS apply a reset your target system from the Debug->Advance Reset->System Reset menu. The STSRST signal will be active for ~1 millisecond.
JTAG Adapter Overview
There are two types of connectors:
- Emulator-This is the connector on the emulator/JTAG ICE/UIF/XDS unit
- Target-This is the connector on the target card
Types of adapters:
- Pin Converters-Passive conversion of one connector type to another
- Adapter-Some active components for different purposes. Ex: Addition of adaptive clocking, buffering of TCK/RTCK signals, Isolation, etc.
JTAG connectors cross reference
TI Part Number, Link to product, or 3rd party product Number
Note: The table below only references adapters available by TI and its direct third parties. It is possible to find other adapters for sale from external companies.
|Target connector||10-pin ARM||14-pin TI||20-pin TI||20-pin ARM||60-pin TI||60-pin MIPI||microSD|
|14-pin TI||N/A|| TMDSADP1414-ISO1
|20-pin TI||selected emulators8,15|| 20e_cTI-14t_TI6
|60-pin MIPI||N/A|| 60e_MIPI-14t_TI6
1 Isolation adapter
2 Voltage Translation
3 RTCK Signal Boost
4 Adaptive Clocking
5 http://www.lauterbach.com/frames.html?order/ord__7748.html - Code JTAG-ARM-CON-20-TI14
8 Bundled with Blackhawk XDS100v2 Model D
9 Bundled with Spectrum Digital XDS100v3
10 Bundled with Spectrum Digital XDS200 and XDS220 emulators
11 Bundled with Blackhawk XDS560 emulators: BP (only 20 TI to 14 TI), m, LAN, PCI.
12 Bundled with Spectrum Digital XDS560v2 LC Traveler and Spectrum Digital XDS560v2 STM Traveler
13 Bundled with Blackhawk USB560v2
14 Bundled with Blackhawk XDS560v2 and Spectrum Digital XDS560v2 STM with target adapters
15 Bundled with Blackhawk XDS200 emulators
Frequently Asked Questions
Q: I have an XDS560 right now, but it is an older one (ex: XDS560 v1 but not revision D). How do I upgrade my XDS560 cable to gain the additional features such as wait in reset, additional connection types, etc. (i.e. revison D)
- A: You can order from TI distributors the part number: TMDSCBL560 (6/18/2010: This product is no longer available. You may be able to order one from Blackhawk)
- A: Recommend you contact your XDS560 manufacturer and determine what upgrade options are available.
Q: What if I want to use the XDS560 Trace capability to collect trace from the pins?
- A: You will need the XDS560 Trace unit. There are more details here: XDS560 Trace
Q: Do any XDS560-class Emulators support Linux Operating Systems?
- A: Yes. Starting with CCS v5, the following Blackhawk models support operation on Linux:
- LAN560 (BH-LAN-560), USB560-M (BH-USB-560m), USB560-BP (BH-USB-560bp), USB560 (BH-USB-560)
For XDS560v2 models, see XDS560v2 System Trace
Q: Does the XDS560 support ARM Adaptive clocking?
- A: Yes, any XDS560 which is Revision D and above supports adaptive clocking. See: Adaptive Clocking for details on Adaptive Clocking.
- A: For CCSv3.3 with Service Release 12 and above, you can setup for adaptive clocking as in the photo below:
- A: For CCS v4.x, you can setup adaptive clocking as in the photo below:
Q: What is the difference between XDS510 and XDS560?
- A: XDS560 is capable of High Speed RTDX (HSRTDX), essentially it has the same functionality of an XDS510 class emulator but is significantly faster, with data rates of over 2MBps.
Q: Where to get an XDS560
Q: Problems with XDS560.sys Loading
- A: While working with CCS emulation (Blackhawk) setup, receives error stating TMS320C62XX" is not supported. It is because "XDS560.SYS" was not loading correctly.
There are two versions of xds560.sys in the system. Version A and Version B
Version A: c:\winnt\system32\xds560.sys Version B: c:\winnt\system32\drivers\xds560.sys
The system actually looks in the second location for the driver, but this version (B) can hang at boot time. Sometimes the xds560.inf file may not copy the correct files from/to the appropriate directories. Rather than edit xds560.inf, the workaround is to create a dummy directory c:\winnt\system32\drivers\Win2000_XP and put the working (A) version of the file in it. Then the New Hardware Found dialogue runs to completion and copies the correct file to the correct directory.
Q: I have a Blackhawk XDS560 USB/Lan560. What does the LED indicate?
- A: On the USB560m/LAN560, the USB LED is bi-color (red and green). This is the same for the USB560bp LED on the end panel.
Start-up: Power-up: RED Enumeration Complete: GREEN
In operation, USB status: Ready: GREEN Busy: RED
Q: My JTAG is not working with CCS...
- A: Please check: Debugging JTAG Connectivity Problems
Q: Are there lower cost options?
Q: Why does my Windows Device Manager show a warning for the TI XDS560 PCI Emulator?
- A: The Windows Device Manager is showing this error because a TI XDS560 PCI emulator is not installed. Windows cannot start the driver because the hardware is not installed in the PC. If you are NOT using this hardware emulator, then there is no issue and other emulators are not affected.
Q: I am a TI 3rd party, and I want to create my own XDS510. What do I do?
- A: Approved, TI 3rd parties can purchase an Emulation Porting Kit
Q: How do I get looback in a TI XDS560 Rev D cable to work?
- A: You will need to fix the connection XML file or as an extra board config file. You will need to insert one of the following combinations depending on what you are doing. (Note, this is not tested extensively.)
- A: This has been filed as an enhancement request (SDSCM00036610) for a fix in a future release.
# This combination loops the TCLKO/TCKI signals in the pod – the timing between return data and clock is modified. # DBGJTAG handles this OK if the target provides compatible return data timing. # CCS drivers won’t will handle this OK if the target provides compatible return data timing. # The XDS560 Trace pod also comprehends this combination and uses it with specific targets. loopback_mode=enable loopback_value=clock # this combination loops the TDI/TDO signals in the pod – the IR/DR scan-paths become 0-bits long # DBGJTAG handles this OK. # CCS drivers fail – they won’t find the target DSP/ARM/icepick loopback_mode=enable loopback_value=data # This combination loops the TDI/TDO and TCLKO/TCKI signals in the pod and disables the cable-break/power-loss detection. # The intention is to allow DBGJTAG to run emulator and cable tests even when the cable is not connected to any target al all. # DBGJTAG handles this OK. # CCS drivers fail – they won’t find the target DSP/ARM/icepick loopback_mode=enable loopback_value=total # this combination does nothing loopback_mode=disable loopback_value=disable
Q: How do I get loopback in a Blackhawk XDS560 with a 20 pin cable (Rev D) cable to work?
- In CCS v4.x, you need to select the loopback option.
Q: Can I use Boundary Scan with XDS560?
- Corelis has software which works with Blackhawk XDS560. See here
Q: Is RTDX supported with C2000 processors on the XDS560?