English
Language : 

R0E00008AKCE00EP52 Datasheet, PDF (37/43 Pages) Renesas Technology Corp – Microcomputer Development Environment System
E8a Emulator
6. Notes on Using the E8a Emulator
6.2.5 Flash memory ID code
This MCU function prevents the Flash memory from being read out by anyone other than the user.
The ID code in Table 6.5 written to the flash memory of the MCU must match the ID code displayed in the Figure 6.1 [ID
Code verification] Dialog Box at debugger startup, otherwise the debugger cannot be launched. Note that when the ID code is
FFh, FFh, FFh, FFh, FFh, FFh, FFh, the ID code is regarded as undefined. In this case, the ID code is automatically
authenticated and the [ID Code verification] dialog box is not displayed.
The values written into the ID code area differs depending on the mode.
- ‘Program Flash’ mode:
Contents of the user program
- Modes other than ‘Program Flash’ mode: FFh, FFh, FFh, FFh, FFh, FFh, FFh
(regardless of the contents of the downloaded user program)
Table 6.5 ID Code Storage Area
Address
FFFFFFE8h
FFFFFFE9h
FFFFFFEAh
FFFFFFEBh
FFFFFFFCh
FFFFFFFDh
FFFFFFFEh
Description
First byte of ID code
Second byte of ID code
Third byte of ID code
Fourth byte of ID code
Fifth byte of ID code
Sixth byte of ID code
Seventh byte of ID code
Figure 6.1 [ID Code verification] Dialog Box
Notes
Notes on ‘Program Flash’ mode:
z When the ID code is specified by the -ID option of the lmc100, download the MOT file or HEX file.
z When the X30 file is downloaded, the ID code is not valid. When downloading the X30 file, specify the ID code
using an assembler directive command such as “.BYTE”.
z The file to which the ID code specified by the assembler directive command “.ID” is output varies depending on
the version of the assembler. For details, refer to the Assembler User’s Manual.
REJ10J1877-0201 Rev.2.01 Jun. 26, 2009
Page 37 of 43