EEM Building Blocks
1021
SLAU367P – October 2012 – Revised April 2020
Copyright © 2012–2020, Texas Instruments Incorporated
Embedded Emulation Module (EEM)
38.2.5 Ener+ Technology
The EEM implements circuitry to support Ener+ technology. The Ener+ technology
allows you to observe information about the internal states of the microcontroller. These states include the
CPU Program Counter (PC), the ON or OFF status of the peripherals and the system clocks (regardless of
the clock source), and the low-power mode currently in use. These states can always be read by a debug
tool, even when the microcontroller sleeps in LPMx.5 modes. See
for more information about integration into the IDE. See
optimizations: ULP advisor software and EnergyTrace™ technology
for examples of use.
38.2.6 Clock Control
The EEM provides device-dependent flexible clock control. This is useful in applications where a running
clock is needed for peripherals after the CPU is stopped (for example, to allow a UART module to
complete its transfer of a character or to allow a timer to continue generating a PWM signal).
The clock control is flexible and supports both modules that need a running clock and modules that must
be stopped when the CPU is stopped due to a breakpoint.
38.2.7 Debug Modes
The TEST/SBWTCK pin is used to enable the connection of external development tools with the EEM
through Spy-Bi-Wire or JTAG debug protocols. The connection is usually enabled when the
TEST/SBWTCK is high. When the connection is enabled, the device enters a debug mode. In the debug
mode, the entry and wakeup times to and from low-power modes may be different compared to normal
operation (application mode).
NOTE:
Pay careful attention to the real-time behavior when using low-power modes with the device
connected to a development tool.
There are two different debug modes available: the default debug mode and a ultra-low power debug
mode. See
Code Composer Studio IDE for MSP430 MCUs
for more information how to select the mode in
the IDE.
Features and restrictions of the default debug mode are:
•
It is possible to change breakpoint settings while the program is executed
•
LPMx.5 is not supported
•
Wakeup from low-power modes are faster than in application mode
•
FRAM is forced on. It cannot be switched off using the FRAM Power Control bits
Features and restrictions of the ultra-low power debug mode are:
•
It is not possible to change breakpoint settings while the program is exectued
•
LPMx.5 is supported
•
Entry and wakeup times to and from low power modes may be longer than in application mode (for
details see below)
•
FRAM can be switched off using the FRAM Power Control bits.
In ultra-low power debug mode, the LPM entry and exit may be delayed. Low-power mode entry and
wakeup from low-power modes is only possible while the debug protocol is in a certain state. Thus, the
delay depends on the speed of the selected debug protocol. With Spy-Bi-Wire the delay is longer than
when using JTAG. Also, the reaction on a DMA trigger or on a SMCLK or MCLK request may be delayed.
38.3 EEM Configurations
gives an overview of the EEM configurations. The implemented configuration is device-
dependent, and details can be found in the device-specific data sheet and these documents:
Advanced debugging using the enhanced emulation module (EEM) with CCS
IAR Embedded Workbench