M30290T2-CPE-HP Renesas Electronics America, M30290T2-CPE-HP Datasheet - Page 70

• Manufacturer Part Number: M30290T2-CPE-HP
• Description: EMULATOR COMPACT FOR M16C/TINY
• Manufacturer: Renesas Electronics America
• Type: In Circuit Debuggerr

Specifications of M30290T2-CPE-HP

• Contents: Compact Emulator, IDE, Assembler and Linker
• For Use With/related Products: M16C/Tiny
• For Use With: M30290T2-CPE - EMULATOR COMPACT M16C/26A/28/29
• Lead Free Status / RoHS Status: Contains lead / RoHS non-compliant

M30290T2-CPE 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.
REJ10J0494-0200 Rev.2.00 July 16, 2005
Note on Differences between the Actual MCU and Emulator:
Note on RESET* Input:
Note on NMI* Input:
Notes on Maskable Interrupts:
Note on DMA Transfer:
Operations of the emulator system differ from those of actual MCUs as listed below.
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).
A low input to pin NMI* 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).
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 emulator. Therefore, timers and other components do not
stop running. If a maskable interrupt is requested when the user program is not being executed (including
Internal I/O access 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.
With this product, the program is stopped with a loop program to a specific address. Therefore, if a DMA
request is generated while the program is stopped, DMA transfer is executed. However, make note that DMA
transfer while the program is stopped may not be performed correctly. Also note that the below registers have
been changed to generate DMA transfer as explained here even when the program is stopped.
(1) Reset condition
(2) Initial values of internal resource data of an MCU at power-on
(3) Interrupt stack pointer (ISP) after a reset is released
(4) Capacities of the internal memories (ROM and RAM)
(5) Oscillator circuit
(6) X
(7) A/D conversion
(8) Operation after releasing the reset
(1) DMA0 transfer counter: TCR0
(2) DMA1 transfer counter: TCR1
Set the time for starting up (0.2 Vcc to 0.8 Vcc) 1 μs or less.
The evaluation MCU of this product has RAM of 12 KB (00400h--033FFh) and flash ROM of 4 KB
(0F000h--0FFFFh) and 128 KB (E0000h--FFFFFh).
In the oscillator circuit where an oscillator is connected between pins X
occur because a converter board is used between the evaluation MCU and the user system. For notes on
when using an oscillator circuit on the user system, refer to "2.9.2 Selecting Clock Supply" (page 36). It is
same for pins X
When resetting the MCU, it is necessary to input a clock to the pin X
The characteristics of the A/D converter differ from those of actual MCU because there are a converter
board and other devices between the evaluation MCU and the user system.
After releasing the reset, for about up to 350 cycles, a program to control the emulator will be executed.
Note that this will have an affect on a user program execution time and tracing result.
IN
input when resetting the MCU
CIN
and X
COUT
.
IMPORTANT
IN
.
IN
and X
4. Hardware Specifications
OUT
, oscillation does not
Page 68 of 86