Embedded Emulation Module (EEM) Introduction
1018
SLAU367P – October 2012 – Revised April 2020
Copyright © 2012–2020, Texas Instruments Incorporated
Embedded Emulation Module (EEM)
38.1 Embedded Emulation Module (EEM) Introduction
Every MSP430 microcontroller implements an EEM. It is accessed and controlled through either 4-wire
JTAG mode or Spy-Bi-Wire mode. Each implementation is device-dependent and is described in
, the EEM Configurations section, and the device-specific data sheet.
In general, the following features are available:
•
Nonintrusive code execution with real-time breakpoint control
•
Single-step, step-into, and step-over functionality
•
Full support of all low-power modes
•
Support for all system frequencies, for all clock sources
•
Up to eight (device-dependent) hardware triggers or breakpoints on memory address bus (MAB) or
memory data bus (MDB)
•
Up to two (device-dependent) hardware triggers or breakpoints on CPU register write accesses
•
MAB, MDB, and CPU register access triggers can be combined to form up to ten (device-dependent)
complex triggers or breakpoints
•
Up to two (device-dependent) cycle counters
•
Trigger sequencing (device-dependent)
•
Storage of internal bus and control signals using an integrated trace buffer (device-dependent)
•
Clock control for timers, communication peripherals, and other modules on a global device level or on
a per-module basis during an emulation stop
•
Ener+ Technology
shows a simplified block diagram of the largest currently-available EEM implementation.
For more details on how the features of the EEM can be used together with the IAR Embedded
Workbench™ debugger or with Code Composer Studio (CCS), see
enhanced emulation module (EEM) with CCS
. Most other debuggers supporting the MSP430 devices
have the same or a similar feature set. For details, see the user's guide of the applicable debugger.