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/CC2652R: SDK issues version 2.30.0.34

Part Number: CC2652R

Tool/software: Code Composer Studio

Hello,

A customer of mine has issues with CCS when they try to use SDK 2.30.34 for the CC2652R and had to implement a work around.

The current work around is to change the 'target' under 'project properties':

General[Products]->Target: ti.targets.arm.elf.M4 -> ti.targets.arm.elf.M4F

(F stands for FPU)

Then the project works and it also works on the launchpad. This should not be necessary compared to the example project where it only says "ti.targets.arm.elf.m4"

What is the impact of this work around?

How can this issue be solved in the proper way?

Thank you for the support!

  • JuMar said:

    The current work around is to change the 'target' under 'project properties':

    General[Products]->Target: ti.targets.arm.elf.M4 -> ti.targets.arm.elf.M4F

    The example projects in the SDK should have the correct setting of ti.targets.arm.elf.M4F. What we have observed is that if the Compiler Version for a project is changed in the Project Properties, then the Target field is incorrectly changed to ti.targets.arm.elf.M4. Is this what may have happened in the customer's case?
    If that is the case, they would need to manually set the Target back to ti.targets.arm.elf.M4F. This is being tracked in a bug report as per this thread

  • Since I haven’t heard back from you, I’m assuming that my earlier reply matches your customer's observation and explains the issue. If not, please post a reply with an update below (or create a new thread). Thanks!