Using the TMS320C6000 Evaluation Compiler and
Simulator
Here are some very basic instructions to get
you started with using the evaluation version of the compiler and simulator.
For complete information on using these tools, refer to the TMS320C6000
C Compiler Reference Guide, the TMS320C6000 Assembly Language Tools
User's Guide, the TMS320C6000 C Source Debugger User's Guide and the Programmers Reference Guide.
First Steps
Once you have installed the evaluation tools,
locate the subdirectory named demos. Once you have located demos, change
to the subdirectory named puzzle. (You can also use environment variables
and command-line options to identify directories that contain source files;
refer to the user's guides.)
You also need to set up the C_DIR environment
variable to point to the directory that contains the runtime-support libraries:
set C_DIR=install_directory\lib
Where install_directory is the directory
in which you have installed the evaluation tools.
Compiling, Assembling, and Linking Example
Code
Compiling for the 'C62x
At the DOS command prompt, enter this on a
single line:
cl6x -g -o -k driver.c puzzle.c -z
puzzle.cmd -l rts6201.lib -o demo1.out
Compiling for the 'C67x:
At the DOS command prompt, enter this on a
single line:
cl6x -g -o -k -mv6700 driver.c puzzle.c
-z puzzle.cmd -l rts6701.lib -o demo1.out
|
cl6x is a shell that runs the compiler,
assembler, and linker; the options used in this example are described below.
You should not receive any error messages,
and the file demo1.out should be created in the puzzle subdirectory.
Debugging Example Code
-
From windows, double-click the icon for the
debugger.
-
From the File menu, choose Load Program. This
displays the Load Program File dialog box.
-
Double-click the demo1.out file. (You may
need to change the working directory.) This loads demo1.out into the simulator.
For more information about using the debugger,
refer to the TMS320C6000 C Source Debugger User's Guide.
Commonly Used Shell
Options
Here is a description of what you told the
shell program to do when you compiled, assembled, and linked the demo program.
| -g |
Generates symbolic debugging directives
that are used by the debugger. |
| -o |
Invokes the optimizer at the default
level (-o is the same as -02). Not all optimizations work well with debugging
because the optimizer's rearrangement of code can make it difficult for
you to correlate source code with object code. Using -g with -o allows
for the maximum amount of optimization that is compatible with debugging. |
| -k |
Keeps the assembly output files
generated by the compiler. Notice that you now have driver.asm and puzzle.asm
in the puzzle directory. |
| -mv6700 |
Generates code for 'C67x devices.
If this switch is not used, the compiler defaults to the 'C62x device. |
| -z |
Invokes the linker. |
| puzzle.cmd |
Identifies the linker command file
for this demo program. Linker command files enable you to put linking information
(such as linker options) into a file instead of on the command line. |
| -l rts6201.lib |
Includes the runtime-support library for
the 'C62x. |
| -l rts6701.lib |
Includes the runtime-support library for
the 'C67x. |
| -o demo1.out |
Names the output file. (The default
is a.out.) Note that this is different from the -o option used earlier
on the command line--because this second -o option follows -z, it is interpreted
as a linker option. |
For a complete description of all the options
you can use with the shell, refer to the TMS320C6000 C Compiler Reference
Guide.
|
|
