Texas Instruments XDS110 User manual

XDS110 Debug Probe
User's Guide
Literature Number: SPRUI94
January 2017

2SPRUI94–January 2017
Submit Documentation Feedback
Copyright © 2017, Texas Instruments Incorporated
Table of Contents
Contents
1 Overview............................................................................................................................. 4
1.1 XDS110 Probe Feature Summary ..................................................................................... 4
1.2 XDS110 System Summary ............................................................................................. 4
1.3 XDS110 Performance ................................................................................................... 5
1.4 XDS110 Probe Overview................................................................................................ 5
1.5 XDS110 Parts List........................................................................................................ 6
1.6 Acronyms, Abbreviations, and Definitions ............................................................................ 6
2 Probe Interfaces................................................................................................................... 8
2.1 Supported Communication Protocols.................................................................................. 8
2.2 USB ........................................................................................................................ 8
2.3 Debug Interface .......................................................................................................... 8
2.4 Auxiliary Debug Interface ............................................................................................... 9
2.5 Probe Expansion Header.............................................................................................. 10
3 Functional Description and Operation................................................................................... 12
3.1 Basic Setup for the Debug Connection.............................................................................. 12
3.2 Auxiliary Target Control................................................................................................ 13
3.3 SWO Trace Capture.................................................................................................... 13
3.4 ETB Trace Support..................................................................................................... 13
3.5 LED Operation .......................................................................................................... 13
3.6 Energy Trace............................................................................................................ 13
3.7 Host SW Interfaces..................................................................................................... 17
4 XDS110 Adaptors ............................................................................................................... 25
4.1 Debug Connection Adaptors.......................................................................................... 25
4.2 Auxiliary Connection Breakout Board................................................................................ 25

www.ti.com
3
SPRUI94–January 2017
Submit Documentation Feedback Copyright © 2017, Texas Instruments Incorporated
List of Figures
List of Figures
1 XDS110 Probe High-Level Block Diagram ............................................................................... 6
2 Debug Connection (CTI-20) Pin Mapping ................................................................................ 9
3 AUX Connection Signal Mapping ........................................................................................ 10
4 Setup Power Source Control ............................................................................................. 12
5 Probe-Supplied Power and Voltage Level .............................................................................. 13
6 Enabling ET on Connect .................................................................................................. 14
7 Selecting XDS110.......................................................................................................... 15
8 EnergyTrace Overview .................................................................................................... 15
9 EnergyTrace and the Toolbar ............................................................................................ 16
10 EnergyTrace Dynamic View .............................................................................................. 16
11 xdsdfu Screenshot ......................................................................................................... 19
12 dbgjtag Screenshot JTAG Integrity Test ................................................................................ 22
13 dbgjtag SWD Integrity Test ............................................................................................... 23
14 dbgjtag Scan Path Test.................................................................................................... 23
List of Tables
1 Acronyms and Definitions................................................................................................... 6
2 Expansion Header Signal Mapping...................................................................................... 11
3 LEDs and Probe Operational States..................................................................................... 13
4 CTI to Other Adaptor Pin Mapping....................................................................................... 25
5 Auxiliary Breakout Board Signal Mapping .............................................................................. 26

4SPRUI94–January 2017
Submit Documentation Feedback
Copyright © 2017, Texas Instruments Incorporated
XDS110 Debug Probe
EnergyTrace is a trademark of Texas Instruments.
ARM is a registered trademark of ARM, Limited.
Mac OS is a trademark of Apple, Inc..
Linux is a registered trademark of Linus Torvalds.
Windows is a registered trademark of Microsoft Corporation.
User's Guide
SPRUI94–January 2017
XDS110 Debug Probe
1 Overview
The XDS110 debug probe is a low-cost system for debugging and tracing embedded systems centered on
Texas Instruments (TI) microcontroller, microprocessor, and DSP-based systems. The XDS110 has
improved performance relative to the XDS100 probe family, and added several useful capabilities such as
probe-supplied target power and enhanced I/O. The XDS110 also includes support for power and energy
profiling through TI’s EnergyTrace™ (ET) technology.
1.1 XDS110 Probe Feature Summary
• Basic debug communications to the target system
– IEEE 1149.1 (JTAG)
– IEEE 1149.7 (cJTAG)
– ARM serial wire debug (SWD)
• Enhanced and auxiliary debug communications
– Support for trace capture through ARM serial wire output (SWO) – UART mode only
– Support for UART communications to and from the target system
– Support for GPIO channels
• Target I/O voltage support from 1.8 V to 3.6 V
• Power profiling features
– Support for TI EnergyTrace
• Host communications
– USB 2.0 high-speed (HS) communication link to the debug host system
– Probe power through USB 5-V supply
• Expansion
– A 30-pin expansion interface that can support a wide array of auxiliary functions
• Target power can be supplied from the probe
1.2 XDS110 System Summary
• Host platforms supported
– The system supports various versions of Windows®, Mac OS™, and Linux®operating systems.
Consult the documentation for CCS and other development environments for more details.
• IDE versions supported
– TI CCS v7.0 and later
– IAR (see IAR documentation)
– Keil (see Keil documentation)

