Step 4: Setting Up the Debugger Environment / Step 5: Describing Your Target System to the Debugger
-
1.6 Step 5: Describing Your Target System to the Debugger
In order for the debugger to understand how you have configured your target
system, you must supply a file for the debugger to read.
-
-
Is your port address set correctly?
J
Check to be sure the –p option of the D_OPTIONS environment vari-
able matches the I/O address defined by your switch settings (refer to
Your Switch Settings , Table 1–2, and Identifying Nondefault I/O
Address Space , Table 1–4).
J
Check to see if you have a conflict in address space with another bus
setting. If you have a conflict, change the switches on your board to
one of the alternate settings in Table 1–1. Modify the –p option of the
D_OPTIONS environment variable to reflect the change in your switch
settings.
If you're using an emulation scan path that contains only one 'C2xx and
no other devices, you can use the board.dat file that comes with the 'C2xx
emulator kit. This file describes to the debugger the single 'C2xx in the
scan path and gives the 'C2xx the name CPU_A. Since the debugger au-
tomatically looks for a file called board.dat in the current directory and in
the directories specified with the D_DIR environment variable, you don't
need to create your own board configuration file. Go to the next page.
If you plan to use a different target system, you must follow these steps:
Step 1: Create the board configuration file.
Step 2: Use the composer utility to translate the board configuration file
to binary so that the debugger can read it.
Step 3: Specify the configuration file when invoking the debugger.
These steps are described in the Describing Your Target System to the
Debugger appendix in the TMS320C2xx C Source Debugger User's
Guide .
Installing the Emulator and C Source Debugger With OS/2
1-15
Need help?
Do you have a question about the TMS320C2 Series and is the answer not in the manual?