Справочник Пользователя для Renesas R0E530640MCU00
R0E530640MCU00 User’s Manual
5. Debugging Functions
REJ10J1733-0100 Rev.1.00 Apr. 01, 2008
Page 100 of 229
Page 100 of 229
5.6 Using Software Breakpoints
5.6.1 Using Software Breakpoints
A software break causes the user program to stop running by rewriting the instruction code at a specified address with a BRK
instruction to generate a BRK interrupt. In that sense, this is a pre-execution break function.
4096 breakpoints can be set.
If multiple software breakpoints are set, the program breaks at any one of those breakpoints reached.
(1) When stopped at a software breakpoint
When the program you have created is run and the address you have set as a software breakpoint is reached, a message
“Software Break” is displayed on the Debug sheet of the Output window, with the program made to stop there. At this time,
the Editor or the Disassembly window is updated, and the position at which the program has stopped is marked with an arrow
“Software Break” is displayed on the Debug sheet of the Output window, with the program made to stop there. At this time,
the Editor or the Disassembly window is updated, and the position at which the program has stopped is marked with an arrow
[
] in the S/W Breakpoints column.
CAUTION
When a break occurs, the program stops immediately before executing the line or instruction at which a software breakpoint is
set. If Go or Step is selected after the program has stopped at that software breakpoint, the program restarts from the line
marked with an arrow.
5.6.2 Adding/Removing Software Breakpoints
Follow one of the following methods to add or remove software breakpoints.
- From the Editor or the Disassembly window
- From the Breakpoints dialog box (only removing)
- From the command line
- From the Breakpoints dialog box (only removing)
- From the command line