E2/E2 Lite
R20UT4582EJ0100 Rev.1.00
Page 25 of 30
Jul.16.19
(4) Removal of software breakpoints when the emulator debugger is to be disconnected
When the emulator debugger is to be disconnected, remove all software breakpoints that have been set.
At this time, reset the CPU since the emulator debugger is certain to reprogram the flash memory.
3.3.5
Note on Peripheral I/O Registers Occupied by the Debugger
(1) Peripheral I/O registers occupied
by the debugger
The emulator debugger occupies the following peripheral I/O registers during debugging. Do not change
the values of these registers, since continued debugging might not be possible after having done so.
Debug stop control register (DBGSTOPCR)
Micro trace buffer (MTB) (SFR area)
System control OCD control register (SYOCDCR)
3.3.6
Note on Using the Trace Function
(1) MTB tracing
When the MTB trace function is in use, the trace recording area is the size of recorded tracing that has
been selected for the emulator debugger from the address where the on-chip SRAM starts. When the on-
chip SRAM is in use by a user program, do not use the trace recording area. For details on the address
where the on-chip SRAM starts, refer to the hardware manual for the given MCU.
If the size of the trace recording area for the emulator debugger is changed, the startup routine must also
be changed.
3.3.7
Notes on Low-Power Modes
(1) Debugging in SSTBY or SNOOZE mode
In SSTBY or SNOOZE mode, the emulator debugger does not have access to the system bus of the
MCU. While the user program is being executed or during mode transitions of the MCU, setting and
viewing of the memory or peripheral I/O registers and setting and changing breakpoints are not possible.
(2) Forcedly stopping a program in SSTBY or SNOOZE mode
When a program is forcedly stopped in SSTBY or SNOOZE mode, proceed with one of the following
operations. Each operation leads to release from SSTBY or SNOOZE mode.
Using [Reset
] of the emulator debugger makes the MCU stop the user program and go to the
position indicated by the reset vector.
Using [Suspend
] of the emulator debugger stops the MCU at the next instruction after the WFE
instruction which led to the mode transition. When [Suspend
] is to be used, for [Connection] on
the [Connection Settings] tabbed page of the emulator debugger, select [Yes] for [Low Power
Handling] (the operation is explained for the case when the e
2
studio is in use).
Figure 3.11 Setting of [Low Power Handling]
