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/LAUNCHXL-CC1312R1: CCS Optimizer Assistant

Part Number: LAUNCHXL-CC1312R1

Tool/software: Code Composer Studio

One more bug found in CCS  Version: 9.2.0.00013 :

The 'Optimizer Assistant' uses invalid target for compiliation.

It trys to compile a CC1312R1-project for M4 instead of M4F

  • Jan,

    Have you noticed that this happens after changing the compiler tools version used to build the project. Because it sounds a lot like this bug where changing the compiler tools version for a project results in the RTSC Target field changing from M4F to M4. : 

    https://cqweb.ext.ti.com/cqweb/restapi/SDO-Web/SDOWP/RECORD/SYSBIOS-848?format=HTML&noframes=true&recordType=IncidentReport&loginId=readonly&password=readonly

    This bug is supposed to be fixed in the SYS/BIOS kernel, and I expect it should be included in latest SDK releases.

    If you could let us know the version of SimpleLink SDK you are using, and whether you noticed the problem after changing the version of compiler tools for the project, that will help us identify if it is the same bug or a new one. Thanks.

  • I have a project that is compiling fine with the right target M4F. With this project active i have started the optimizer assistant and it is going wrong and uses RTSC target M4

    The Simplelink-SDK is the current/latest version 3.30.00.03.

    CCS is  Version: 9.2.0.00013

    For me its looks that something is going wrong with the optimizer assistant.

    It pairs with another bug : https://e2e.ti.com/support/tools/ccs/f/81/p/857715/3172315#3172315

    Regards

    Jan

  • Jan Ingwer Baer said:
    I have a project that is compiling fine with the right target M4F. With this project active i have started the optimizer assistant and it is going wrong and uses RTSC target M4

    Thank you for clarifying the issue. I can reproduce this with CCS 9.2. 

    Similar to the other thread you referenced, this issue is also fixed in CCS 9.3. I just confirmed that with an internal build of 9.3.
    CCS 9.3 is expected to be released before the end of the month. 

    Thanks for your patience.