E30A Emulator User
’s Manual
Appendix C Notes on Using This Product
R20UT0422EJ0501 Rev.5.01
Page 55 of 65
Mar 15, 2016
Appendix C Notes on Using This Product
Notes on using this product are listed below. When debugging the MCU using this product, be careful about the following
precautions.
Notes on the Resources of the MCU Used by the Emulator:
When you are using a data comparison break (event E5 only), the E30A Emulator uses several bytes
from the beginning of the MCU’s internal RAM (8 bytes at the addresses 0400h -- 0407h) for data
comparison by the debug monitor program. These bytes cannot be used in the user program when
using a data comparison break.
The E30A Emulator uses approximately 1.2 Kbyte of the internal RAM as needed, for example, to
download a user program. Since the memory contents are saved in advance, you do not need to be
specifically concerned, except that you cannot specify any area that overlaps the interrupt stack and an
area on which DMA operates.
Notes on Power Supply to the User System:
The emulator does not supply power to the user system. Provide power to the user system separately.
Do not change the voltage of the user system after turning on the power.
Note on Downloading Firmware:
Do not shut off the power while downloading the firmware. If this happens, the product will not start up
properly. If the power is shut off unexpectedly, startup the emulator in maintenance mode and
redownload the firmware.
Note on Quitting the Emulator Debugger:
To restart the emulator debugger, always shut power to the emulator and user system off once and
then on again.
Note on Event Settings:
Events are used for breaks, trace, and time measurement in common. For breakpoint settings in the
source window, events are given priority in order to reduce the number of times the flash ROM is
rewritten. Note that the unused events are used in order of followings.
(Extraction start event E0, end of range event E4, and data comparison event E5 are assigned lower
priorities.)
E7 -> E6 -> E3 -> E2 -> E1 -> E5 -> E4 -> E0
Notes on the Software Breaks:
Software breaks execute the tool-only BRK2 command instead of instruction code to generate a BRK
interrupt. Be aware that when trace results are referred to in bus d
isplay, you will see “BFh” displayed
for instruction fetches performed at the addresses that have software breakpoints set.
If a user program is altered before being downloaded, the software breakpoints that have been set may
be displaced depending on the content of alteration. After downloading a user program, be sure to
check the contents of software breakpoints set.
Notes on the Data Access Trace:
16-bit word data starting from an odd address and 32-bit long word data assigned differently from the 4-
byte alignment cannot be traced properly.
Data access event by DMA is not the subject of detection.
