Zilog Z8F0130 - Manual (Page 513)

UM013037-1212 Appendix D. Using the Command Processor
Zilog Developer Studio II – Z8 Encore!
User Manual
489
Appendix D. 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 – see page 494
•
Supported Script File Commands – see page 495
•
Running the Flash Loader from the Command Processor – see page 518

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 the Command Processor Toolbar section on page 31.
•
Using the batch command to run a command script file from the Command Proces-
sor toolbar.
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 must precede the script file with an at symbol ( @ ) when passing 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, in the log file as well; see the log
section on page 505.
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: