
( 35 / 52 )
4.3 Starting Up the Emulator Debugger
(1) Workflow When Starting Up the Emulator Debugger
The workflow when starting up the emulator debugger is shown below.
End of workflow when starting up the M3T-PD30
Executing custom command RESET_10
Starting up the M3T-PD30
Settings in the Init dialog box
Figure 4.3 Workflow when starting up the emulator debugger
(2) Settings in the Init Dialog Box
When starting up the emulator debugger, the Init dialog box is displayed. In the box make
environment settings such as MCU file, communication interface and firmware according to your
system, and click "OK". For details on settings in the Init dialog box, refer to the user's manual of the
emulator debugger. For making an MCU file, refer to "3.5 Procedure for Making an MCU File for
the M3T-PD30" (page 30).
(3) Executing custom command RESET_10
With the M30100T-RPD-E you need to execute custom command RESET_10 every time you start
up the emulator debugger. If the RESET_10 is set in the script file which is executed when the M3T-
PD30 is started up, custom command RESET_10 is automatically executed. For details, refer to "2.5
(2) How to Use Custom Command RESET_10" on page 20.
If the RESET_10 is not set in the script file which is executed when the M3T-PD30 is started up,
execute custom command RESET_10 in the script window.
IMPORTANT
Note on Version of Custom Command RESET_10:
• When you execute custom command RESET_10, if "RESET_10 is done!" is
displayed instead of "RESET_10 (Ver.2) is done!", a custom command program file
of a previous version is used. Replace the old custom command program file
reset_10.p with the "reset_10.p" file in the floppy disc included with this product,
and re-execute custom command RESET_10.
Note on Settings in the Init Dialog Box:
• The present version of custom command RESET_10 has a function to set a work area
start address at 8000h. Therefore, you do not need to change the setting of the address
with the Init dialog box.
Komentáře k této Příručce