• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 83 subscribers
  • Views 316 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TMS320F28377D: Build configuration tools ?

RahulB
Prodigy 60 points
Part Number: TMS320F28377D


Hi I am working with TMS320F28377D using CCS IDE which uses different ti compiler versions for cpu1 and cpu2 and sys/bios.

I noticed a few of my colleagues were using different tool versions. Also CCS automatically chooses close enough version which is not desirable for the project.

Question : 

1. Is there any way I can strictly force version numbers, optimizations, compiler flags  and other configs which results in different .hex files (otherwise should generate error) for everyone on the team by using some kind of config file , instead of manual selection from GUI which may result in unintentional inconsistencies?

2. One way to do this is use something like Cmake so that versions can be forces strictly. But not sure how it works with debugger. Would like to know if there is any guide for setting cmake with CCS.

Thanks,

Rahul B

  • +1
    TI__Guru**** 162565 points

    Rahul,

    In general, for "products" and compilers CCS will look for the exact match but if it can't find that it will use one that is deemed to be compatible (based on version difference).  It should output a build warning for that.  If it can't find a compatible version then it will produce an error and fail the build.  We refer to that as flexible validation.  However there is an option to change it to strict.  This is a project level setting.  If you go to the properties of a project.  Select Build, and then the "validator" tab.  You can then check it from flexible to strict.

    If you want to use cmake and make use of the version validation then I think you would need to move away from using a full CCS project and instead use a standard make project and manually manage everything.  I do not have any experience with cmake.

    Regards,

    John

  • 0 in reply to JohnS
    Prodigy 60 points

    Thanks JohnS,

    Validator option will help for now for making sure tools versions are consistent. Still with that .hex files are different because of linking order, probably cmake could help.

    So, in case if we move away from CCS project, does that mean we won't be able to use CCS based debugger as well ?

    - Rahul

  • 0 in reply to RahulB
    Prodigy 60 points

    Also I saw there is an option for link order which is possible through CCS. Will give it a try.

    Thanks,

    Rahul

  • 0 in reply to RahulB
    TI__Guru**** 162565 points

    Rahul,

    You can specify the link order as well.  There is a tab for that in the same project properties dialog.

    If you move to a makefile based project you can still use the CCS debugger.  Most people will end up doing a "manual debug launch".  Basically you launch a debug session and then connect and load the program.

    https://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_debug-main.html#manual-launch

    You can also script those steps if you want or once you have done it once you can edit the configuration so that it does that automatically.

    Regards,

    John