www.ti.com
Overview
5
SPRUI94–January 2017
Submit Documentation Feedback Copyright © 2017, Texas Instruments Incorporated
XDS110 Debug Probe
• TI platforms, devices, and ISAs supported
– MSP432 MCUs
– CC26xx/13xx wireless MCUs
– CC32xx/31xx Wi-Fi MCUs
– Hercules and Conqueror safety MCUs
– Sitara
– Stellaris MCUs
– C2000 MCUs
– C66xx
– C64x+
– C674x
– C55xx
– C54xx
– DaVinci
– OMAP
1.3 XDS110 Performance
The XDS110 debug probe has much higher debug performance than XDS100v2. Depending on the target
device, host environment, and configuration, the XDS110 performs 3× to 5× better than the existing
XDS100v2 debug probe.
Example: BeagleBone Cortex A8 (Code Composer 6.2 setup on Windows 7 PC):
• XDS100v2 RAM download = 21 kbps
• XDS110 RAM download = 110 kbps
NOTE: Some TI scan-based debug platforms, such as the C6000, C5500, and C2000 DSP families,
will not see the same magnitude of performance improvements.
1.4 XDS110 Probe Overview
Figure 1 shows a high-level diagram of the major functional areas and interfaces of the XDS110 probe.
Details of these are contained in Section 3.

Debug Control
MCU
Energy
Trace
Subsystem
USB
Interface
Voltage Translation
Expansion Interface
Target Debug Connection
Target Auxiliary Connection
USB Host Connection
x
x
x
x
x
JTAG
cJTAG
SWD
Reset
SWO
XDS110
Probe
UART
Power
GPIO
Target
System
(DUT)
Overview
www.ti.com
6SPRUI94–January 2017
Submit Documentation Feedback
Copyright © 2017, Texas Instruments Incorporated
XDS110 Debug Probe
Figure 1. XDS110 Probe High-Level Block Diagram
1.5 XDS110 Parts List
The XDS110 debug probe system consists of the following hardware:
• The XDS110 debug probe
• One USB cable with Type-A female host connector and micro-B female connector for the probe
• One debug connection cable with CompactTI 20-pin connector (CTI-20)
• One auxiliary connection cable with 14-pin header
• One CTI-20 to Cortex-M 20-pin adaptor
• One CTI-20 to Cortex-M 10-pin adaptor
• One CTI-20 to TI 14-pin adaptor
• One 14-signal AUX breakout adaptor
1.6 Acronyms, Abbreviations, and Definitions
Table 1 shows the common acronyms and abbreviations used in this document.
Table 1. Acronyms and Definitions
Acronym Definition
cJTAG Compact JTAG
CAN Controller area network
CMSIS-DAP Cortex microcontroller software interface standard – debug access port
ET Energy trace
GPIO General purpose input output
HS High speed
IDC Insulation-displacement connector
JTAG Joint test action group
OTG On the go
SSI Synchronous serial interface
SWCLK Serial wire clock
SWD Serial wire debug

www.ti.com
Overview
7
SPRUI94–January 2017
Submit Documentation Feedback Copyright © 2017, Texas Instruments Incorporated
XDS110 Debug Probe
Table 1. Acronyms and Definitions (continued)
Acronym Definition
SWDAT Serial wire data
SWO Serial wire output
TCK Test clock
TDI Test data input
TDO Test data out
TMS Test mode select
TRSTn Test reset (not)
UART Universal asynchronous receiver transmitter
USB Universal serial bus
CAUTION
This debug probe contains components that can potentially be damaged by
electrostatic discharge. Always transport and store the debug probe in the
supplied ESD bag when not in use. Handle using an antistatic wristband.
Operate on an antistatic work surface. For more information on proper
handling, refer to Electrostatic Discharge (ESD) (SSYA010).

