Convert project from CCS v3.3 to v5

Hi Mark,

The XDAIS package is no longer used.  You can ignore this warning or delete the reference from the project if the warning bothers you.

As far as resolving the other resources, I recommend right clicking on the project name in the Project Explorer window and selecting Properties.  On the left hand toolbar, there will be a "Resources" option.  On the new window, towards the top right there will be a "Linked Resources" tab where you can see all of the files which are (attempting to be) linked to the project.  You can modify the paths here to point them to the correct resources.

Kris

Hi Kris,

I have difficulty to load the screen capture file under Word .doc format to show the Linked Resources content for the SPRC229 project. So the following is the list for the Linked Resources with red color:

C:\test\DPS_C280x\v200\DCDC_BUCK_VREG\Buck-ISR.asm

SRC_ROOT\DCDC_BUCK_VREG\Buck-Main.c

SRC_ROOT\DCDC_BUCK_VREG\DCDC_Buck_VReg.pjt

SRC_ROOT\dsp280x\DSP280x_CodeStartBranch.asm

SRC_ROOT\dsp280x\DSP280x_Headers_nonBIOS.cmd

SRC_ROOT\dplib280x\dplib280x.lib

SRC_ROOT\dsp280x\dsp280x_compact.lib

From following console msg (with red color), it seems the compiler can not open the Buck-ISR.asm. I am not able to figure out in the Linked Resources" tab, where I should change to have corect path. Any clue?

Or are you able to imput SPRC229 from Ti's web into your CCSv5, and let me know the steps how to complete the conversion process?

Thanks,

Mark

**** Build of configuration Debug for project DCDC_Buck_VReg ****

C:\TI\ccsv5\utils\bin\gmake -k all

'Building file: C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/Buck-ISR.asm'

'Invoking: C2000 Compiler'

"C:/TI/ccsv5/tools/compiler/c2000/bin/cl2000" -v28 -ml -mt -g --include_path="C:/TI/ccsv5/tools/compiler/c2000/include" --include_path="/packages/ti/xdais" --include_path="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../dsp280x" --include_path="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../dplib280x" --define="_DEBUG" --define="LARGE_MODEL" --quiet --display_error_number --issue_remarks --temp_directory="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/EMP --asm_directory="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/EMP --obj_directory="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/EMP --list_directory="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/EMP --preproc_with_compile --preproc_dependency="Buck-ISR.pp" "C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/Buck-ISR.asm"

"C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/Buck-ISR.asm", ERROR! at EOF:

>> Compilation failure

'Building file: C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/Buck-Main.c'

'Invoking: C2000 Compiler'

[E1500]

file access error: failed to open

"C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/EMP

--list_directory=C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/EMP/Buck-ISR.obj"

for writing

"C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/Buck-ISR.asm", ERROR! : [E1000]

Failed to write object file :

C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/EMP

--list_directory=C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/EMP/Buck-ISR.obj

gmake: *** [C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/EMPBuck-ISR.obj] Error 1

"C:/TI/ccsv5/tools/compiler/c2000/bin/cl2000" -v28 -ml -mt -g --include_path="C:/TI/ccsv5/tools/compiler/c2000/include" --include_path="/packages/ti/xdais" --include_path="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../dsp280x" --include_path="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../dplib280x" --define="_DEBUG" --define="LARGE_MODEL" --quiet --display_error_number --issue_remarks --temp_directory="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/EMP --asm_directory="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/EMP --obj_directory="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/EMP --list_directory="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/EMP --preproc_with_compile --preproc_dependency="Buck-Main.pp" "C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/Buck-Main.c"

Command-line error #569: cannot open IL output file C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/EMP --asm_directory=C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/EMP/Buck-Main.if - Invalid argument

1 fatal error detected in the compilation of "C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/Buck-Main.c".

Compilation terminated.

Mark,

This is difficult to debug from my end without having access to all of your paths and linking variables and such, so I'm going to walk through the debug step by step to see if we can help you along.

To begin with, take a look at this example project.  You'll notice all of the files which have the arrow in the lower right corner of the file icon are linked resources.  These are the ones we need to make sure are resolving. 

