Debugger Engine Commands
Debugger Commands
763
Microcontrollers Debugger Manual
The new project directory is C:\Program
Files\Freescale\CodeWarrior for Microcontrollers
V6.1\prog

CF

The CF command reads the commands in the specified command file, which are then
executed by the command interpreter. The command file contains ASCII text commands.
Command files can be nested. By default, after executing the commands from a nested
command file, the command interpreter resumes execution of remaining commands in the
calling file. Any error halts execution of CF file commands. When the command is
entered with no parameter, the Open File dialog box is displayed. The CALL command is
equivalent to the CF command.
NOTE If no path is specified, the destination directory is the current project directory.
Usage
CF fileName [;C][;NL]
Where fileName is a file (and path) containing Simulator/Debugger commands.
;C specifies chaining the command file. This option is meaningful in a nested
command file only.
When the ;C option is given in the calling file, the command interpreter quits the
calling file and executes the called file. (i.e. in the calling file, commands following
the CF ... ;C command are never executed).
When the option is omitted, execution of the remaining commands in the calling
file is resumed after the commands in the called file have been executed.
;NL: when set, the commands that are in the called file are not logged in the
Command Line window (and not to log file, when a file has been opened with an
LF command), even if the CMDFILE type is set to ON (see also the LOG
command).
Components
Debugger engine.
Examples:
in>CF commands.txt
Executes the COMMANDS.TXT file, which contains debugger commands like those
described in this chapter.