User`s manual

Chapter 1. Precautions for Safety
( 17 / 74 )
IMPORTANT
Notes on Debugging in CPU Rewrite Mode:
z When you debug the M16C/6N Group M16C/6NK, M16C/6NL, M16C/6NM, M16C/6NN, M16C/6N4,
M16C/6N5 MCUs in CPU rewrite mode, do not change the block 0 area (FF000h--FFFFFh) of the flash
memory. Otherwise, the emulator will be uncontrollable.
z 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
z In the rewrite control program area (from setting CPU rewrite mode to releasing it), do not use the
following functions.
(1) Single-stepping
(2) Setting software breakpoints
(3) Setting hardware breakpoints
z 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.
z 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:
z Be sure to use this product with the emulator debugger M3T-PD30F V2.20 or later.