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/TM4C1294NCPDT: CCS 6.1.2 upgrade to CCS 8.2 recommendations

Part Number: TM4C1294NCPDT
Other Parts Discussed in Thread: SYSBIOS

Tool/software: Code Composer Studio

I am using ccs 6.1.2, TIRTOS 2.16.0.08, compiler 5.2.7 and XDC 3.31.1333 with a TIVA TM4C1294NCPDT CPU. 

If I want to move to all the latest CCS 8.2, RTOS and network stack what is the recommended way to do this?  

I assume I could just install the latest CCS 8.2 and do all the updates then import my project that was created with CCS 6.2.1.  Should this method work with no problems or would this cause problems with the RTOS.cfg files etc?    If things in the RTOS .cfg file changed, this may cause problems with the latest software

The other option would be to spend the time and install all the software (CCS 8.2) then create a new CCS project and do the full setup on the RTOS, network etc and then pull in all the source code. 

I would prefer to just do the first option since it's so much easier but if it's going to problematic then I should create a new project and start over.

Thanks for any recommendations.

Doug

  • Doug,

    >>I assume I could just install the latest CCS 8.2 and do all the updates then import my project that was created with CCS 6.2.1. Should this method work with no problems or would this cause problems with the RTOS.cfg files etc? If things in the RTOS .cfg file changed, this may cause problems with the latest software

    This can be done without a problem. If you had installed everything under C:\ti, you can also install CCSv8.2 under this directory (they will not overlap) and the first time that CCS runs (just make sure you are using a different workspace!) it should prompt you with the Product Discovery and ask you to install the new product (or products) found.

    You also have to add the compiler already installed with CCSv6.1.2 to your new CCS version according to the instructions below.
    software-dl.ti.com/.../ccs_compiler-installation-selection.html

    If the TI-RTOS (and any other component) is not automatically recognized, please follow the instructions in the reference below:
    software-dl.ti.com/.../ccs_product-installation-selection.html

    Hope this helps,
    Rafael
  • The original compiler in my ccs 6.2 was 5.2.7 and CCS 8.2 chose to use TI c18.1.3.LTS but I see that other compilers in ccs 8.2 are TI v18.1.4.LTS and TI v18.9.0.STS also are available as options. I selected the default use TI c18.1.3.LTS but would it be better to use v18.1.4.LTS or TI v18.9.0.STS instead of c18.1.3.LTS?

     

    The code appears to build, run and debug OK using CCS 8.2. Also it appears that using XGCONF to edit the RTOS.cfg file works as well. I noticed that the RTOS CCS 8.2 installed was 2_16_00_08 but I had 2_16_01_13 in my 6.2 install.

     

    I’ll update my RTOS to the latest but what compiler should I select?

    Thanks,

    Doug

  • I installed the new CCS and tools and pulled in my project so I wanted to report that everything worked OK.  

    I do have a couple comments and questions though.

    When I do a clean build, I now get 5 warnings that I didn't get before.  The warning is " warning #112-D: statement is unreachable" and all 5 of them point to the file RTOS_pem4f.c  For example, here the code one of the warnings points to.

    #1

    /* destruct */
    void ti_sysbios_knl_Event_destruct(ti_sysbios_knl_Event_Struct *obj)
    {
        ti_sysbios_knl_Event_Object__destruct__S(obj);   <<<<<<<<<<<<<<<<<<<<<<<<<  HERE
    }

    What (if anything) should I do to fix this warning?

    #2

    The compiler I had used in CCS 6.1.2 was  5.2.7 but the CCS 8.2 picked the compiler "TI v18.1.3.LTS".  I selected this compiler but noticed that there is another compiler available "TI 18.9.0.STS".  I assume since everything is working OK with the exception of the above warnings that I'm using the right compiler but what are the differences between the compiler  5.2.7, "TI v18.1.3.LTS" and "TI 18.9.0.STS".?

    Thanks,

    Doug

  • Doug,

    Please apologize; I missed your previous reply.

    #1
    What is the exact combination of tools you are using? I get the same issue with 18.1.3.LTS and TivaC TI-RTOS 2.16.0.8. The reason the older compiler did not catch this may be due to either a bug (it didn't appropriately report it) or a project option that suppressed the warning. Something such as --diag_suppress=112 (the code of the warning).

    #2
    The compiler you are using is the "LTS" or "Long Term Support", which means it will be supported for a long time - your code will be fine with it. The newer 18.1.4.LTS is an update to 18.1.3.LTS that comes pre-packaged with your CCSv8.2.0.

    In contrast, the "bleeding edge" 18.9.0.STS is the one that aggregates the newest features and is called "Short Term Support".

    Additional details can be found at:
    processors.wiki.ti.com/.../Compiler_Version_Numbers_and_What_They_Mean

    Hope this helps,
    Rafael
  • I am using CCS 8.2.0.00007, and I see in the tool I have RTOS 2.16.0.08 and RTOS version 2.16.1.14 and version 2.16.1.14 is selected.  I am using the compiler TI v18.1.3.LTS but I have available TI v18.1.4.LTS and TI v18.9.0.STS . It sounds like I may want to use TI v18.1.4.LTS.

    It sounds like I can just ignore the warnings I get when I build clean… Correct?

    Thanks,

    Doug

  • Doug,

    Thanks for the confirmation on the toolset - that is the same I am using here.

    Although I hate leaving warnings unchecked I can see from the source code that these seem to be harmless.

    I will ask a developer on the TI-RTOS team to confirm this for me.

    Regards,
    Rafael
  • Doug,

    The only way to get rid of the compiler warning is with the 18.1.xx series
    1. Move back to the recommended compiler
    2. Move XDCtools to a newer version which is not recommended. This would start a cascade of changing of product versions that we have validated (and do not have any plans on validating or supporting at this time).
    3. Suppress the warning (so basically sweep it under a rug).

    Note: we have not validated the 18.1.xx compiler with the version of TI-RTOS for TivaC you are using. I don't know of any potential issues (other than the annoying compiler warning you mention), but wanted to make sure you knew that.

    Todd
  • As long as the warning is harmless I'm OK with it but the comment "Move back to the recommended compiler" implies I'm not using the recommend compiler.  What is the recommended compiler I should be using?

    Thanks,

    Doug

  • Hi Doug,

    We validated with 5.2.5, so the 5.2.x series would be recommended. Again, I don't know of any reason not to use the new one, but unless there is a compelling reason to move, I generally stay on things that I know work.

    Having said that, the newer TI ARM compiler did make some non-trivial footprint optimizations.

    Todd