So now right click on the project name, in this case, Example_2806xEPwmUpDownAQ, and select properties.  Next, expand the Resource option on the top left and highlight Linked Resources.  Now on the right hand side, select the Linked Resources tab.  This will show all of the linked resources for your project.  In this case, they are all being resolved properly, but if any weren't they would be on the top with a red x next to them.

So now I'll modify one of the paths so that the file is not properly resolved.  As you can see, CCS is telling us that it cannot find the F2806x_DefaultIsr.c file by putting the yellow ! icon on the file. 

So now let's right click on F2806x_DefaultIsr.c and select properties.  This window here is very useful in the debug.  Let's pay particular attention to the "Location" and "Resolved Location" fields.  The "Location" is the path that we have given CCS to look for the file.  This path is using the INSTALLROOT_F2806x_V120 variable, so the Resolved Location gives us the actual full path CCS resolved the "Location" field to on our machine.  Now we can go find the file on our machine and compare the full path to the Resolved Location and see what isn't adding up.  In this case, the file actually exists at C:\ti\controlSUITE\device_support\f2806x\v120\F2806x_common\source\F2806x_DefaultIsr.c.  So by comparing this path with the Resolved Location, you will see I removed the source directory from the CCS Location path.

What may have happened is the variable, in this case, INSTALLROOT_F2806x_V120 may be going up a certain number of directories, and for whatever reason is now going up an extra directory or not going back far enough.  If this is the case, you can modify the path by going back to my first image and highlighting the Path Variables tab.

Please let me know if you have any questions!

Kris

Hi Kris,

Thanks for the guide info.

