Table of Contents
Advertisement
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.
Note on Differences between the Actual MCU and Emulator:
Operations of the emulator system differ from those of actual MCUs as listed below.
(1) Reset condition
Set the time for starting up (0.2 Vcc to 0.8 Vcc) 1 μs or less.
(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)
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).
(5) Oscillator circuit
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
(6) X
input when resetting the MCU
IN
When resetting the MCU, it is necessary to input a clock to the pin X
(7) A/D conversion
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.
(8) Operation after releasing the reset
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.
Note 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).
Note on NMI* Input:
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).
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 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.
Note on DMA Transfer:
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) DMA0 transfer counter: TCR0
(2) DMA1 transfer counter: TCR1
REJ10J0494-0200 Rev.2.00 July 16, 2005
IMPORTANT
and X
.
CIN
COUT
4. Hardware Specifications
and X
, oscillation does not
IN
OUT
.
IN
Page 68 of 86
Advertisement
Table of Contents
