User`s guide
Using the Configuration Tool
Program Generation 2-7
❏ CLK - Clock Manager
❏ PRD - Periodic Function Manager
❏ SWI - Software Task Manager
❏ TSK - Task Manager
❏ IDL - Idle Function Manager
The order of objects in the Ordered Collection View can be rearranged by
dragging and dropping the object into its new position. For example, if you
require the CLK0 object to execute immediately after the PRD_clock object,
drag and drop CLK0 on top of the PRD_clock object. The dropped object is
placed in the list immediately after the object that it is dropped upon, and will
execute in that order. This is shown in Figure 2-1.
2.2.7 Referencing Static DSP/BIOS Objects Created with the Configuration Tool
Objects created using the Configuration Tool need to be declared using the
extern variable declaration and must be defined outside of all function bodies.
For example,
extern far PIP_Obj inputObj; /* C6000 devices */
or
extern PIP_Obj inputObj; /* C5000 and C2800 devices */
The DSP/BIOS object is now visible in all functions that follow its definition in
the program.
The Configuration Tool creates these declarations automatically in a file of the
form program cfg.h, where program is the name of your application program.
This file can be # included in your C files that reference the DSP/BIOS object.
Although DSP/BIOS itself is compiled using the small model, you can compile
DSP/BIOS applications using either the C6000 compiler’s small model or any
variation of the large model. (See the TMS320C6000 Optimizing Compiler
User’s Guide .) In fact, you can mix compilation models within the application
code provided all global data that is accessed by using a displacement
relative to B14 is placed no more than 32K bytes away from the beginning of
the .bss section.
DSP/BIOS uses the .bss section to store global data. However, objects
created with the Configuration Tool are not placed in the .bss section. This
maximizes your flexibility in the placement of application data. For example,
the frequently accessed .bss can be placed in on-device memory while larger,
less frequently accessed objects can be stored in external memory.