
E8a Emulator Section 6 Notes on Using the E8a Emulator
10. Memory access during emulation execution
When referring to or modifying the memory contents, the user program is temporarily halted. For this reason, a
real-time emulation cannot be performed. When a real-time emulation is necessary during a program execution,
disable the automatic update in the watch window or fix the display in the memory window before running the
program so that memory accesses do not occur during an execution.
11. Setting of address match break during user program execution
When adding or cancelling the address match break, the user program is temporarily halted. For this reason, a real-
time emulation cannot be performed.
12. When the E8a emulator does not supply power to the user system, it consumes the power voltage of the user
system from several mA to more than 10 mA. This is because the user power supply drives 74LVC125,
74LVC1T45 and 74LVC2T45 to make the communication signal level match the user system power supply
voltage.
13. When debugging, the Flash memory is frequently rewritten by the E8a emulator. Therefore, do not use an MCU
that has been used for debugging in products. Also, as the E8a emulator program is written to the MCU while
debugging, do not save the contents of the MCU Flash memory which were used for debugging nor use them as
the ROM data for products.
14. NMI interrupt
If NMI interrupts are used, be sure to take the necessary precautions before executing the user program like
disabling the automatic update in the watch window or fix the display in the memory window before running the
program so that memory accesses do not occur during an execution. If an NMI interrupt occurs while the user
program halts or when memory contents are referenced or modified during user program execution, the E8a
emulator cannot control the MCU.
15. Reserved area
The addresses not specified in the Hardware Manual for M16C/62P and M16C/6N Groups are reserved area. Do
not change the contents. Otherwise, the E8a emulator cannot control the MCU.
16. Debugging in stop mode or wait mode
When debugging in stop mode or wait mode, do not operate windows until the program stops at the breakpoint by
setting the breakpoint at the line of the program which will be executed after the stop mode or wait mode is
cancelled. In addition, disable the automatic update in the watch window or fix the display in the memory window
before running the program so memory accesses do not occur during an execution.
When the program is forcibly stopped or when the memory is referred to or modified in stop mode or wait mode,
these mode will be cancelled.
17. Peripheral I/Os during a halt
REJ10J1640-0400
Rev.4.00 Page 18 of 31
During a user program halt, interrupts are not accepted although peripheral I/Os continue to run. For example, a
timer interrupt is not accepted although the timer continues to count when a user program is stopped by a break
after the timer started.
Apr 30, 2010
Commentaires sur ces manuels