Probe Interfaces
www.ti.com
8SPRUI94–January 2017
Submit Documentation Feedback
Copyright © 2017, Texas Instruments Incorporated
XDS110 Debug Probe
2 Probe Interfaces
The XDS110 probe supports a number of interfaces for host and target communication.
2.1 Supported Communication Protocols
The XDS110 probe supports the following industry standard interfaces for host to probe and probe to
target communications:
• Host to probe communication
– USB 2.0 device with HS USB PHY
– USB Communication Device Class protocol used for UART support
– Standard USB Bulk IN and OUT endpoints support TI custom protocols
• Probe to target communications
– IEEE 1149.1 JTAG
– IEEE 1149.7 cJTAG
– ARM serial wire debug (SWD)
– ARM serial wire output (SWO) – UART mode only
– Transmit and receive UARTs with RS-232C signaling – no hardware handshakes
2.2 USB
Host to probe communication is accomplished through a USB link. The probe has a female micro-USB B
type connector. The probe functions as a USB device only (no host mode or OTG). Power for the XDS110
probe is sourced from the USB VBUS (+5 V).
2.3 Debug Interface
The XDS110 probe supports a debug connection interface through the standard CTI-20 connector (see
Section 2.3.1). The supported debug features include:
• 5-pin 1149.1 JTAG connection (including TRSTn)
• 2-pin 1149.1 cJTAG connection
• 2-pin ARM SWD connection
• 1-pin SWO overlaid on JTAG TDO
• Target system reset
• Target voltage detect
• Target disconnect detect
• Four EMU signals for GPIO
– 2 × Probe to target
– 2 × Target to probe
– These signals are replicated on the AUX connector because many of the debug adaptors for CTI-
20 do not support connections with GPIO.
2.3.1 Physical Connection for Debug
The CTI-20 connection is a 20-pin IDC connection using .050 by .100 inch pitch. The pin mapping is
shown in Figure 2.

www.ti.com
Probe Interfaces
9
SPRUI94–January 2017
Submit Documentation Feedback Copyright © 2017, Texas Instruments Incorporated
XDS110 Debug Probe
Figure 2. Debug Connection (CTI-20) Pin Mapping
2.4 Auxiliary Debug Interface
The XDS110 probe supports an auxiliary interface (AUX) for additional debug features through a second
14-signal cable and connector (see Section 2.4.1). Many of the AUX features and functions are not
available on the standard CTI-20 connector. These additional features include:
• A probe/target UART
• Probe-supplied target power
May be monitored for ET
• Target power supply input
May be looped back to the Target after monitoring for ET
• Four GPIO signals
– 2 × Probe to target
– 2 × Target to probe
– These signals are replicated the CTI-20 connector, but are also present for scenarios where
adaptors on the CTI-20 are supporting debug connections without GPIO capability.
2.4.1 Physical Connection for AUX
The AUX connection is a 14-pin IDC connection using .05 inch pitch. It is Samtec FFSD-compatible, with
the female connector on both ends. The pin mapping is shown in Figure 3.

Probe Interfaces
www.ti.com
10 SPRUI94–January 2017
Submit Documentation Feedback
Copyright © 2017, Texas Instruments Incorporated
XDS110 Debug Probe
Figure 3. AUX Connection Signal Mapping
A breakout adaptor is also supplied for this interface (see Section 4.1.2)
2.5 Probe Expansion Header
The XDS110 probe also supports an expansion header, for adding functionality to the XDS110 system. It
exposes a number of functional interfaces of the TM4C129 debug control CPU, and these can be utilized
by logic external to the probe. The functional interfaces include:
• GPIO
• UART
• I2C
• SSI
• CAN
• ADC (reference voltage for ADCs is 2.5 V)
• Timer input
All these interfaces operate at the 3.3 V of the controller, and that voltage is supplied on the connector. A
5-V source is also available for higher voltage needs such as relays.
The expansion port also has interfaces for accepting a power input supplied by the target system, and a
path to send power back to the target system through the XDS110 probe AUX connector. The primary use
case for these features is for energy trace monitoring, but it can be used for other functions.
2.5.1 Physical Connection for the Expansion Interface
The XDS110 probe supports a 30-pin IDC female socket with .100 inch pitch. It exposes additional
functionality of the XDS110 debug processor (TMC4129) for add-on modules. The signal mapping for this
connection is shown in Table 2, but utilizing this interface is generally reserved for TI and designated third
parties that have the ability to integrate the add-on functionality into the entire system.

www.ti.com
Probe Interfaces
11
SPRUI94–January 2017
Submit Documentation Feedback Copyright © 2017, Texas Instruments Incorporated
XDS110 Debug Probe
Table 2. Expansion Header Signal Mapping
Alternate Functions Tiva
Pin XDS110 Signal
Name Pin Pin XDS110 Signal
Name Tiva Pin Alternate Functions
GPIO (PB5), ADC
(AIN11), I2C5 Data 120 ET_SSICLK 1 2 ET_PN0 107 GPIO (PN0)
GPIO (PB4), ADC
(AIN10), I2C5 Clock 121 ET_SSIFSS 3 4 ET_PN1 108 GPIO (PN1)
GPIO (PE4), ADC (AIN9) 123 ET_SSIDAT0 5 6 ET_PN2 109 GPIO (PN2)
GPIO (PE5), ADC (AIN8) 124 ET_SSIDAT1 7 8 ET_PN3 110 GPIO (PN3)
Ground GND 9 10 GND Ground
ADC (AIN1), GPIO (PE2) 13 ET_AIN1 11 12 ET_SCL 112 GPIO (PN5)
ADC (AIN2), GPIO (PE1) 14 ET_AIN2 13 14 ET_SDA 111 GPIO (PN4)
GPIO (PB0), CAN1 RX,
UART1 RX, I2C5 Clock 95 ET_PB0 15 16 ET_PM2 76 GPIO (PM3),
Timer3 CCP0
GPIO (PC4), UART7 RX 25 ET_PC4 17 18 ET_PH3 32 GPIO (PH3)
GPIO (PB1), CAN1 TX,
UART1 TX, I2C5 Data 96 ET_PB1 19 20 ET_PC5 27 GPIO (PC5), UART7 TX
POD_NON_ET
_VCC_SUPPLY 21 22 POD_NON_ET
_VCC_SUPPLY
DEBUG_TARGET
_VDD_IN 23 24 DEBUG_TARGET
_VDD_IN
Ground GND 25 26 GND Ground
Digital 3.3 V E3V3 27 28 E5V0 Digital 5 V
Digital 3.3 V E3V3 29 30 E5V0 Digital 5 V

Functional Description and Operation
www.ti.com
12 SPRUI94–January 2017
Submit Documentation Feedback
Copyright © 2017, Texas Instruments Incorporated
XDS110 Debug Probe
3 Functional Description and Operation
3.1 Basic Setup for the Debug Connection
Setting up the XDS110 debug probe is similar to most of the other debug probes in the TI portfolio, and
the general debug tool documentation can guide users on the basic setup.
Refer to the CCS getting started guide for details on setup and configuration steps. Similar documentation
exists for other IDE vendors. Extra setup steps are required for some features, and these are outlined
below.
3.1.1 Target-Supplied Power
The XDS110 debug probe can be used for debugging targets across 1.8-V to 3.6-V IO levels. The
XDS110 probe can also be used to supply power to targets with 1.8-V to 3.6-V IO and with current draw
limited to ~400 mA. Configuring the power supply capability requires some additional setup steps.
3.1.1.1 Hardware Setup
When the target is being powered externally, the debug probe does not supply the power. The only
connection between the XDS110 and the target is the JTAG header. No other HW setup is required.
3.1.1.2 CCS Setup
To use the XDS110 probe in Code Composer Studio, CCSv7.0 or later must be installed. To set up the
connection properties, open the CCXML target configuration for the target, click on the Advanced tab, and
select the XDS110 in the hierarchy. The panel on the right shows all the XDS110 connection properties.
Set the Power Selection field to Target supplied power, and the Voltage Level to Default, as shown in
Figure 4.
Figure 4. Setup Power Source Control
3.1.2 Probe-Supplied Power
The ability to supply target power from the probe is a new feature of the XDS110, and requires additional
HW and SW setup.
3.1.2.1 Hardware Setup
In this mode, the XDS110 JTAG header is connected to the target for debug, and the XDS110 AUX cable
is used to supply the power. The TGTSUPPLYOUT and GND pins on the AUX connector (refer to the
Figure 3) are connected to the supply pins of the target.
3.1.2.2 CCS Setup
To use the XDS110 probe in Code Composer Studio, CCSv7.0 or later must be installed. To set up the
connection properties, open the CCXML target configuration for the target, click on the Advanced tab, and
select the XDS110 in the hierarchy. The panel on the right shows all the XDS110 connection properties.
Set the Power Selection field to Probe supplied power. An edit box appears for voltage level. Specify the
target IO voltage level in the edit box. Figure 5 shows an example configuration with supply set to 3.3 V.

