The E8a and Flash Starter ID input screen is not meant to be used for setting ID codes to MCUs. It is used to input and verify MCU ID codes that have already been set.
When a program is written to flash memory, the ID code is set and cannot become invalid.
Moreover, the ID code is not verified for blank products at the time of shipment or after being fully erased. Please set an optional ID code for blank products.
ID code management is made easier by using the "M3T-NC30WA" C compiler specified commands and optional functions. When not using these, an ID code that has been set for the program is reflected, as in the following.
For example, for fixed vectors that are included in the ID code storage area, when setting to ".lword dummy_int", the highest-order byte is set up to "00h", and the ID code is also set to "00h."
When this results in a comment such as "; . lword dummy_int", the data has remained "FFh" since flash memory erasion in order that writing does not occur to the address, and the ID code becomes "FFh".
You can also check the data of the ID code store area via write-in files, such as mot files.
- Please refer to FAQ No.102481; "Please provide detailed instructions on how to set the ID code." for details on how to set R8C family flash memory ID codes.
- Please refer to FAQ No.102626; "Please provide detailed instructions on how to set the ID code." for details on how to set M16C family flash memory ID codes.
|R8C/34E, R8C/34F, R8C/34G, R8C/34H|
|R8C/36E, R8C/36F, R8C/36G, R8C/36H|
|R8C/38E, R8C/38F, R8C/38G, R8C/38H|
|M16C/6NK, M16C/6NL, M16C/6NM, M16C/6NN|