Notes On Debugging In Cpu Rewrite Mode; Note On The Version Of The M3T-Pd30F - Renesas M30290T-EPB User Manual

M30290T-EPB User's Manual

Notes on Debugging in CPU Rewrite Mode:

When you debug M16C/26A, 28, 29 Group MCUs in CPU rewrite mode, do not change the block 0 area
(FF000h--FFFFFh) of the flash ROM. Otherwise, the emulator will be uncontrollable.
If you check "Debug the program using CPU Rewrite Mode" in the MCU tab of the Init dialog box of
the emulator debugger, you cannot use the following functions.
(1) Setting software breakpoints in an internal ROM area
(2) Executing COME in an internal ROM area
Do not stop the program in the CPU rewrite mode or erase suspend mode. And do not single step the
instruction shifting to these modes. The emulator is uncontrollable in these modes.
To reference data after executing CPU rewrite, stop the program at a point which is not a rewrite control
program area and use a memory window etc.
As the following interrupt vectors are used by the emulator system, the read data is different from
expected value.
(1) BRK instruction (FFFE4h--FFFE7h)
(2) Address match (FFFE8h--FFFEBh)
(3) Single-step (FFFECh--FFFEFh)
(4) DBC (FFFF4h--FFFF7h)

Note on the Version of the M3T-PD30F:

Be sure to use this product with the emulator debugger M3T-PD30F V2.20 or later.
IMPORTANT
( 16 / 58 )