Epson S5U1C17001C, Руководство пользователя

Страница: 490 / 742

10-40
EPSOn
S5U1C17001C ManUal
(C COMPilEr PaCkagE fOr S1C17 faMily) (Ver. 1.5.0)
10 DEBUggEr
10.5.4 Using a Command file To Execute Commands
You can use a command file to execute a series of debugging commands written in the file.
Creating a command file
Create a command file as a text file using a general-purpose editor, etc.
Example of a command file
Only one command can be written per line.
Example:
c17 rpf c17.par
Sets memory map information.
file sample.elf
Loads debug information.
target sim
Connects the target.
load
Loads a program.
c17 rst
Resets the CPU.
c17 stdout 1 WRITE_FLASH WRITE_BUF stdout.txt
Sets stdout.
c17 stdin 1 READ_FLASH READ_BUF stdin.txt
Sets stdin.
break _exit
Sets a software PC breakpoint.
cont
Executes the program.
c17 stdout 2
Clears stdout.
c17 stdin 2
Clears stdin.
loading/executing a command file
There are two methods of loading and executing a command file:
1. Execution by a startup option
By specifying the
-x
option (or
--command
option) in the debugger startup command, you can execute
one command file at debugger startup.
Example:
c:\EPSON\gnu17\gdb -x startup.cmd
2. Execution by a command
A command named "
source
" is available to execute a command file. The
source
command loads a
specified file and executes the commands in it in the order written.
Example:
(gdb) source startup.cmd
The commands written in a command file are displayed in the [Console] window.
The
source
command can also be executed from the [File] menu in the [Source] window.
Executing a command file repeatedly
Once a command file is executed using the
source
command, you can execute it repeatedly by simply
clicking the [Enter] key thereafter. In this case, all commands written in the command file are executed. This
function is effective until you execute another command.
Command execution intervals
When you enter the
--c17_cmw
option, a wait time specified in seconds is inserted between each command.
The wait time can be specified from 1 to 256 seconds. If any other value is specified, a 1-second wait time is
assumed. When the debugger is started without specifying the
--c17_cmw
option, no wait time is inserted
between each command.