R0E00008AKCE00EP9 Datasheet, PDF (14/23 Pages) Renesas Technology Corp – Microcomputer Development Environment System

E8a Emulator
Section 6 Notes on Using the E8a Emulator
9. 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.3 [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.
In ‘Program Flash’ mode, the contents of the user program are input into the ID code area. When debugging in
other modes, FFh, FFh, FFh, FFh, FFh, FFh, FFh is written into the ID code area regardless of the contents of the
downloaded user program.
Table 6.5
ID Code Storage Area of R8C/18, 19, 1A and 1B
Address
Description
FFDFh First byte of ID code
FFE3h Second byte of ID code
FFEBh Third byte of ID code
FFEFh Fourth byte of ID code
FFF3h Fifth byte of ID code
FFF7h Sixth byte of ID code
FFFBh Seventh byte of ID code
Figure 6.3 [ID Code verification] Dialog Box
Note on ‘Program Flash’ mode:
When the ID code is specified by the -ID option of the lmc30, download the MOT file or HEX file. 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”. 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.
REJ10J1646-0200 Rev.2.00 Jun. 17, 2009
Page 11 of 18