- 1 Introduction
- 2 General Features
- 3 Which XDS110 is right for me?
- 4 Installation Instructions
- 5 Unboxing
- 6 Performance
- 7 Updating the XDS110 Firmware
- 8 Finding and updating the serial number
- 9 Debug and Trace Usage Modes
XDS110 is the newest class of JTAG debuggers for Texas Instruments' microcontrollers and embedded processors.
XDS110 is a low cost embedded MCU debug probe which has derived from the Stellaris ICDI debug probe family. The debug probe has a Tiva Snowflake (TM4C129) as the debug processor. XDS110 includes SWD/SWO and Energy Trace functionality.
It offers a balance of low cost with features between the super low cost XDS100 and mid range XDS200 classes of JTAG debuggers. Embedded (on-board) XDS110 debug probes are compatible with Code Composer Studio development environment version 6.1.0 and newer.
Standalone XDS110 Debug probes (TMDSEMU110-U) require CCSv7.0.0 or later.
- JTAG (IEEE 1149.1), cJTAG (IEEE 1149.7) ARM SWD (Serial Wire Debug) support
- ISA Support - check the product page at: http://www.ti.com/xds110
- OS integrated USB driver. USB 2.0 FS default and HS optional for higher performance
- ARM Cortex-M SWO via TDO (target interface) and USB COM port (host interface) in UART format
- EnergyTrace measurements exported via a USB bulk endpoint - no need to have an active CCS debug session open (some debuggers)
- Interface compliant with currently published XDS APIs and CMSIS-DAP
- OpenOCD ready (OpenOCD version 0.8 and above)
Which XDS110 is right for me?
XDS110 is currently available in both standalone or embedded versions. Some embedded debuggers featured on development kits can function as a standalone debugger to custom boards. Check compatibility with actual kits. Available kits/probes with XDS110:
- XDS110 Standalone Debug Probe
- SimpleLink™ MCU Platform LaunchPad™ development kits Support for MSP432™ host MCUs and Wi-Fi®, Bluetooth® low energy (BLE), Sub-1GHz wireless MCUs
- SimpleLink SensorTag Debugger DevPack - only recommended to be used with Sensortag development kits
- Selected Hercules Launchpads: LAUNCHXL2-RM46, LAUNCHXL2-RM57L, LAUNCHXL2-TMS57012 and LAUNCHXL2-570LC43
- Make sure XDS110 is not plugged in
- Install Code Composer Studio version 6.1.0 or later if using an embedded XDS110, install 7.0.0 or later if using a standalone XDS110.
- Plug in the XDS110. It should be properly recognized by the system.
Watch the video below to learn about the contents of the standalone XDS110 Debug Probe.
Check MSP432 results shown in the XDS Performance comparison page.
Updating the XDS110 Firmware
When using CCSv6.1.1 or CCSv6.1.0 with TI Emulators package version 22.214.171.124 or newer, the firmware on the XDS110 is updated automatically when connecting from inside CCS.
If manual updating or diagnostics is required, using a Windows host is highly recommended. Close any instances of CCS that are running in your system. Open a Windows Command Prompt and issue the following commands:
- Go to the directory where the utility is installed:
- C:\>cd C:\ti\ccsv6\ccs_base\common\uscif\xds110
- Run the configuration just to make sure a XDS110-class debugger is connected (or to list how many are connected) and what is the firmware revision installed on it:
- C:\ti\ccsv6\ccs_base\common\uscif\xds110>xdsdfu -e
- Put the XDS110 in DFU mode:
- C:\ti\ccsv6\ccs_base\common\uscif\xds110>xdsdfu -m
- Run the updater, passing the firmware file and resetting the debug probe afterwards:
- C:\ti\ccsv6\ccs_base\common\uscif\xds110>xdsdfu -f firmware.bin -r
In case of a bricked pod
In certain scenarios there is a chance your Pod or Launchpad becomes bricked by the firmware update. If that is your case, important recovery tips can be found at the end of the <ReadMe.txt> file located at the directory below:
Finding and updating the serial number
When using multiple debug probes in the same host, in general it is necessary to properly differentiate each debug probe by serial number.
To find out what is the serial number of all connected debug probes, follow steps 1 and 2 above
If you want to set the serial number to a specific value:
- Unplug all other debug probes from the host
- Follow steps 1 through 3 above
- Set the serial number:
- C:\ti\ccsv6\ccs_base\common\uscif\xds110>xdsdfu -s 01234567 -r
Debug and Trace Usage Modes
The XDS110 allows using multiple modes of operation through the option JTAG / SWD / cJTAG Mode of the Target Configuration Editor:
JTAG: compliant with IEEE1149.1
- 4 pin debug (TDI, TDO, TMS, TCLK)
- Supports TVRef
SWD: Serial Wire Debug
- 2 pin debug: SWDIO/TMS and SWCLK/TCLK
SWO: Serial Wire Output
- 1 pin trace (SWO/TDO)
- Supported only by DAP based devices like MSP432 which have DAP as the toplevel router in the scan chain.
- SWO trace can be obtained in UART or Manchester format. XDS-110 only supports UART format. The TDO/SWO pin is routed to a UART on the debug processor (Snowflake) during SWO capture.
- SWO (ITM) Usesecases:
- Function profiling (DWT - Data Watchpoint and Trace)
- Data variable trace (DWT - Data Watchpoint and Trace)
- Interrupt profiling (DWT - Data Watchpoint and Trace)
- Software messages (ITM - Instrumentation Trace Macrocell)
For additional details about Trace via SWO, check the following resources:
cJTAG: Compact JTAG or IEEE_1149.7
- 2 and 4 pin modes
- 2 OSCAN modes
- 2 pin mode allows using the other pins as a COM (UART) port
- Supported by selected Wireless Connectivity devices such as CC13xx, CC2538, CC26xx and CC32xx families.
EnergyTrace technology for MSP430/2 microcontrollers is an energy-based code analysis tool that measures and displays the application’s energy profile and helps to optimize it for ultra-low-power consumption. The tool can be used in three modes:
- ET: Energy profiling only
- ET+: Energy profiling + Program Counter trace
- ET++: Energy profiling + Program Counter trace + Peripheral state
Specifically for XDS110, currently the only board that supports Energy Trace is the MSP432 Launchpad. MSP432 devices support ET and ET+ but do not support ET++ as there is no support for profiling peripherals.
For additional details about Energy Trace for MSP432, please check the page below: