Functional Description and Operation
14
SPRUI94 – January 2017
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. Ener: Energy profiling with program counter correlation. This mode is supported for the
MSP432 device family only.
3. Ener+: 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
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
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.
indicates the specific fields.
