Texas Instruments CDT370, User Manual

Page: 24 / 83

Software Installation
2-10
You can accomplish these tasks by entering individual DOS commands, but
it’s simpler to put the commands in a batch file.
You can edit your system’s autoexec.bat file; however, in some cases, modify-
ing the autoexec.bat file may interfere with other applications running on your
PC. So, if you prefer, you can create a separate batch file that performs these
tasks.
Figure 2–2 (a) shows an example of an autoexec.bat file that contains the sug-
gested modifications (highlighted in bold type).
Figure 2–2 (b) shows a sample batch file that you could create instead of edit-
ing the autoexec.bat file. (For the purpose of discussion, assume that this sam-
ple file is named initdb.bat). The subsections following the figure explain these
modifications.
Figure 2–2. DOS Command Setup for the Debugger
DATE
TIME
ECHO OFF
PATH=c:\dos;c:\370tools
SET D_DIR=c:\370tools
SET D_SRC=;c:\csource
SET D_OPTIONS=–p2 –b
SET C_DIR=c:\370tools
CLS
PATH statement
Environment
variables and
I/O space
(a) Sample autoexec.bat file
PATH=C:\370tools;%path%
SET D_DIR=c:\370tools
SET D_SRC=c:\csource
SET D_OPTIONS=–p2 –b
PATH statement
Environment
variables and
I/O space
(b) Sample initdb.bat file
Invoking the new or modified batch file
-
If you modify the autoexec.bat file, be sure to invoke it before invoking the
debugger for the first time. To invoke this file, enter:
autoexec