www.ti.com
Functional Description and Operation
13
SPRUI94–January 2017
Submit Documentation Feedback Copyright © 2017, Texas Instruments Incorporated
XDS110 Debug Probe
Figure 5. Probe-Supplied Power and Voltage Level
The power supply to the target is turned on when a debug or EnergyTrace session is started, and turned
off when the session terminates.
3.2 Auxiliary Target Control
There are additional interfaces between the probe and target that are mapped to GPIO signals on both the
CTI-20 and AUX cable. A typical use case for these signals is to drive GPIO inputs to the target to control
boot modes. Currently, the state of these signals can be set through the dbgjtag utility (see
Section 3.7.3.3).
3.3 SWO Trace Capture
The XDS110 probe supports ARM®SWO (serial wire output) trace for TI’s single-core MCU and WCS
devices. SWO trace is a single-pin trace interface that can be used for profiling hardware events such as
program counter, data reads/writes, and interrupt entry and exit, as well as application-initiated software
messages. When the XDS110 probe is supporting debug communication through 2-pin protocols such as
ARM SWD (2-pins) or 2-pin cJTAG, the target may reuse the TDO pin for SWO trace output. Currently,
only UART format is supported for transport of SWO data from target to host.
For more details on how to use SWO trace in Code Composer Studio and the devices supported, refer the
documentation at the following link: http://processors.wiki.ti.com/index.php/SWO_Trace.
3.4 ETB Trace Support
The XDS110 probe supports exporting trace data stored in on-chip buffers called ETB (embedded trace
buffer). The trace data captured in the ETB is device or trace component-specific. For more details on
using the ETB, refer the documentation at the following link:
http://www.ti.com/lit/ug/spruhm7b/spruhm7b.pdf
3.5 LED Operation
The XDS110 probe supports two LEDs to provide feedback on the operating state to the user. Table 3
maps LED functionality to probe operational states.
Table 3. LEDs and Probe Operational States
Green LED Red LED Probe Status
Off Off Probe is not powered, booting, or in Flashing mode
On Off Probe is operating normally but no active debug connection
On On Probe is operating normally and there is an active debug connection
On Rapid Flash Debug transactions are being processed
3.6 Energy Trace
3.6.1 Introduction
The XDS110 debug probe has on-board circuitry that can be used for measuring the target’s energy
consumption. The hardware circuitry provides high-accuracy energy consumption with low bandwidth
current and power profile. The energy profiling range covers 1-µA to 100-mA current draw, above which
the tool will display an overcurrent message and shutdown. This tool is ideal for characterizing energy
consumption, but not for capturing short current spikes, because sampling occurs over large time windows
(~500 µsec).

Functional Description and Operation
www.ti.com
14 SPRUI94–January 2017
Submit Documentation Feedback
Copyright © 2017, Texas Instruments Incorporated
XDS110 Debug Probe
3.6.2 Specifications
3.6.2.1 Accuracy
• ± 2% OR ± 500 nA, Condition: I < 25 mA, VBUS = 5-V constant
• ± 5% OR ± 500 nA, Condition: I > 25 mA & I < 100 mA, VBUS = 5 V
• Overcurrent condition > 100 mA
3.6.2.2 Device Support
EnergyTrace is only available on single-core Cortex M devices at this time. This includes the MSP432,
CC13/26xx, CC31/32xx, and the TM4C family of devices.
3.6.2.3 Modes
Depending on the target capability, there are three modes of energy profiling:
1. EnergyTrace: Energy profiling only. This mode is supported for all the single-core Cortex M devices
mentioned above.
2. EnergyTrace+: Energy profiling with program counter correlation. This mode is supported for the
MSP432 device family only.
3. EnergyTrace++: Energy profiling with program counter and peripheral state correlation. This mode will
be available in upcoming devices.
The XDS110 can support all of the above modes if the target device supports it.
3.6.3 Hardware Setup
The XDS110 debug probe must supply power to the target for measuring energy. Refer to Section 2 for
hardware setup required when the probe is supplying power.
3.6.4 Usage in Code Composer Studio
The EnergyTrace tool in Code Composer Studio can be used for profiling energy, power, and current
consumption while a debug session is active, as well as outside of a debug session.
3.6.4.1 CCS Setup
Refer to Section 2 for details on the target connection (CCXML) setup.
To start the EnergyTrace tool automatically on launching debug session, open up the Preferences section
by going to the Window menu and selecting the Preference menu item. Enable the checkbox for “Enable
Auto-launch on target connect”.
Figure 6. Enabling ET on Connect
Alternatively, if the EnergyTrace tool must be started after establishing a debug connection, then when the
core is connected, go to the Tools menu and select the EnergyTrace menu item.
Set the target connection as XDS110. Figure 7 indicates the specific fields.

