Invoking The New Or Modified Batch File; Os/2 Command Setup For The Debugger - Texas Instruments TMS320C2 Series Installation Manual

Step 4: Setting Up the Debugger Environment
Figure 1–6 (a) shows an example of a config.sys file that contains the sug-
gested modifications (highlighted in bold type). Figure 1–6 (b) shows a sample
batch file that you could create instead of editing the config.sys file. (For the
purpose of discussion, assume that this sample file is named initdb.cmd.) The
subsections following the figure explain these modifications.
Figure 1–6. OS/2 Command Setup for the Debugger
(a) Sample config.sys file to use with the debugger and emulator
PATH statement
Environment
variables and
I/O space
Set IOPL to yes
Reset the
emulator
(b) Sample initdb.cmd file to use with the debugger and emulator
PATH statement
Environment
variables and
I/O space
Reset the
emulator

Invoking the new or modified batch file

-
-
1-10
PATH = C:\OS2\SYSTEM;C:\C2XXTOOLS;C:\C2XXHLL
SET D_DIR=C:\C2XXHLL
SET D_SRC=C:\C2XXCODE;C:\PROJECT\SOURCE
SET D_OPTIONS= –P 280
SET C_DIR=C:\C2XXTOOLS
IOPL = YES
RUN = C:\C2XXHLL\EMURST.EXE
PATH = %PATH%; C:\C2XXHLL
SET D_DIR=C:\C2XXHLL
SET D_SRC=C:\C2XXCODE;C:\PROJECT\SOURCE
SET D_OPTIONS= –P 280
SET C_DIR=C:\C2XXTOOLS
EMURST
If you modify the config.sys file, be sure to invoke it before invoking the
debugger for the first time. To invoke this file, reboot your PC.
If you create an initdb.cmd file, you must invoke it before invoking the
debugger for the first time. After that, you'll need to invoke initdb.cmd for
each session in which you want to use the debugger. To invoke this file,
enter:
INITDB