Datasheet

www.ti.com

EEM Introduction

28.1 EEM Introduction

Every MSP430 flash-based microcontroller implements an embedded emulation module (EEM). It is

accessed and controlled through JTAG. Each implementation is device dependent and is described in

section 1.3 EEM Configurations and the device-specific data sheet.

In general, the following features are available:

• Non-intrusive 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/breakpoints on memory address bus (MAB) or

memory data bus (MDB)

• Up to two (device dependent) hardware triggers/breakpoints on CPU register write accesses

• MAB, MDB ,and CPU register access triggers can be combined to form up to eight (device dependent)

complex triggers/breakpoints

• 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

Figure 28-1 shows a simplified block diagram of the largest currently available 2xx EEM implementation.

For more details on how the features of the EEM can be used together with the IAR Embedded

Workbench™ debugger see the application report Advanced Debugging Using the Enhanced Emulation

Module (SLAA263) at www.msp430.com. Code Composer Essentials (CCE) and most other debuggers

supporting MSP430 have the same or a similar feature set. For details see the user’s guide of the

applicable debugger.

639

SLAU144J–December 2004–Revised July 2013 Embedded Emulation Module (EEM)

Submit Documentation Feedback