R0E00008AKCE00 Renesas Electronics America, R0E00008AKCE00 Datasheet - Page 160

• Manufacturer Part Number: R0E00008AKCE00
• Description: EMULATOR E8A FOR H8 AND M16C
• Manufacturer: Renesas Electronics America
• Type: In Circuit Debuggerr

Specifications of R0E00008AKCE00

• Contents: Emulator Board, Cables, Software and Documentation
• Core Architecture: R8C, M16C, H8
• Core Sub-architecture: R8C/Lx, M16C/60, M16C/30
• Kit Contents: E8A Emulator, USB-Interface Cable, User-Interface Cable, CD-ROM
• Features: On-Chip Debugging , Flash Memory Programming
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• For Use With/related Products: 740, H8, H8S, M16C, R8C
• Lead Free Status / Rohs Status: Compliant

E8a Emulator User's Manual
17. Note on Using the [Run Program] Dialog Box
18 [Stack Trace] window
19. Memory Access during User Program Execution
20 Internal Flash Memory
21 Suspend during Emulator Use
22 Verification of Memory
23 Overwrite of a File
REJ10J1655-0400 Rev.4.00
Apr 30, 2010
⎯ MEMORY_FILL command
When [Run...] is selected from the [Debug] menu to specify the stop address, there is the
following note:
⎯ When the breakpoint that has been set as Disable is specified as the stop address, note that
When using the NC30WA or NC8C, if parameters and local variables of a function are
referred in the call stack window and one or more parameters are on a register, the register
parameters may be interchanged with the local variables. However, the correct values are
displayed.
For NC308WA, NC30WA, or NC8C, specify the compiler option ‘-genter’, which is used to
output the ENTER or EXITD instruction, to all functions. If this option is not specified, the
[Stack Trace] window will not be correctly displayed.
When a memory is accessed from the memory window, etc. during user program execution,
the user program is resumed after it has stopped in the E8a emulator to access the memory.
Therefore, realtime emulation cannot be performed
The emulator is also available as the programming tool for mass production.
However, the actual MCU, which has been used by connecting to the emulator, has been
programmed to the flash memory at emulation and stressed. Do not use the MCU that has been
used for debugging for the mass products.
The host computer cannot enter suspend mode while the emulator is in use.
Use the FILE_VERIFY command to verify memory. Do not use [Verify Memory…] in the
[Debug] menu.
In command line interface, a file that has the same name as the output file is overwritten
without asking the user.
The [Format] specification in the [Copy Memory] dialog box is ignored. Memory is copied
in a byte unit.
the breakpoint becomes Enable when the user program stops.
Appendix D Notes on High-performance Embedded Workshop
Page 144 of 158