User`s guide

12 Developer’s Kit for Texas Instruments™ DSP 1.1 Release Notes
12-6
New Run-Time Libraries
To reduce the size of the generated .out files when you build models for
targeting, and to improve the efficiency of the resulting file, the Developer’s Kit
now uses run-time libraries to include many block functions in the
.out file.
When your model uses one of a number of DSP blocks, the
.out file generated
by the compile uses the
.obj file for the block from the run-time library that is
appropriate for the target. In Version 1.0. the
.out file included all versions of
the block algorithm, rather than just the one required for the specified target.
For example, now when you use the FFT block in a model targeted to a 16-bit
processor, only the 16-bit FFT code appears in the
.out file, instead of all 48
variants of FFT.
One side effect of this architectural change shows up in the Simulink
simulation parameters. When you build a model with the default settings,
compiling the model operates as before. If you change one or more of the
parameters from the default setting, such as switching to little-endian from
big-endian, the compile time can grow somewhat. Compiling a model with
simulation parameter settings that are not the defaults can raise the compile
time to as much as ten minutes or more for complex models.
Architecture Change in CCSDSP Object
To more easily support future target development and to speed up the
processing associated with ccsdsp objects (created when you use the function
ccsdsp), the ccsdsp object does not include user-accessible ActiveX handles,
such as
dspuser. Removing the handles reduces the risks associated with using
handles and the housekeeping required in managing your handles to ensure
that handles do not cause problems if they are left unattended.
To use the handles as they existed in the earlier product release, for example
to perform additional ActiveX/COM interactions with CCS IDE, you can
regenerate the handles. The following MATLAB script recreates the handles
for a specified board and processor.
% h = structure that will hold the CCS/RTDX handles
boardnum = 0 % Supplied desired board number
procnum = 0 % and processor number
% Create activeX handles to Code Composer
h.app = actxserver('CodeComposer.Application');
h.dspboards = get(h.app,'DspBoards');