Hi,
I am trying out CCS(v5). How can i import an existing CCS(v3) project of PMSM (sprc178) in CCS(v5)?
Regards
Devi.
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi,
I am trying out CCS(v5). How can i import an existing CCS(v3) project of PMSM (sprc178) in CCS(v5)?
Regards
Devi.
Devi,
Provided you have all the dependencies installed according to section 3.1 of the <pmsm3_3_28xx.pdf> user's guide, the import and successful build can be done simply by following the steps at this page.
However, if you installed newer versions of the peripheral headers and examples files you will have to manually change the version numbers on the paths to correctly point to the installed files after you imported the project as shown above.
For example: if importing the project pmsm3_3_281x_CCS3x, it has the file <DSP281x_CodeStartBranch.asm> pointing to SRC_ROOT\c28\DSP281x\v100\DSP281x_common\source. However, if you install the latest release (1.20) of the peripheral headers and files for the F281x, then you will have to right-click on this source file, select Properties --> Resource --> button Edit --> then edit the Location box to change the path from v100 to v120. Similar thing must be done for the paths that point to the F280x peripheral Headers and files (which the latest revision is 1.70).
Same thing must be done for the compiler include paths. Check below:
Irrespectfully of the peripheral headers and examples files version, the project must explicitly include the *.L28 libraries in the linker options (they are linked in the Project Explorer view, but CCS only recognizes .lib extensions). Check the screenshot below with the entire settings and remarks on these libraries.
For consistency, I recommend including all the libraries in the project options instead of linking them in the Project Explorer - this way you know exactly how many are being included in a single place.
At the end you will be able to build with some warnings regarding compatibility keys - these may be ignored (explanation here).
I don't foresee any trouble during runtime, but if you see any problem with this regard please check with the experts in the C2000 forum - they will be able to provide you further help with the code itself.
Hope this helps,
Rafael