Renesas Emulator Debugger M16C PC4701 - Manual (Page 70)

5.6 Method of making MCU file
5.6.1 Method of making MCU file (the M16C/R8C Debugger)
The following content is sequentially described in the MCU file.
Specify the MCU name to the file name, and specify "mcu" to the file extension.
1.
Start address of SFR area
2. End address of SFR area
3. Start address of internal RAM area
4. End address of internal RAM area
5. Start address of ROM area
6. End address of ROM area
7. File name of the Firmware *1
8. MCU type (whether memory space extension mode has to be specified or not)*2
Specify the addresses in hex format, and don't add any prefix which describe its radix.
*1 Specify the addresses in hex format, and don't add any prefix which describe its radix.
MCU Firmware file name
M16C/60 group M30600
M16C/61 group M30600
M16C/62 group M30620B
M16C/20 series M30620B
There is a case that the emulation pod need the different firmware from the listed firmware, when the
emulation pod is re-modeled.
*2 Specify whether the MCU: supports the memory space extension function or not.
When the MCU supports the function (EX: M16C/62 group), specify "1" , the other case, specify "0".
Only when "1" is specified, the setting for memory space extension mode is available in Memory
Extension Mode tab of INIT Dialog
ATTENTION
• The areas specified as the ROM in the MCU file are write-protected from the program.
Even if the write command is executed to the area, no value is written.
However, you can use the Dump command to write values to memory.
(This is enabled only when the Internal area is mapped by the MAP command.)
• If the RAM is assigned to the same area, you must change the setting of the MCU file.
5.6.1.1 Example
0
3FF
400
2BFF
F0000
FFFFF
M30600
0
56