Differences Between The Actual Mcu And Emulator - Renesas R0E521000EPB00 User Manual

Emulation probe for r8c/tiny series
Table of Contents

Advertisement

R0E521000EPB00 User's Manual

4.2 Differences between the Actual MCU and Emulator

Differences between the actual MCU and emulator are shown below. When debugging the MCU using this product, be careful
about the following precautions.
Notes on Internal Memory (ROM and RAM):
The evaluation MCU mounted on this product has the emulation memory for RAM area of 8 KB (00300h--
012FFh, 03000h--03FFFh) and flash ROM area of 4 KB (02000h--02FFFh) and 112 KB (04000h--1FFFFh).
For this reason, the nonexistent ROM or RAM area of the target MCU may be accessed.
With this product, the flash ROM area of target MCU is cleared at "04h (NOP instruction)" when starting up the
emulator. If you want the MCU's internal flash ROM to be cleared when starting up the debugger, (when
cleared, the content of the flash ROM is initialized to 0FFh.), select the flash ROM block you want to clear in
the Flash Clear tab of the MCU setting dialog box.
Note on Access Prohibited Area:
You cannot use internally reserved areas. Because an evaluation MCU is operated in the special mode for the
emulator, a function which does not support the target MCU may run.
Notes on RESET# Input:
A low input to pin RESET# from the user system is accepted only when a user program is being executed
(when the RUN status LED on the emulator's upper panel is lit).
The time for starting up (0.2 VCC to 0.8 VCC) and falling edge (0.8 VCC to 0.2 VCC) for RESET# pin should
be set to 1μs or less.
Note on Power-on Reset Function:
This product emulates inputs to the RESET# pin for the purpose of emulator function control. For this reason,
the power-on reset function cannot be used.
Notes on Maskable Interrupts:
Even if a user program is not being executed (including when run-time debugging is being performed), the
evaluation MCU keeps running so as to control the emulation probe. Therefore, timers and other components do
not stop running. If a maskable interrupt is requested when the user program is not being executed (including
when run-time debugging is being performed), the maskable interrupt request cannot be accepted, because the
emulator disables interrupts. The interrupt request is accepted immediately after the user program execution is
started.
Take note that when the user program is not being executed (including when run-time debugging is being
performed), a peripheral I/O interruption is not accepted.
Notes on Oscillator Circuit:
Make note of the fact that in the oscillator circuit where a resonator is connected between pins P4_6/XIN and
P4_7XOUT, oscillation does not occur because a converter board and other devices are used between the
evaluation MCU and the user system. It is same for a sub-clock oscillator (P4_3/XCIN and P4_4/XCOUT).
For notes on when using the oscillator circuit on the user system, refer to "2.10.3 Selecting Clock Supply" (page
40).
Note on the pin P4_4/XCOUT:
Make note that the pin P4_4/XCOUT of the evaluation MCU used for this product has no XCOUT output
function.
REJ10J0844-0400 Rev.4.00 October 16, 2007
Page 67 of 88
IMPORTANT
4. Hardware Specifications

Advertisement

Table of Contents
loading

Table of Contents