
MB91350A Series
21
[Note on debugger]
Step execution of RETI command
If an interrupt occurs frequently during single-stepping, the corresponding interrupt handling routine is executed
repeatedly. This will prevent the main routine and low-interrupt-level programs from being executed. (Whenever
RETI is single-stepped when interrupts by the timebase timer have been enabled, for example, the timebase
timer routine causes a break at the beginning.)
Disable the corresponding interrupt when the corresponding interrupt handling routine no longer needs debug-
ging.
Break function
If the address at which to cause a hardware break (including a event break) is set to the address currently
contained in the system stack pointer or in the area containing the stack pointer, the user program causes a
break after execution of one instruction.
To prevent this, do not set (word) access to the area containing the address in the system stack pointer as the
target of a hardware break (including an event break).
Internal ROM area
Do not set an area of internal ROM as a DMAC transfer destination.
Simultaneous occurrences of a software break (INTE instruction) and a user interrupt/NMI
When an INTE instruction and a user interrupt/NMI are accepted simultaneously, the emulator debugger reacts
as follows.
The emulator debugger stops while indicating a location in the user program, which is not a user-specified
breakpoint. (It stops with the beginning of the user interrupt/NMI handling routine indicated.)
The user program cannot be re-executed correctly.
To prevent this problem, follow the instructions below.
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 the programmed breakpoints.
The halted program is not re-executed correctly.
If this symptom occurs, use a hardware break in place of a hardware break. When using a monitor debugger,
do not set a break at the relevant location.
A stack pointer placed in an area set for a DSU operand break can cause a malfunction. Do not apply a data
event break to access to the area containing the address of a system stack pointer.