Zilog EZ80F916 - Manual (Page 407)

UM014423-0607 Using the Command Processor
ZiLOG Developer Studio II
eZ80Acclaim! ® User Manual
387
Using the Command Processor
The Command Processor allows you to use commands or script files to automate the exe-
cution of a significant portion of the integrated development environment (IDE). This sec-
tion covers the following topics:
•
“Sample Command Script File” on page 391
•
“Supported Script File Commands” on page 392
•
“Running the Flash Loader from the Command Processor” on page 412
You can run commands in one of the following ways:
•
Using the Command Processor toolbar in the IDE.
Commands entered into the Command Processor toolbar are executed after you press
the Enter (or Return) key or click the Run Command button. The toolbar is described
in “Command Processor Toolbar” on page 22.
•
Using the
batch
command to run a command script file from the Command
Processor toolbar in the IDE.
For example:
batch "c:\path\to\command\file\runall.cmd"
batch "commands.txt"
•
Passing a command script file to the IDE when it is started.
You need to precede the script file with an at symbol (
@
) when passing the path and
name of the command file to the IDE on the command line. For example:
zds2ide @c:\path\to\command\file\runall.cmd
zds2ide @commands.txt
Processed commands are echoed, and associated results are displayed in the Command
Output window in the IDE and, if logging is enabled (see “log” on page 400), in the log
file as well.
Commands are not case sensitive.
In directory or path-based parameters, you can use
\
,
\\
, or
/
as separators as long as you
use the same separator throughout a single parameter. For example, the following exam-
ples are legal:
cd "..\path\to\change\to"
cd "..\\path\\to\\change\\to"
cd "../path/to/change/to"
The following examples are illegal:
cd "..\path/to\change/to"
cd "..\\path\to\change\to"