www.ti.com
Functional Description and Operation
15
SPRUI94–January 2017
Submit Documentation Feedback Copyright © 2017, Texas Instruments Incorporated
XDS110 Debug Probe
Figure 7. Selecting XDS110
3.6.4.2 EnergyTrace Within a Debug Session
When a debug session is launched, the core is connected, and the EnergyTrace tool is started, three
EnergyTrace windows appear. The windows include the EnergyTrace Technology (main view), which
shows the statistical data, the Power graph, and the Energy graph. Trace collection starts when the core
runs and stops, either when the core halts or when the stopwatch timer in the main view expires,
depending on whichever occurs first. The trace collection time can be changed by clicking on the
stopwatch icon in the EnergyTrace Technology window.
Figure 8 shows a sample collection of 10 seconds. The Main UI shows the average, minimum, and
maximum current and power consumed, as well as the total energy consumption. It also indicates the
estimated battery life. The graphs show the consumption over time.
Figure 8. EnergyTrace Overview
The EnergyTrace session is automatically terminated when the debug session is terminated. To terminate
EnergyTrace collection while debugging, click on the red power icon in the EnergyTrace Technology
window.
3.6.4.3 EnergyTrace Without Debug Intervention
In this capture mode, true energy measurements can be performed without debug overhead. To do so,
first disconnect the JTAG header from the target. To start the tool, click on the blue icon with the
EnergyTrace Logo from the CCS Toolbar, as shown in Figure 9.

Functional Description and Operation
www.ti.com
16 SPRUI94–January 2017
Submit Documentation Feedback
Copyright © 2017, Texas Instruments Incorporated
XDS110 Debug Probe
Figure 9. EnergyTrace and the Toolbar
A dialog box opens up describing EnergyTrace measurement terminology. Click on the Proceed button.
Three EnergyTrace windows open up. The windows include the EnergyTrace Technology (main view)
display, which shows the statistical data, the Power graph, and the Energy graph.
To start EnergyTrace capture, click on the green Start icon in the EnergyTrace Technology window. The
duration of the capture can be changed by using the stopwatch icon in the main view. To stop trace
collection while trace capture is in progress, click on the Pause icon that replaces the Start icon. Trace
capture can be restarted by clicking on the green Start icon again.
Figure 10 was taken with an MSP432 LaunchPad running a low-power application. The target was reset in
the middle of the capture, causing a shoot up of the power and current consumed, indicating wakeup
followed by a dip, which indicates entry into a low-power state. Note that the device is completely
disconnected.
Figure 10. EnergyTrace Dynamic View
The EnergyTrace Technology window shows the true values for average, minimum, and maximum current
and power consumed, as well as the total energy consumption. It also indicates the estimated battery life.
The graphs show the true consumption numbers over time.
To terminate EnergyTrace collection, click on the red power icon in the EnergyTrace Technology window.
3.6.4.4 MSP432 EnergyTrace+ (Energy Consumption With Program Correlation)
For details on how to invoke ET+ mode, available only with the MSP432 device family, refer to the
documentation at the following link: http://processors.wiki.ti.com/index.php/Energy_Trace_for_MSP432.
3.6.5 Usage With Command Line Utility – stune
The Windows-based CCS installation has an interactive command line utility called stune which can be
used for capturing EnergyTrace data to a CSV file. This does not require CCS to be running. However, the
setup does require the target’s connection file (.ccxml), which is created in CCS.

