• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 1335 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCS/TMS320F2808: CCS3.3 --> CCS5.5 Migration Questions

Mihir Gupta65
Intellectual 2155 points
Part Number: TMS320F2808
Other Parts Discussed in Thread: CCSTUDIO, CODECOMPOSER

Tool/software: Code Composer Studio

Hi Team,

I have a customer who is migrating their CCS3.3 to CCS5.5 because they are upgrading to Win10. They have the following questions about the upgrade process:

1         DSP/BIOS Config file

The config.tcf file is interpreted by

"C:\CCStudio_v3.3\bios_5_33_05\xdctools\tconf" -b -Dconfig.importPath="Y:/fl_fl_pd-se_gint-x-001-struct/okc15_servo/se_cbl/targets/ti_f280x;C:/CCStudio_v3.3/bios_5_33_05/packages" Config.tcf

This will generate following files:

Config.s28; Config_c.c; Configcfg.cmd (1 & 2 in screenshot)

  

  • Where do we have to place the tconf command in the build sequence?

The build of the Config.tcf must be handled in two steps:

  1. Interpretation of the *tcf will generate the above mentioned files
  2. Compiling these files
  • How can we do this within CCS5.5?

 

By building selected file “config.tcf” we got following error code:

**** Build of configuration Debug for project se_afdf ****

 

"C:\\ti\\ccsv5\\utils\\bin\\gmake" -k D:/CCSV5servo/okc15_servo/se_afdf/targets/ti_f280x/objects/Config.h

subdir_rules.mk:160: warning: overriding commands for target `D:/CCSV5servo/okc15_servo/se_afdf/targets/ti_f280x/objects/Configcfg_c.obj'

subdir_rules.mk:153: warning: ignoring old commands for target `D:/CCSV5servo/okc15_servo/se_afdf/targets/ti_f280x/objects/Configcfg_c.obj'

gmake: *** No rule to make target `D:/CCSV5servo/okc15_servo/se_afdf/targets/ti_f280x/objects/Config.h'.

 

**** Build Finished ****

 

 

  • When compiling the generated files, there’s no rule for Config.s28 to build – How can we get this rule? I suppose that the new compiler is also able to compile this assembler file.

Simply by adding the file to the project no rule was generated.

 

2         Flashlibs

We are using the old flashlibs (3 in screenshot)

Flash2809_API_V100.lib and

Flash2808_API_V302.lib

 

  • Do they work together with code compiled by the new compiler?

 

  • Do we have to use more recent libs?

 

3         Memory-section-command files

We are using separate “*.cmd” files instead of 2809_RAM_lnk.cmd (chosen by import). (4 in screenshot)

  • Where do we have to place them in the linker dialog??

4         Initial and final build steps

General Dialog of old CCS3.3


  • Where do we have to place initial and final build steps with CCS5.5?

 

5         Project files

  • Which is the new project file? Which files are generated by CCS5 out of which primary files?

… because we have to put the primary files under version control!

 

6         Building the project without CCS-IDE

Building an official  executable product we are using today timake recursively, called by scripts, to automatically generate the product without starting CCS-IDE.

  • How does this work with Codecomposer 5.5?

I know this is detailed and specific. I hope you can help.

Regards,

Mihir Gupta

FAE - South Germany

  • 0
    TI__Guru**** 450911 points

    Mihir Gupta65 said:
    I have a customer who is migrating their CCS3.3 to CCS5.5 because they are upgrading to Win10.

    First note that CCSv5.5 is not officially supported on Windows 10. CCSv6.1.3 is the first version to officially support Windows 10. It doesn't mean that CCSv5.5 cannot run on Windows 10 (I have gotten it to work), but it was never tested. The customer should upgrade to at least CCSv6.1.3 if they want proper Windows 10 support.

    But I see that they are using DSP/BIOS. The last version of CCS to best support DSP/BIOS was CCSv5.5 (which still has RTA support). Perhaps that is why they want to use CCSv5.5. Anyway, it is up to them.

    Mihir Gupta65 said:
    • Where do we have to place the tconf command in the build sequence?

    The build of the Config.tcf must be handled in two steps:

    1. Interpretation of the *tcf will generate the above mentioned files
    2. Compiling these files
    • How can we do this within CCS5.5?

    If the project is a RTSC project, then this is automatically handled for you. If you add a DSP/BIOS tcf file to a CCS project, it will detect it and convert the project to a RTSC project. Then the additional steps of building the tcf file is automatically handled when you build the project. You can identify if the project is a RTSC project by the little "RTSC" icon on the project folder icon in Project Explorer:

    Mihir Gupta65 said:

    2         Flashlibs

    We are using the old flashlibs (3 in screenshot)

    Flash2809_API_V100.lib and

    Flash2808_API_V302.lib

     

    • Do they work together with code compiled by the new compiler?

     

    • Do we have to use more recent libs?

    The experts in the C2000 forum can answer this best

    Mihir Gupta65 said:

    We are using separate “*.cmd” files instead of 2809_RAM_lnk.cmd (chosen by import). (4 in screenshot)

    • Where do we have to place them in the linker dialog??

    The option is under the "File Search Path" options under the C2000 Linker project properties.

    But you can simply just add the cmd files to the project instead (this is more common)

    Mihir Gupta65 said:
    Where do we have to place initial and final build steps with CCS5.5?

    See the screenshot below:

    Mihir Gupta65 said:
    • Which is the new project file? Which files are generated by CCS5 out of which primary files?

    … because we have to put the primary files under version control!

    See: http://processors.wiki.ti.com/index.php/Source_control_with_CCS

    Mihir Gupta65 said:

    Building an official  executable product we are using today timake recursively, called by scripts, to automatically generate the product without starting CCS-IDE.

    See: http://processors.wiki.ti.com/index.php/Projects_-_Command_Line_Build/Create

    Thanks

    ki

  • 0 in reply to Ki
    TI__Intellectual 2155 points
    Thanks Ki! Appreciate the support!

    Regards,
    Mihir