beautypg.com

Notes on debugging in cpu rewrite mode, Note on software break, Important – Renesas Emulation Probe for M32C/87 Group M30870T-EPB User Manual

Page 92

background image

M30870T-EPB User’s Manual

4. Hardware Specifications

REJ10J0482-0300 Rev.3.00 February 16, 2006

IMPORTANT

Notes on Debugging in CPU Rewrite Mode:

To debug a program in CPU rewrite mode, select the check box "Debug the program using the CPU Rewrite

Mode" in the MCU tab of the Init dialog box. When you do not debug a program in CPU rewrite mode, clear
the check box.

When you debug a program in CPU rewrite mode, the block 0 area (FFF000h--FFFFFFh) must not be rewritten.

Otherwise, the emulator will be out of control.

When debugging in CPU rewrite mode is enabled, you cannot use the following functions.

(1) Setting an address match breakpoint
(2) Setting a software breakpoint to the internal ROM area
(3) Executing COME to the internal ROM area

Do not use the following functions to the rewrite control program area (from setting CPU rewrite mode select

bit to releasing it). If any of these are used, malfunctions may occur (e.g. The emulator cannot shift to CPU
rewrite mode or contents of ROM cannot be read out properly.).

(1) Single stepping
(2) Setting a software breakpoint
(3) Setting a hardware breakpoint
(4) Executing COME

When CPU rewrite program is allocated to the expansion emulation memory, the program may run out of

control. For the CPU rewrite program, use an internal RAM area or external resource on the use system. These
precautions only need to be observed when using an emulator, and do not apply for the actual MCU.

Note on Software Break:

A software break generates a break interruption by forcibly inserting a BRK instruction "08h" instead of an

instruction code. Therefore, when referencing the result of a trace in bus mode, "08h" is displayed for the
instruction fetch address where a software break is set.

Notes on Service-Life of the MCU's Internal Flash ROM:

With the M30870T-EPB, programs are downloaded to the MCU's flash ROM when debugging in single-chip

mode or memory expansion mode. Because the number of write/erase cycles of this ROM is limited, the ROM
must be replaced when at the end of its service-life.

If the following errors occur frequently during program download, replace the emulation probe or request for

repair.

(1) Flash ROM erase error occurred ERROR (16258)

(2) Flash ROM verify error occurred ERROR (16259)

To purchase the product for replacement or request for repair, contact your local distributor.

Page 92 of 104