Renesas Emulator System E8 Betriebsanweisung PDF herunterladen (Seite 31)

CSE8E10-2

Hardware-specific debugging

For information about the various methods for setting breakpoints, the facilities for

monitoring breakpoints, and the various breakpoint consumers, see the chapter Using

breakpoints, page 18 in this guide.

AVAILABLE BREAKPOINTS

Using the C-SPY drivers for hardware debugger systems you can set code breakpoints

and for some drivers you can also set data breakpoints. Code breakpoints are

implemented as software breakpoints or hardware breakpoints. Hardware breakpoints

are also referred to as execution address breakpoints. Data breakpoints are referred to as

break conditions.

The type of breakpoints you can set in C-SPY depends on the target system you are

using.

The table below summarizes the characteristics of breakpoints for the E8/E8a Emulator:

For the E10A-USB Emulator, these are the available breakpoints:

1 For the E10A-USB Emulator, data breakpoints are referred to as break conditions. See The

Break Condition dialog box, page 22 for more information.

Determining which breakpoint type is set

In the IDE, there are two ways to see which type of breakpoint is set. One way is to open

the Breakpoint Usage dialog box. An other way is to move your mouse over the

breakpoint symbol in the editor window. Then a tooltip appears and informs you of the

breakpoint type.

Breakpoint type M16C/R8C M32C R32C H8

Hardware breakpoints x x x --

Software breakpoints x x x x

Data breakpoints -- -- -- --

Table 7: Available breakpoints for the E8/E8a Emulator

Breakpoint type H8

Hardware breakpoints --

Software breakpoints x

Data breakpoints x

Table 8: Available breakpoints for the E10A-USB Emulator

1 2 ... 26 27 28 29 30 31 32 33 34 35 36 ... 40 41

Keine Kommentare

Renesas Emulator System E8 Betriebsanweisung Seite 31