Texas Instruments TMS320 User Manual page 49

❏ module.h62. DSP/BIOS API header files for assembly programs.
Assembly source files should include the *.h64 header file for any module
the assembly source uses.
❏ program.obj. Object file(s) compiled or assembled from your source file(s)
❏ *.obj. Object files for optional assembly source file(s)
❏ *.cmd. Optional linker command file(s) that contains additional sections
for your program not defined by the DSP/BIOS configuration.
❏ program.out. An executable program for the target (fully compiled,
assembled, and linked). You can load and run this program with Code
Composer Studio commands.
Static Configuration Files
When you build a project that contains a *.tcf file in CCSv4, the following file
are automatically created and added to the Debug folder of the project list
(where "program" is the configuration file name and 62 is replaced by 28, 55,
or 64 as appropriate for your platform):
❏ programcfg.cmd. Linker command file for DSP/BIOS objects. This file
defines DSP/BIOS-specific link options and object names, and generic
data sections for DSP programs (such as .text, .bss, .data, etc.).
❏ programcfg.h. Includes DSP/BIOS module header files and declares
external variables for objects created in the configuration.
❏ programcfg_c.c. Defines DSP/BIOS related objects. (No longer defines
CSL objects.)
❏ programcfg.s62. Assembly language source file for DSP/BIOS settings.
❏ programcfg.h62.
programcfg.s62.
❏ program.cdb. Stores configuration settings for use by run-time analysis
tools. In previous versions, this was the configuration source file. It is now
generated by running the *.tcf file. This file is used by the DSP/BIOS
analysis tools.
❏ programcfg.obj. Object file created from the source file generated by
the configuration.
Files Used to Create DSP/BIOS Programs
Assembly language
Program Generation
header file included by
2-19