I am still using SPRC229 from Ti as example (you can download it from: http://www.ti.com/mcu/docs/mcuorphan.tsp?contentId=50550)

The first file failed at compilation is with Buck_ISR.asm. From following, this file in the Project Explorer is without the yellow ! icon as in your screen, but with red X icon. From following screen, you also can see the error message after compilation. I also attach the Buck_ISR.asm's property screen and project folder screen as following. 

By the way, I use SPRC229 for simplicity because my real project was designed based on SPRC229 path and the library it included.

Thank you for help,

Mark

Kris,

Another thought, Can we creat a brand new project and then drag and drop all the source/include/liabrary files into the new project folder? With this way, we can avoid the headache we have faced?

Mark

Mark,

This seems to be a different issue than I thought it was.  I'm going to contact a few other people to ask them to take a look and maybe have this moved over to the CCS forum since this seems to be a problem with the migration process.  

I'm not sure creating a new project is going to help anything as this seems it may be something with file access or the new compiler.  The one thing I notice that looks a little strange to me in your second screenshot is the "archive" box that is checked.  I don't recall seeing this before.  You may want to try unchecking that.

Kris

All,

It seems it is not easy job to converter a project for 280x from CCS v3.3 to v5. The following is just an example.

 http://www.ti.com/mcu/docs/mcuorphan.tsp?contentId=50550)

If above project is difficult to import, is any sample project for 280x chip available?

Appreciate your help,

Mark

I am going to push this thread to the code composer studio forum to see if anyone there has any ideas.  From the screenshots you have posted I'm at a loss for what is going incorrect - all the paths look ok to me. 

There are some simple CCS4 projects in this download (CCS 4 to 5 is a much easier path)  http://www.ti.com/lit/zip/sprc191

Hi Mark,

do you have v4 as well?  Have you tried importing to v4 first and into v4 .. there are some known issues when not using v4 in some cases?     Have you checked if it is available via the TI Resource Explorer?

Please keep us informed.

Best regards,
Lisa

Mark,

If you open the original CCS 3.3 .pjt you will see the following:  -fr".\$TEMP$" -fs".\$TEMP$" and so on. These options set the directory to place files generated by the compiler such as obj files, asm files and so on.

When migrated to CCSv5, these options look like this on the command line you see in the build console:
--asm_directory="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/EMP --obj_directory="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/EMP

As you can see the $TEMP$ is not getting processed properly and then CCS is having trouble resolving these options properly.

If you change these options to set the directory say to C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/TEMP it should build fine. I just verified that it does. To do this, in CCSv5, go into Project Properties->CCS Build->C2000 Compiler->Directory Specifier, and change the directory settings for -ft, -fs, -fr and -ff to something other than $TEMP$. I simply changed it to TEMP and that helped.

Let us know how this goes.

Hi ,

By following your suggestion, after the building, The red X icon on both Buck_ISR.asm and Buck_Main.c are gone. That is a good news.

But I still see link errors (see below). The compile output report with red color attached below too.

Do you think because of the 2808_RAM_Lnk.cmd file? Should I need the file F280x_RAM_DPS.cmd only?

Please advise.

By the way, why there is no any project code as example in the ControlSuite for 280x chip? Those chip are not good for new design?

To answer Lisa's question, I haven't use CCS v4.

Is any project code as example available for CCS v4?

Appreciate all of your efforts!

Mark

Fig 1. Before change

Fig 2 After the change

Fig 3. Project folder

**** Build of configuration Debug for project DCDC_Buck_VReg ****

C:\TI\ccsv5\utils\bin\gmake -k all

'Building file: C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/Buck-ISR.asm'

'Invoking: C2000 Compiler'

"C:/TI/ccsv5/tools/compiler/c2000/bin/cl2000" -v28 -ml -mt -g --include_path="C:/TI/ccsv5/tools/compiler/c2000/include" --include_path="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../dsp280x" --include_path="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../dplib280x" --define="_DEBUG" --define="LARGE_MODEL" --quiet --diag_warning=225 --display_error_number --issue_remarks --temp_directory="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/TEMP" --asm_directory="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/TEMP" --obj_directory="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/TEMP" --list_directory="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/TEMP" --preproc_with_compile --preproc_dependency="Buck-ISR.pp" "C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/Buck-ISR.asm"

'Finished building: C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/Buck-ISR.asm'

' '

'Building file: C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/Buck-Main.c'

'Invoking: C2000 Compiler'

"C:/TI/ccsv5/tools/compiler/c2000/bin/cl2000" -v28 -ml -mt -g --include_path="C:/TI/ccsv5/tools/compiler/c2000/include" --include_path="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../dsp280x" --include_path="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../dplib280x" --define="_DEBUG" --define="LARGE_MODEL" --quiet --diag_warning=225 --display_error_number --issue_remarks --temp_directory="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/TEMP" --asm_directory="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/TEMP" --obj_directory="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/TEMP" --list_directory="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/TEMP" --preproc_with_compile --preproc_dependency="Buck-Main.pp" "C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/Buck-Main.c"

'Finished building: C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/Buck-Main.c'

' '

'Building file: C:/test/DPS_C280x/v200/dsp280x/DSP280x_CodeStartBranch.asm'

'Invoking: C2000 Compiler'

"C:/TI/ccsv5/tools/compiler/c2000/bin/cl2000" -v28 -ml -mt -g --include_path="C:/TI/ccsv5/tools/compiler/c2000/include" --include_path="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../dsp280x" --include_path="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../dplib280x" --define="_DEBUG" --define="LARGE_MODEL" --quiet --diag_warning=225 --display_error_number --issue_remarks --temp_directory="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/TEMP" --asm_directory="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/TEMP" --obj_directory="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/TEMP" --list_directory="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/TEMP" --preproc_with_compile --preproc_dependency="DSP280x_CodeStartBranch.pp" "C:/test/DPS_C280x/v200/dsp280x/DSP280x_CodeStartBranch.asm"

'Finished building: C:/test/DPS_C280x/v200/dsp280x/DSP280x_CodeStartBranch.asm'

' '

'Building target: C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/DCDC_Buck.out'

'Invoking: C2000 Linker'

"C:/TI/ccsv5/tools/compiler/c2000/bin/cl2000" -v28 -ml -mt -g --define="_DEBUG" --define="LARGE_MODEL" --quiet --diag_warning=225 --display_error_number --issue_remarks --temp_directory="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/TEMP" --asm_directory="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/TEMP" --obj_directory="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/TEMP" --list_directory="C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/TEMP" -z -m"C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/DCDC_Buck.map" --stack_size=0x300 --warn_sections -i"C:/TI/ccsv5/tools/compiler/c2000/lib" -i"C:/TI/ccsv5/tools/compiler/c2000/include" -i"C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg" -i"C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG" -i"C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DSP280x" --reread_libs --rom_model -o "C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/DCDC_Buck.out" "C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/TEMP/DSP280x_CodeStartBranch.obj" "C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/TEMP/Buck-Main.obj" "C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/TEMP/Buck-ISR.obj" -l"rts2800_ml.lib" "../2808_RAM_lnk.cmd" "C:/test/DPS_C280x/v200/dsp280x/DSP280x_Headers_nonBIOS.cmd" "C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/F280x_RAM_DPS.cmd" "C:/test/DPS_C280x/v200/dsp280x/SFO_TI_Build.lib" "C:/test/DPS_C280x/v200/dplib280x/dplib280x.lib" "C:/test/DPS_C280x/v200/dsp280x/dsp280x_compact.lib"

"C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/F280x_RAM_DPS.cmd", line 30: error:

>> Compilation failure

BEGIN memory range has already been specified

"C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/F280x_RAM_DPS.cmd", line 30: error:

BEGIN memory range overlaps existing memory range BEGIN

"C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/F280x_RAM_DPS.cmd", line 31: error:

RAMM0 memory range has already been specified

"C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/F280x_RAM_DPS.cmd", line 31: error:

RAMM0 memory range overlaps existing memory range RAMM0

"C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/F280x_RAM_DPS.cmd", line 32: error:

PRAMH0 memory range has already been specified

"C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/F280x_RAM_DPS.cmd", line 32: error:

PRAMH0 memory range overlaps existing memory range PRAMH0

"C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/F280x_RAM_DPS.cmd", line 33: error:

RESET memory range has already been specified

"C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/F280x_RAM_DPS.cmd", line 33: error:

RESET memory range overlaps existing memory range RESET

"C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/F280x_RAM_DPS.cmd", line 34: error:

BOOTROM memory range has already been specified

"C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/F280x_RAM_DPS.cmd", line 34: error:

BOOTROM memory range overlaps existing memory range BOOTROM

"C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/F280x_RAM_DPS.cmd", line 41: error:

RAMM1 memory range overlaps existing memory range BOOT_RSVD

"C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/F280x_RAM_DPS.cmd", line 41: error:

RAMM1 memory range has already been specified

"C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/F280x_RAM_DPS.cmd", line 41: error:

RAMM1 memory range overlaps existing memory range RAMM1

"C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/F280x_RAM_DPS.cmd", line 42: error:

DRAMH0 memory range has already been specified

"C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/F280x_RAM_DPS.cmd", line 42: error:

DRAMH0 memory range overlaps existing memory range DRAMH0

error #10010: errors encountered during linking;

"C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/D

CDC_Buck.out" not built

gmake: *** [C:/test/DPS_C280x/v200/DCDC_BUCK_VREG/DCDC_Buck_VReg/../../DCDC_BUCK_VREG/DCDC_Buck.out] Error 1

gmake: Target `all' not remade because of errors.

**** Build Finished ****

sm3447 said:

But I still see link errors (see below). The compile output report with red color attached below too.

Do you think because of the 2808_RAM_Lnk.cmd file? Should I need the file F280x_RAM_DPS.cmd only?

Most likely. Those linker errors are common ones for v3 BIOS projects imported into v5. That is because in v5, it will often try to auto-pull in another cmd file hence you have two cmd files in there that define the same memory sections. Or it could be that one of the cmd files pulls in a another via the -l option which is no longer needed (see figure 8 of: http://processors.wiki.ti.com/index.php/Importing_CCSv3_Projects_into_CCSv4)

Thanks

ki

Hi All,

The issue is fixed.  Now I can move my project to CCS v5.

Thank you very much!

Mark