Epson S5U1C17001C, Manual

Page: 503 / 742

S5U1C17001C ManUal
EPSOn
10-53
(C COMPilEr PaCkagE fOr S1C17 faMily) (Ver. 1.5.0)
10 DEBUggEr
10
Debugger
Software PC breakpoints can also be set from the [Source] window.
The lines where you can set software PC breakpoints are marked by a bar "–" at the beginning of the lines.
Move the cursor near the beginning of a line where you wish to set a breakpoint. The cursor will change shape
to a circle (white ). Click the mouse button there. The "–" mark at the beginning of the line will change to
n
(in red by default), indicating that a software PC breakpoint has been set. Clicking the button again clears the
breakpoint you have set.
Otherwise, right-clicking at the "–" position will display a popup menu, so you can choose [Set Breakpoint]
from the menu to set a software PC breakpoint. You can also choose [Set Temporary Breakpoint] from the
menu and can set a temporary software PC breakpoint. When you have set a temporary software PC breakpoint,
the color of the
n
mark that indicates the breakpoint becomes orange (by default).
For how to use the functions of the [Source] window, see Section 10.4.2, "[Source] Window".
notes : • Software PC breaks are implemented by an embedded
brk
instruction. Therefore, they cannot
be used for the target board ROM in which instructions cannot be embedded. In such case,
use hardware PC breaks instead.
• When you set a software PC break at the address of an
ext
-based extended instruction or
delayed branch instruction, note that you cannot set a breakpoint at other than the start address.
ext
xxxx ... Can be set.
jr*.d
xxxx ... Can be set.
ext
xxxx ... Cannot be set. Delayed instruction ... Cannot be set.
Extended instruction ... Cannot be set.
• The debugger refers to the memory map information set by loading a parameter file using
the
c17 rpf
command as it checks each address to determine whether a software PC
breakpoint can be set. Unless the
c17 rpf
command has been executed, the debugger does
not perform error processing that pertains to the target system.
Hardware PC breaks (
hbreak
and
thbreak
commands)
The on-chip debugger of the S1C17 Core is used to set the type of break. Breaks can also be simulated in
simulator mode, as well as in other modes. When the executed PC address matches the address set by a
command, the program is made to break before executing the instruction at that address. The maximum number
of addresses that can be set as hardware PC breakpoints depends on the model. For more information, refer to
the technical manual for the model in question.
Like software PC breaks, there are two types of hardware PC breaks: normal and temporary.
hbreak
command: This command sets a normal hardware PC breakpoint.
Example: To set a hardware PC breakpoint at line 7 in
main.c
(gdb) hbreak main.c:7
Hardware assisted breakpoint 1 at 0xc0001c: file main.c, line 7.
thbreak
command: This command sets a temporary hardware PC breakpoint.
Example: To set a temporary hardware PC breakpoint at address 0xc0001e
(gdb)
thbreak
*0xc0001e
Hardware assisted breakpoint 2 at 0xc0001e: file main.c, line 10.
When a hardware PC break occurs, the debugger waits for command input after displaying the following
message:
(gdb) continue
Continuing.
Breakpoint 1, main () at main.c:7
Breakpoints can be set by specifying an address, source line number, or function/label name the same way as
for software PC breakpoints.
Hardware PC breakpoints can also be set from the [Source] window.
The lines where you can set hardware PC breakpoints are marked by a bar "–" at the beginning of the lines.