When you execute CMDFILE, you will be prompted with:
Define command file parameter [&ADDR]
To pass the parameter, enter the address of the first memory location to be
modified. You will then be prompted for &VALUE1. If you enter, for example,
"0,-1,20, 0ffffh, 4+5*4", the first parameter "0,-1,20," is passed to &VALUE1 and
the remaining parameters "0ffffh," and "4+5*4" are passed to &ArG_lEfT.
You can also pass the parameters when you invoke the command file (for example,
CMDFILE 1000h 0,-1,20, 0ffffh, 4+5*4).
Other Things to Know About Command Files
You should know the following about using command files:
1 Command files may contain shell variables. Only those shell variables
beginning with "$" followed by an identifier will be supported. An identifier
is a sequence of letters, digits or underscores beginning with a letter or
underscore. The identifier may be enclosed by braces "{ }" or entered directly
following the "$" symbol. Braces are required when the identifier is followed
by a letter, a digit or an underscore that is not interpreted as part of its name.
For example, assume a directory named /users/softkeys and the shell variable
"S". The value of "S" is "soft". By specifying the directory as /users/${S}keys
the correct result is obtained. However, if you attempt to specify the directory
as /users/$Skeys, the Softkey Interface looks for the value of the variable
"Skeys". This is not the operators intended result. You may not get the
intended result unless Skeys is already defined to be "softkeys".
You can examine the current values of all shell variables defined in your
environment with the command "env".
2 Positional shell variables, such as $1, $2, and so on, are not supported. Neither
are special shell variables, such as $@, $*, and so on, supported.
3 You can continue command file lines. This is done by avoiding the line feed
with a backslash (\). A line terminated by "\" is concatenated with any
following lines until a line that does not contain a backslash is found. A line
constructed in this manner is recognized and executed as one single command
line. If the last line in a command file is terminated by "\", it appears on the
command line but is not executed. Normally, the line feed is recognized as the
command terminator. The UNIX environment recognizes three quoting
Chapter 4: Entering Commands
Using Command Files
76
Summary of Contents for 64780A
Page 1: ...Graphical User Interface User s Guide MC68360 68EN360 Emulator Analyzer HP 64780A ...
Page 20: ...xx ...
Page 21: ...Part 1 Quick Start Guide 1 ...
Page 23: ...1 Getting Started 3 ...
Page 45: ...Part 2 Using The Emulator 25 ...
Page 47: ...2 Plugging into a Target System 27 ...
Page 55: ...Chapter 2 Plugging into a Target System Plugging into the Motorola QUADS Target System 35 ...
Page 59: ...3 Starting and Exiting HP 64700 Interfaces 39 ...
Page 69: ...4 Entering Commands 49 ...
Page 103: ...5 Configuring the Emulator 83 ...
Page 122: ...102 ...
Page 123: ...6 Using the Emulator 103 ...
Page 193: ...7 Using the Emulation Bus Analyzer How to record program execution in real time 173 ...
Page 249: ...8 Making Software Performance Measurements 229 ...
Page 279: ...9 Making Coordinated Measurements 259 ...
Page 295: ...Part 3 Reference 275 ...
Page 297: ...10 Setting X Resources 277 ...
Page 312: ...292 ...
Page 313: ...11 Emulator Analyzer Interface Commands 293 ...
Page 391: ...set Chapter 11 Emulator Analyzer Interface Commands set 371 ...
Page 405: ... SYMB Chapter 11 Emulator Analyzer Interface Commands SYMB 385 ...
Page 422: ...402 ...
Page 460: ...440 ...
Page 461: ...Part 4 Concept Guide 441 ...
Page 463: ...13 Concepts of the EMSIM and EMRAM 443 ...
Page 471: ...Part 5 Installation and Service Guide 451 ...
Page 473: ...14 Installation 453 ...
Page 491: ...Chapter 14 Installation Verifying the Installation 471 ...
Page 493: ...15 Installing Updating Emulator Firmware 473 ...
Page 500: ...480 ...
Page 516: ...496 ...
Page 540: ...520 ...