CODECOMPOSER: Replacing a bundle compiler 7.4.14 of an installed CCS 6.1.1 package with an older compiler 6.1.21 - Is it safe?

  • Is it possible to get a blessing from TI for doing this hybrid CCS setup?

    Is there any official comment from TI for this topic?

  • Is it supported? Yes. Assuming that the compiler discovery path was added to CCS and the compilers in question were properly discovered by CCS:

    https://dev.ti.com/tirex/explore/node?node=A__AJRfIGmBSkp9naUDysxAFg__ccs_devtools__FUz-xrs__LATEST

    Is it safe? Well, I'm not sure how to answer this question. All I can say is that CCS is designed to support various versions of the compiler, including ones installed standalone.  

  • Thank you!

  • Hi Ki,

    Please provide comments for these cases:

    1. CCS 6.1.1 - User Environment Variable not configured by the installer

        "XDAIS_CG_ROOT" - Manually added!

        This patch is required to rebuild some libraries.

    2. CCS 6.1.1 + bundle compiler 7.4.14 vs CCS 6.1.1 + stand-alone compiler 6.1.21 - File size difference

       I had problem loading up the second file, here's the contents:

     ---Compiler 7.4.14------                       ----Compiler.6.1.21------

    Date       File Size         Lib Name     Date           File Size   Lib Name

    8/19/2025   2,236,150    lib1              10/1/2015 3,84`,478   Lib1

                       124,498       lib2                                   152,184 Lib2

                       242,280       lib3                                   315,444 Lb3

    Based on my experience and trust TI's IDE tool, compiler 7.4.14 is the obvious choice.

  • 1. CCS 6.1.1 - User Environment Variable not configured by the installer

        "XDAIS_CG_ROOT" - Manually added!

        This patch is required to rebuild some libraries.

    What is this variable pointing to? Is XDAIS being used in your project?

    2. CCS 6.1.1 + bundle compiler 7.4.14 vs CCS 6.1.1 + stand-alone compiler 6.1.21 - File size difference

       I had problem loading up the second file, here's the contents:

     ---Compiler 7.4.14------                       ----Compiler.6.1.21------

    Date       File Size         Lib Name     Date           File Size   Lib Name

    8/19/2025   2,236,150    lib1              10/1/2015 3,84`,478   Lib1

                       124,498       lib2                                   152,184 Lib2

                       242,280       lib3                                   315,444 Lb3

    Based on my experience and trust TI's IDE tool, compiler 7.4.14 is the obvious choice.

    The difference could be related to the debug symbol generation. COFF vs ELF or even differences between the DWARF versions. The key thing is the size of the actual binary loaded to the target.

  • 1. CCS 6.1.1

    One particular project has this setting:
    Properties > Build > C6000 Compiler > Include Options

    "$(XDAIS_CG_ROOT)/packages/ti/xdais"

    I assume that the above setting is referring to this folder:
    C:\RTN\xdctools_3_31_00_24_core

    2. File size

      Great valuable information - Thank you!

  • 1. CCS 6.1.1

    One particular project has this setting:
    Properties > Build > C6000 Compiler > Include Options

    "$(CDAIS_CG_ROOT)/packages/ti/xdais"

    I assume that the above setting is referring to this folder:
    C:\RTN\xdctools_3_31_00_24_core

    XDAIS and XDC are different tools. You can get XDAIS from:

    https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/xdais/index.html

    Note that XDAIS has been obsoleted long ago and I don't have much expertise on it so I will not be able to provide much support for XDAIS related questions.

  • Thank you!