MB91350A Series
DS07-16503-5E
27
[Note on Debugger]
Single-Step Execution of the RETI Command
If single-step execution is used in an environment where an interrupt occurs frequently, the corresponding
interrupt handling routine will be executed repeatedly to the exclusion of other processing. This will prevent the
main routine and the handlers for low priority level interrupts from being executed (For example, if the time-base
timer interrupt is enabled, stepping over the RETI instruction will always break on the first line of the time-base
timer interrupt handler) .
Disable the corresponding interrupt when the corresponding interrupt handling routine no longer needs debug-
ging.
Break Function
If the range of addresses that cause a hardware break (including event breaks) is set to the address of the
current system stack pointer or to an area that contains the stack pointer, execution will break after each
instruction regardless of whether the user program actually contains data access instructions.
To prevent this, do not set (word) access to the area containing the address of the system stack pointer as the
target of the hardware break (including event breaks).
Internal ROM area
Do not set DMAC transfer destination to an address in the internal ROM area.
Simultaneous Occurrence of a Software Break (INTE instruction) and a User Interrupt/NMI
When a software break and a user interrupt/NMI occur simultaneously, the emulator debugger may react as
follows.
The debugger stops pointing to a location other than a programmed breakpoint.
The program does not resume execution correctly after breaking.
If this symptom occurs, use a hardware break in place of the software break. When using a monitor debugger,
do not set a break at the relevant location.
A malfunction may occur if the stack pointer is in an area that is configured for DSU operand break. Do not
set a data event breaks that apply to accesses to an area that contains the address of the system stack pointer.