www.ti.com
Functional Description and Operation
17
SPRUI94–January 2017
Submit Documentation Feedback Copyright © 2017, Texas Instruments Incorporated
XDS110 Debug Probe
To use stune, open a command window and change directories to the stune directory in the CCS
installation at: <Install base>\ccs_base\emulation\analysis\bin\stune. Type “stune” and press enter to drop
into the stune command shell.
The first step is to establish connection. Use the connect command with the target connection file in the
following format within stune:
connect -c targetConfig.ccxml xds
EnergyTrace data can be collected either for a fixed duration, or for an indefinite duration with user
intervention to stop trace collection. In fixed duration mode, when trace collection stops, the average,
maximum, and minimum current and total energy consumed is reported. In the indefinite mode, when
trace collection starts, the window is updated with live updates for the current and energy values, until the
user terminates the collection by pressing Ctrl+C.
For example:
To capture 5 seconds of EnergyTrace, enter the following command:
energytrace -D 5000 -o output.csv et
The –D option specifies the time in milliseconds.
The –o option specifies the output filename. The file format is fixed as CSV.
To capture EnergyTrace with user intervention to stop collection, omit the –D option.
energytrace -o output.csv et
The –o option specifies the output filename. The file format is fixed as CSV.
To stop collection, press the Ctrl+C key combination.
3.7 Host SW Interfaces
3.7.1 Serial Communications
A bidirectional UART channel is provided for additional host to target communications (with the probe as a
UART-to-UART bridge and the UARTs mapped on the AUX header). The UART channel is realized on the
host through a USB CDC driver, and enumerated as Virtual Comm Port.
3.7.2 CMSIS-DAP
CMSIS-DAP is a standard interface for creating debug probes capable of debugging ARM Cortex
microcontrollers through the CoreSight debug access port (DAP). CMSIS-DAP support consists of
software that is ported into the firmware of an interface chip, such as the TM4C129 CPU of the XDS110.
This firmware code provides a standardized USB interface that allows the host to make DAP access
requests, and handles converting those requests into the necessary JTAG or SWD protocols.
CMSIS-DAP has been included as part of the XDS110 debug probe. Any debugger able to communicate
with a CMSIS-DAP-enabled debug probe can use the XDS110 directly with no other software required.
Debuggers that include support for CMSIS-DAP include the following: Keil uVision, IAR Workshop, and
OpenOCD.
The USB VID/PID of the XDS110 are 0x0451/0xbef3. Some CMSIS-DAP debuggers may require the user
to provide these IDs to find the XDS110.
3.7.3 TI XDS Utilities
The XDS110 probe supports three utilities that can be useful for managing debug functionality external to
a debug IDE.
3.7.3.1 Rest Control Utility – xds110reset
xds110reset is a command line utility to control the board reset feature of the XDS110. xds110reset was
created to provide reset control, without the need to install the entire XDS software stack.

Functional Description and Operation
www.ti.com
18 SPRUI94–January 2017
Submit Documentation Feedback
Copyright © 2017, Texas Instruments Incorporated
XDS110 Debug Probe
The reset line controller is the board or system reset pin on the debug header. Asserting this pin should
cause a hard reset on the target device, similar to pressing a manual reset button. On the TI 20-pin
header, this is pin 15 (nSRST). On the Cortex-M 10-pin header, this is pin 10 (nRESET). And on the ARM
20-pin header, this is pin 15 (nSRST). This reset is not available on the TI 14-pin header.
xds110reset provides the following features:
• Toggle the board reset with configurable delay.
• Assert or deassert the board reset line.
• Choose which XDS110 to use by serial number
Installation Path:
.../<CCS Install>/ccs_base/common/uscif/xds110
Usage:
xds110reset<command> <...>
Supported commands:
• -a <NAME>, -action <NAME>
Choose an action to perform. NAME may be assert, deassert, or toggle. If not specified, toggle is
executed by default.
• -d <VALUE>, -delay <VALUE>
Set the asserted time for the reset toggle in milliseconds. Has no effect if action is assert or deassert. If
not specified, delay is set to 50 ms by default.
• -s <TEXT>, -serial <TEXT>
Select the XDS110 probe by serial number. TEXT is the serial number to use, up to eight characters. If
not specified, the first XDS110 found is used.
• -h, -help
Show help for these commands, and exit.
Examples:
How to reset the target using an XDS110:
xds110reset
xds110reset connects to the first XDS110 it finds. It then toggles the board reset line, holding it asserted
for 50 ms.
How to toggle the board reset, holding asserted for 3 seconds:
xds110reset --action toggle --delay 3000
The given delay is the time between asserting the reset and releasing it. The --delay option is only used
when the --action option is toggle.
3.7.3.2 Firmware Maintenance Utility - xdsdfu
xdsdfu is a command line utility that provides several features for examining and maintaining the firmware
of the XDS110 debug probe. While the XDS software stack includes an auto-update feature for ensuring
the latest firmware is always flashed, the user may need to manually examine or update the firmware.
xdsdfu also allows the user to view and set the XDS110 probe serial number.
xdsdfu provides the following features:
• Report the XDS110 firmware version and serial number
• Place the XDS110 into flash programming mode (DFU mode)
• Download the bootloader into the XDS110
• Download the firmware into the XDS110
• Set a new serial number into the XDS110
• Reset the XDS110 to restart the firmware

