Targeting with DSP/BIOS<sup>TM</sup> Options (Embedded Target for Texas Instruments C6000 DSPs)

Embedded Target for Texas Instruments C6000 DSPs

Generated Code Without and with DSP/BIOS

The next two figures show the results of generating code without and with the DSP/BIOS option enabled in the Simulation Parameters dialog.

Example--c6711dskwdnoisf.pjt code generated without DSP/BIOS

When you create your project in Code Composer Studio, the directory structure looks like this.

Example--c6711dskwdnoisf.pjt code including DSP/BIOS

If you now create a new project that includes DSP/BIOS, the directory structure for your project changes to look like the following figure.

Added File
Description

modelname.cdb
Contains the DSP/BIOS objects required by your application, and the vector table for the hardware interrupts

modelnamecfg.s62
Shows all the included files in your project, the variables, the DSP/BIOS objects, and more in this file generated from the .cdb file.

modelnamecfg.h62
The header file for modelnamecfg.s62

modelnamecfg.h
Model configuration header file

modelnamecfg_c.c
Source code for the model

modelnamecfg.cmd
The linker command file for the project; adds the required DSP/BIOS libraries and the library RTS6201.lib or the run-time support library for your target

Notice that the new directory includes some new files, shown in the next table.

Added File	Description
modelname.cdb	Contains the DSP/BIOS objects required by your application, and the vector table for the hardware interrupts
`modelnamecfg.s62`	Shows all the included files in your project, the variables, the DSP/BIOS objects, and more in this file generated from the `.cdb` file.
`modelnamecfg.h62`	The header file for `modelnamecfg.s62`
`modelnamecfg.h`	Model configuration header file
`modelnamecfg_c.c`	Source code for the model
`modelnamecfg.cmd`	The linker command file for the project; adds the required DSP/BIOS libraries and the library `RTS6201.lib` or the run-time support library for your target

With DSP/BIOS functions enabled for your project, the following files no longer appear in your project.

Filename
Description

vectors.asm
Defines the hardware interrupts (HWI) used by interrupt service routines on the processor. This file is removed after all hardware interrupts appear in the HWI section of the Configuration Tool.

Original linker command file--modelname.cmd
Assigns memory sections on the processor. Removed if SECTION directive is empty because all section assignments moved to the configuration file. Otherwise, include call to the DSP/BIOS command file

Some *.lib files
Provide access to libraries for the processor, and peripherals. Removed if their contents have been incorporated in the new compound linker command file.

Filename	Description
`vectors.asm`	Defines the hardware interrupts (HWI) used by interrupt service routines on the processor. This file is removed after all hardware interrupts appear in the HWI section of the Configuration Tool.
Original linker command file--`modelname.cmd`	Assigns memory sections on the processor. Removed if SECTION directive is empty because all section assignments moved to the configuration file. Otherwise, include call to the DSP/BIOS command file
Some `*.lib` files	Provide access to libraries for the processor, and peripherals. Removed if their contents have been incorporated in the new compound linker command file.

When you investigate your generated code, notice that the function "main" portion of modelname_main.c includes different code when you generate DSP/BIOS-enabled source code, and modelname_main.c incorporates one or more new functions.

Code Generation with DSP/BIOS Profiling Generated Code