Converting CCSv3.3 Projects to CCSv4 Projects
2-10
2.2 Converting CCSv3.3 Projects to CCSv4 Projects
To import a CCSv3.3 project, choose Project > Import Legacy CCSv3.3
Project in CCSv4. Follow the instructions in the import wizard. For more
information about converting CCSv3.3 projects to CCSv4 projects, go to
http://tiexpressdsp.com/wiki/index.php?title=CCSv4 and follow the link near
the bottom of the page to the "Migrating to CCSv4" topic.
If you are importing a project that uses DSP/BIOS, the wizard asks you to
select the version of DSP/BIOS you want the imported project to use. It is
recommended that you select DSP/BIOS 5.40. This version of DSP/BIOS is
compatible with previous 5.x versions.
If you select a DSP/BIOS 6.x version, you will need to make changes to your
source code and configuration.
If you select a DSP/BIOS version prior to 5.40, you will not have access to the
ROV tool and Real-time Analysis debugging features.
2.2.1 Notes for Adding DSP/BIOS to Existing Projects
If your project previously had its own linker command file, you may want to
remove the old linker command file from the project or use both linker
command files. In a DSP/BIOS application, programcfg.cmd is your project's
linker command file. This file already includes directives for the linker to use
the appropriate libraries (e.g., bios.a62, rtdx.lib, rts64plus.lib), so you do not
need to add any of these library files to your project.
For most DSP/BIOS applications the generated linker command file,
programcfg.cmd, suffices to describe all memory segments and allocations.
All DSP/BIOS memory segments and objects are handled by this linker
command file. In addition, most commonly used sections (such as .text, .bss,
.data, etc.) are already included in programcfg.cmd. Their locations (and
sizes, when appropriate) can be controlled from the MEM Manager in the
configuration. In some cases an application can require an additional linker
command file (app.cmd) to describe application-specific sections that are not
described in the linker command file generated by the configuration.
If your project includes the vectors.asm source file, you should remove that
file from the project. Hardware interrupt vectors are automatically defined in
the DSP/BIOS configuration.
Code Composer Studio software automatically scans all dependencies in
your project files, adding the necessary DSP/BIOS and RTDX header files for
your configuration to your project's include folder. So, you don’t need to
explicitly add DSP/BIOS header files to the project.
To Next Page
Loading...
Need help?
General
