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.

Migrating a legacy C55x DSP/BIOS project from CCS v3.3 to CCS v6

After 2 days of total frustration I'm almost ready to give up.

I'm trying to migrate a legacy DSP/BIOS project for the C5510, that compiles and runs fine under CCS v3.3, over to CCS v6. I have been reading tons of threads in this forum and searched the Internet, but I'm still not able to make it work.

I think it all comes down of having the correct version combination of DSP/BIOS and XDC tools. So far, I have been using DSP/BIOS 5.41.0.06 and XDCtools 3.30.1.25 but that combination seems not to be the correct one.

If I double click on my .tcf file, the "Open TCF File" dialog opens, stays there for about 10 seconds and then just closes without doing anything or giving me any error message. If I try to build my .tcf file I get console output

**** Build of configuration Debug for project Test ****

"C:\\tools\\ti\\ccsv6\\utils\\bin\\gmake" -k out/Debug/Test.h
gmake: *** No rule to make target `out/Debug/Test.h'.

**** Build Finished ****

Can anyone help me please?

Many thanks,

Roland

  • Hi Roland,

    It's hard to speculate what the issue is without more details on the project (was there a migration.log or project.log file generated?). One thing that may remove some headaches is to update your BIOS version to 5.42. This will remove the dependency on XDCtools since that version of BIOS comes with tconf.

    http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/bios/dspbios/index.html

  • Many thanks, Ki-Soo, for your help. Updating to DSP/BIOS 5.42 did the trick.

    But, of course, more problems and questions came up.

    1) The .tcf file seems to be getting built only if it is located at the top level of the project directory. If I place it into the active configuration's output directory (e.g. Debug) then it won't get built. Does this mean that I can not have separate .tcf files for separate configurations (e.g. one for Debug and another for Release)?

    2) I have a user defined linker command file next to the linker command file that DSP/BIOS generates. My command file is in a dedicated directory and somehow its path got put correctly into the makefile when I imported my legacy CCS v3.3 project. However, I do not see where this path is defined in the project's properties. If I move my user defined linker command file to another directory (I want to move it to the configuration's output directory so that I can have separate ones for different configurations) then it gets removed from the makefile and, naturally, my project does not link anymore.

    3) This one is easy ;-). Under the edit menu in CCS v6 I do not see a "Find in Files" command. Can it be that searching among several files can not be done from within CCS v6?

    Many thanks for helping, I really appreciate your time.

    Roland

  • Roland Welte said:
    1) The .tcf file seems to be getting built only if it is located at the top level of the project directory. If I place it into the active configuration's output directory (e.g. Debug) then it won't get built. Does this mean that I can not have separate .tcf files for separate configurations (e.g. one for Debug and another for Release)?

    You can have multiple tcf files in the project folder root and only have one apply to a build configuration by excluding all the others from the build.

    Roland Welte said:
    2) I have a user defined linker command file next to the linker command file that DSP/BIOS generates. My command file is in a dedicated directory and somehow its path got put correctly into the makefile when I imported my legacy CCS v3.3 project. However, I do not see where this path is defined in the project's properties. If I move my user defined linker command file to another directory (I want to move it to the configuration's output directory so that I can have separate ones for different configurations) then it gets removed from the makefile and, naturally, my project does not link anymore.

    Note that if a file is physically in the project folder, CCS will automatically find it and have it as part of the project. There is no need for the project to have a path to it since all files in the project folder are known to it.

    Note - do not put source files in the project configuration subfolder (Debug, Release, etc). That folder is for generated files. CCS probably does not look for source files in there

    Roland Welte said:
    3) This one is easy ;-). Under the edit menu in CCS v6 I do not see a "Find in Files" command. Can it be that searching among several files can not be done from within CCS v6?

    Try CTRL+H

    Thanks

    ki

  • Thanks again, Ki-Soo, for your effective help.

    1), 2) As you have said, one can have several DSP/BIOS configuration files (.tcf) and linker command files (.cmd) in the project folder root and then exclude the ones from building that do not fit a certain configuration. First I thought, that this is kind of cumbersome because changing of the project's configuration would mean to exclude/include .tcf and .cmd files according to a certain configuration. Interestingly, this must only be done once for every configuration. Afterwards, a configuration change will automatically do the relevant build include/exclude of the .tcf and .cmd files.

    3) CTRL+H calls the search dialog which I was looking for. I also realized that there is a flash light symbol in the tool bar. Shame on me for not having checked that on my own ;-).

    Regards,

    Roland