NOTICE: The Processors Wiki will End-of-Life in December of 2020. It is recommended to download any files or other content you may need that are hosted on processors.wiki.ti.com. The site is now set to read only.
Migrating to CCSv5
This page covers specific migration topics for migrating to CCSv5 from CCSv4 or CCS3.3.
CCSv5 is based off a newer version of Eclipse than CCSv4. Although the overall look and feel is a lot like CCSv4 and project and debug environments are similar, there are a few key changes. See the page for details on key changes: CCSv5_Changes
If you are migrating from CCS 3.3 to CCS5, the overall environment is quite a bit different. There are some tools to help with migration such as the project import wizard however there are many aspects that are different. Take a look at this page if you are new to the Eclipse environment: Migrating_to_CCSv4
CCSv3.3 Projects (.pjt): CCSv5 uses the Eclipse concept of projects, which is different than the projects in CCSv3.3. CCSv5 includes a project import wizard for importing legacy 3.3 projects. To import a CCS 3.3 project, from the Project menu select "Import Legacy CCSv3.3 Project". This will launch a wizard that will guide you through the conversion process. If you don't want to convert your projects at this time one thing you may want to try is to instead create a standard make project that calls timake to build your existing pjt file. A standard make project is really just a wrapper project where you provide the build utility that you want to use and the parameters that should be passed to it for building and cleaning.
If you are importing a project that uses DSP/BIOS the import wizard will ask you which version of DSP/BIOS you want the imported project to use. It is recommended that you select DSP/BIOS 5.41.xx. This version of DSP/BIOS is compatible with previous 5.x versions.
CCSv4 Projects: CCSv4 and CCSv5 projects are similar. However, the internal storage format of the managed build system changed between CCSv4 and CCSv5 so an internal migration will happen automatically. To import a CCSv4 project, from the Project menu select "Import Existing CCS/CCE Eclipse Project". During import, CCS will ask if you want to convert to the newer format. If you select "No" the project will not be converted and imported into CCSv5.
Note: Projects converted to CCSv5 cannot be directly loaded back into CCSv4, but the conversion process saves a copy of the original .cdtbuild, .project and macros.ini (if one exists) files and names them with a _initial extension. If the project needs to be imported back into CCSv4, these files should first be restored to their original names.
CCSv3.3 Workspaces: Workspaces in CCSv3.x are binary files that contain the serialized content from the windows in CCS, and are totally different from CCSv4/5 workspaces. There is no way to import CCSv3 workspaces into CCSv5.
CCSv4 Workspaces: Although both CCSv4 and CCSv5 use Eclipse workspaces, it is best to create a new workspace when starting with CCSv5 and importing the v4 projects into the new workspace.
Scripting and Automation
CCSv3.x import configurations: It is not possible to use CCSv3.x import configurations (.ccs) files in CCSv5. You will need to re-create these in the target configuration editor in CCSv5. For most target configurations you should just have to select your device and connection (emulator or simulator) and the configuration tool will take care of the rest. For more complex configurations there is a tool provided for building up advanced configurations from scratch, which is explained in this topic: Target_Configuration_-_Custom_Configurations.
CCSv4 Target configurations: Target configurations are the same in CCSv4 and v5, so what was created in CCSv4 can be reused in CCSv5 without changes. The default user area where the target configurations are stored is the same for v4 and v5: "C:\Documents and Settings\<Your login id>\user\CCSTargetConfigurations\".