Updating 6727 ccs v3.3 project to ccs v4.x

Thank you Ki-Soo for the direction.  The problem I am running into with the importing is that we are currently using BIOS 5.x but we also were using the old CSL libraries and patches for v3.3.  So i guess i will have to migrate from the CSL libraries too?  Is there a recommended path/approach for doing that?  Our project makes use of c672xSystemPatchV2_00_00.lib, csl_C6727.lib, and csl_C672x_intc.lib.  We are currently using BIOS 5.31.09 with CDT 6.0.18 looking to upgrade to 5.4 BIOS.

Thanks,

Seth

v4 does not comes with CSL libraries. What we suggest is to use the same CSL libraries you used in CCSv3. When you import a v3 project, it will add the path to the CSL libraries and headers in the default v3 installation. If you installed v3 in a different location you may have to update these paths

ki

Okay thank you.

1)What about the following library, will i need it any more: C:\CCStudio_v3.3\sprc203\SystemPatch\c672xSystemPatchV2_00_00.lib.

2)I get the following migration warning, here is the library i believe it is referring to in the project C:\Texas Instruments\ccsv4\tools\compiler\C6000 Code Generation Tools 7.2.2\lib\rts67plus.lib should i remove this from linker?:

!WARNING: Source file 'rts67plus.lib' has been linked into the project relative to version-specific Code-generation Tool variable 'CCS_C6000_7_2_2_CG_ROOT'.  It is recommended, however, that you do not link any resources from the Code-generation Tool directory - consider using build-options to reference include-files and libraries, or linking the resource into your project using a new version-independent variable.

 

seth

Seth,

Seth Fowler said:

1)What about the following library, will i need it any more: C:\CCStudio_v3.3\sprc203\SystemPatch\c672xSystemPatchV2_00_00.lib.

Yes, you will need to keep this as contains a fix for the dMAX module.

Seth Fowler said:

2)I get the following migration warning, here is the library i believe it is referring to in the project C:\Texas Instruments\ccsv4\tools\compiler\C6000 Code Generation Tools 7.2.2\lib\rts67plus.lib should i remove this from linker?:

!WARNING: Source file 'rts67plus.lib' has been linked into the project relative to version-specific Code-generation Tool variable 'CCS_C6000_7_2_2_CG_ROOT'.  It is recommended, however, that you do not link any resources from the Code-generation Tool directory - consider using build-options to reference include-files and libraries, or linking the resource into your project using a new version-independent variable.

This warning sounds like it is just telling you to go into the Project's Build Options and point to all the libraries/headers from within there rather than adding the files into the project themselves. Be sure to use the RTS library from whichever specific version of the Code Gen Tools you are using (e.g., don't link in CGTv7.2.2's RTS if you are using CGTv6.1.18).

Thank you. I removed links in projects to .lib files in project.  As far as CGT tool versions go, in v3.3 it says we were using 6.0.18, i don't even see that as an option in the CCS Build settings (6.0.28 oldest) do I need to use the older 6.0.18 or can i use a new version?

I get a lot of redefined linking problems because of duplicates in libraries I guess from our math routines, should i switch my CGT to a later version.  I am just really unclear about what version of what i should be using.  I assumed the import utility would handle that.:

error: symbol "_atan2" redefined: first defined in "C:/Texas

Instruments/ccsv4/tools/compiler/C6000 Code Generation Tools

7.2.2/lib/rts67plus.lib<atan2.obj>"; redefined in

"C:\CCStudio_v3.3\sprc203\UsingROMApplications\FastRts_DspLib\ROMexamples\c6

7xfastrts\lib\fastrts67xR.lib<atan2.obj>"

error: symbol "_atan2" redefined: first defined in "C:/Texas

Instruments/ccsv4/tools/compiler/C6000 Code Generation Tools

7.2.2/lib/rts67plus.lib<atan2.obj>"; redefined i

Thanks,

Seth

Seth,

As far as which version you should be using this is a bit of an open-ended question. This is usually left up to the developer unless there are specific reasons not to use a given version of CGT (compatibility, lack of features, etc.). In the case of the C6727 I think you are fairly free to use whichever version of CGT you would like; however, to make it easier for the porting process you are free to continue using the same older versions of CGT and BIOS if you would prefer.

Seth Fowler said:

As far as CGT tool versions go, in v3.3 it says we were using 6.0.18, i don't even see that as an option in the CCS Build settings (6.0.28 oldest) do I need to use the older 6.0.18 or can i use a new version?

You can actually point CCSv4 to older versions of CGT that it is not able to automatically detect. To do so open the project's build options, select CCS Build on the left, and then to the right of the CGTools drop-down click the button labeled 'More...' You can click 'Select tool from file-system:' and point it to your older CGT version (if you were using the default CGT from v3.3 you can find it in C:\CCStudio_v3.3\C6000\cgtools). Again, the choice is ultimately up to you as to which version you wish to use but if everything is already built with the older version this would be the easiest route.