Specifications

DSP/BIOS Plug-ins
Code Composer Studio Overview 1-9
❏
It serves as a visual editor for creating and setting properties for run-time
objects that are used by the target application’s DSP/BIOS API calls.
These objects include software interrupts, I/O pipes, and event logs.
When you open a configuration file in Code Composer Studio, a window like
the following one appears.
Unlike systems that create objects at run time with API calls that require extra
target overhead (especially code space), all DSP/BIOS objects are statically
configured and bound into an executable program image. In addition to
minimizing the target memory footprint by eliminating run-time code and
optimizing internal data structures, this static configuration strategy detects
errors earlier by validating object properties before program execution.
You can use a configuration file in both programs that use the DSP/BIOS API
and in programs that do not. A configuration file simplifies ISR vector and
memory section addressing for all programs.
Saving a configuration file generates several files that you must link with your
application. See section 1.7.2, page 1–16 for details about these files.