Filter
Top Products
R0E530640MCU00 User’s Manual 7. Hardware Specifications
REJ10J1733-0100 Rev.1.00 Apr. 01, 2008
Page 224 of 229
IMPORTANT
Notes on Power Supply to the User System:
z Pins Vcc1 and Vcc2 are connected to the user system to observe the voltage. Therefore, the power is not
supplied to the user system from the emulator. Design your system so that the user system is powered
separately.
z The voltage of the user system should be as follows.
2.7 V ≤ Vcc1 = Vcc2 ≤ 5.5 V
Notes on Internal Flash ROM of the MCU:
z Because the number of write/erase cycles of the internal flash ROM of the MCU is limited, it must be replaced
at the end of its service-life.
z If the following errors occur frequently when downloading a program, replace the MCU board.
(1) Flash ROM erase error occurred ERROR (16258)
(2) Flash ROM verify error occurred ERROR (16259)
Notes on Debugging in CPU Rewrite Mode:
z When you debug an M16C/60 Series MCU 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 System tab of the Configuration properties
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 CPU rewrite mode and erase suspend mode, do not stop the program. And do not single step an instruction
shifting to CPU rewrite mode or erase suspend mode. The emulator will be uncontrollable in CPU rewrite mode
and erase suspend mode.
z To reference data after executing CPU rewrite, stop the program at other then a rewrite control program area
and use the Memory window etc.
z As the following interrupt vectors are used by the emulator system, the read data is different from expected
value.
- Single-step (FFFECh--FFFEFh)
z As the user boot function cannot be debugged, do not enter the user boot mode.
Note on Accessing Addresses 00000h and 00001h:
z With the M16C/60 Series MCUs, when a maskable interrupt is generated, the interrupt data (interrupt number
and interrupt request level) stored in addresses 00000h and 00001h are read out. Also, the interrupt request bit is
cleared when address 00000h or 00001h is read out. Consequently, when the address 00000h or 00001h readout
instruction is executed or when address 00000h or 00001h is read out in the cause of a program runaway, a
malfunction occurs in that the interrupt is not executed despite the interrupt request, because the request bit of
the highest priority interrupt factor enabled is cleared.
For this malfunction, when the reading out to address 00000h or 00001h is generated excluding the interrupt, an
expansion monitor window will appear. At that time, check the user program. There is a possibility of wrong
access.