www.ti.com
Functional Description and Operation
19
SPRUI94–January 2017
Submit Documentation Feedback Copyright © 2017, Texas Instruments Incorporated
XDS110 Debug Probe
Installation path:
.../<CCS Install>/ccs_base/common/uscif/xds110
Usage:
xdsdfu <command> <...>
Supported commands:
• -e
Enumerate connected devices, show info, then exit.
• -m
Switch XDS110 into programming mode (DFU mode).
• -b <FILE>
Download the given bootloader file into the device.
• -f <FILE>
Download the given firmware file into the device.
• -s <TEXT>
Set the XDS110 serial number to given text, any eight character string (no spaces). This option
replaces the entire serial number.
• -r
Reset the XDS110 on completion of another command.
• -? or -h
Show help for these and additional commands.
Examples:
How to examine the firmware in all connected XDS110 probes:
xdsdfu -e
xdsdfu examines all connected XDS110 probes and devices in DFU mode, and reports the details of each
device. Sample output is shown in Figure 11.
Figure 11. xdsdfu Screenshot

Functional Description and Operation
www.ti.com
20 SPRUI94–January 2017
Submit Documentation Feedback
Copyright © 2017, Texas Instruments Incorporated
XDS110 Debug Probe
How to program new firmware into the XDS110 probe:
xdsdfu -m
xdsdfu -f firmware.bin -r
The -m command must be executed separately. When -m is executed, the XDS110 reconfigures its USB
interface to enable the DFU mode. It then reconnects as a different USB device, and the OS needs a
moment to recognize it. The -r command tells the XDS110 to reboot after programming the firmware.
How to program a new bootloader and firmware into the XDS110 probe:
xdsdfu -m
xdsdfu -b bootloader.bin -r
xdsdfu -m
xdsdfu -f firmware.bin -r
The -m commands must be executed separately, but the second -m may not be necessary if the XDS110
probe flash was blank.
How to change the serial number of the XDS110 probe:
xdsdfu -m
xdsdfu -s 00000000 -r
3.7.3.3 Connection Diagnostic Utility – dbgjtag
dbgjtag is a command line utility that provides multiple commands for testing and operating the features of
Texas Instruments debug probes. dbgjtag is a tool for diagnosing problems with the debug connection,
and dbgjtag allows the user to exercise some control over features of the debug probe.
dbgjtag provides the following features for XDS110 users:
• Report the installed XDS emupack software version
• Test the reliability of the debug connection (JTAG, cJTAG, and SWD)
• Measure the scan path (JTAG and cJTAG)
• Reset the probe and target into test-logic-reset state
• Reset the target board through the system reset pin (nSRST)
• Configure, read, and write the XDS110 GPIOs
Installation path:
...<CCS Install>/ccs_base/common/uscif
Usage:
dbgjtag <command>, <variable=value>
Supported commands for XDS110:
• -f @<debug probe>
Select which debug probe and scan mode to use. For XDS110 use: @xds110, @xds110cjtag, or
@xds110swd for JTAG, cJTAG, or SWD modes.
• -f <board file>
Select which CCS board configuration file to use.
• -r
Reset the debug probe and its target through the nTRST pin. If used with the commands below, -r is
executed first.
• -v
Enable verbose output.
• -S integrity
Test the DR/IR scan paths with fixed data (JTAG and cJTAG), or test the SWD connection by reading
the target IDCODE (SWD).
Other manuals for XDS110
1
Table of contents
Other Texas Instruments Computer Accessories manuals

Texas Instruments
Texas Instruments SWRU197F User manual

Texas Instruments
Texas Instruments PHP1800 User manual

Texas Instruments
Texas Instruments TMS320C6 Series User manual

Texas Instruments
Texas Instruments SWRU197E User manual

Texas Instruments
Texas Instruments PHP1500 User manual

Texas Instruments
Texas Instruments MSP Series User manual
Popular Computer Accessories manuals by other brands

Coldzero
Coldzero CZ-900D-40 installation manual

Blue Orb
Blue Orb orbiTouch manual

Sony
Sony LFA-PC1 operating instructions

AbleNet
AbleNet TrackerPro quick start guide

Addonics Technologies
Addonics Technologies ADCFASTHDD installation guide

Addonics Technologies
Addonics Technologies ADSAHDCF installation guide