
Rev. 2.0, 01/01, page 205 of 216
8. When the [Physical] option is selected in the [Memory area] group box in the [General] page
of the [Configuration] dialog box, a BREAKPOINT is set to a physical address. A
BREAKPOINT is set after disabling the SH7729 or SH7709A MMU upon program execution.
After setting, the MMU is returned to the original state. When a break occurs at the
corresponding virtual address, the cause of termination displayed in the status bar and the
[System Status] window is ILLEGAL INSTRUCTION, not BREAKPOINT.
9. When the [Virtual] option is selected in the [Memory area] group box in the [General] page of
the [Configuration] dialog box, a BREAKPOINT is set to a virtual address. A BREAKPOINT
is set after enabling the SH7729 or SH7709A MMU upon program execution. After setting,
the MMU is returned to the original state. When an ASID value is specified, the breakpoint is
set to the virtual address corresponding to the ASID value. The emulator sets the breakpoint
after rewriting the ASID value to the specified value, and returns the ASID value to its original
value after setting. When no ASID value is specified, the breakpoint is set to a virtual address
corresponding to the ASID value at command input.
10.An address (physical address) to which a breakpoint is set is determined when the breakpoint
is set. Accordingly, even if the VP_MAP table is modified after breakpoint setting, the
breakpoint address remains unchanged. When a breakpoint is satisfied with the modified
address in the VP_MAP table, the cause of termination displayed in the status bar and the
[System Status] window is ILLEGAL INSTRUCTION, not BREAKPOINT.
11.When a breakpoint is set to the cacheable area, the cache block containing the breakpoint
address is filled immediately before and after user program execution.
12.Note on DSP repeat loop:
A breakpoint is equal to a branch instruction. In some DSP repeat loops, branch instructions
cannot be set. For these cases, do not set breakpoints. Refer to the hardware manual for
details.
6.5.6
Notes on Setting the [Break Condition] Dialog Box
1. Break Condition 2 is disabled during step execution.
2. Break Condition 2 is disabled when an instruction to which a BREAKPOINT has been set is
executed. Accordingly, do not set a BREAKPOINT to an instruction which satisfies Break
Condition 2.
3. When a Break Condition is satisfied, emulation may stop after two or more instructions have
been executed.
4. If a PC break address condition is set to the slot instruction after a delayed branch instruction,
user program execution cannot be terminated before the slot instruction execution; execution
stops before the branch destination instruction.
5. Note on DSP repeat loop:
A breakpoint is equal to a branch instruction. In some DSP repeat loops, branch instructions
cannot be set. For these cases, do not set breakpoints. Refer to the hardware manual for
details.