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.

CODECOMPOSER: CC1352 buildserver fails after upgrading to CCS12 and new SDK

Part Number: CODECOMPOSER
Other Parts Discussed in Thread: CCSTUDIO

For our CI environment we use a docker image to build our projects.

Now after I upgraded to CCS12 and CC13XX SDK6.30 I get a build error regarding the compiler.

Buildfile generation error occurred..
This project was created using a version of compiler that is not currently installed - TICLANG_2.1.2.LTS [Arm]:
- See 'Help > Install New Software' and select 'Code Generation Tools Updates' to check if this compiler is available through a CCS update.
- Visit CCS App Center to get the latest compiler support.
- Or download and install the compiler [http://software-dl.ti.com/codegen/non-esd/downloads], then register it with CCS through 'Preferences > CCS > Build > Compilers'.
Build stopped..

Now after this SDK upgrade the project is using the TI CLANG compiler which seems not being installed.

I changed the docker image to install the compiler from https://www.ti.com/tool/ARM-CGT#downloads

I also ran the command to let eclipse discover the compiler with:

eclipse -nosplash -data /workspace -application com.ti.common.core.initialize -ccs.toolDiscoveryPath "/opt/ti/ti-cgt-armllvm_2.1.2.LTS/"

But I still keep getting this error.

Anyone any ideas as to how to fix this?

  • Hello,

    If you run:

    > eclipse -nosplash -data /workspace -application com.ti.ccstudio.apps.inspect -ccs.product

    It should output all the compilers discovered by CCS. Do you see clang 2.1.2 under the list of Arm compilers?

    thanks

    ki

  • Hi Ki,

    No I don't see the compiler listed if I execute this command unfortunately. (See below)

    root@41f703a51156:/workspace# eclipse -nosplash -data /workspace -application com.ti.common.core.initialize -ccs.toolDiscoveryPath "/opt/ti/ti-cgt-armllvm_2.1.2.LTS"
    SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
    SLF4J: Defaulting to no-operation (NOP) logger implementation
    SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
    
    Searching for deleted extension-sites to uninstall:
    	Finished!
    
    Searching for new extension-sites to install:
    	Finished!
    
    root@41f703a51156:/workspace# eclipse -nosplash -data /workspace -application com.ti.ccstudio.apps.inspect -ccs.product
    SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
    SLF4J: Defaulting to no-operation (NOP) logger implementation
    SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
    
    Product location: /opt/ti/ccs
    
    Compilers:
    	Arm:
    		TI v20.2.7.LTS [/opt/ti/ccs/tools/compiler/ti-cgt-arm_20.2.7.LTS]
    	C7000:
    		<none>					
    
    Products:
    	com.ti.SIMPLELINK_CC13XX_CC26XX_SDK [SimpleLink CC13xx CC26xx SDK]:
    		6.30.1.03 [/opt/ti/simplelink_cc13xx_cc26xx_sdk_6_30_01_03]
    
    	sysconfig [SysConfig]:
    		1.14.0 [/opt/ti/sysconfig_1.14.0]
    
    	com.ti.rtsc.XDCtools [XDCtools]:
    		3.62.1.16_core [/opt/ti/xdctools_3_62_01_16_core]
    		3.62.1.15_core [/opt/ti/xdctools_3_62_01_15_core]
    
    
    
    root@41f703a51156:/workspace# ll /opt/ti/
    total 48
    drwxr-xr-x  1 root root 4096 Jan  5 13:41  ./
    drwxr-xr-x  1 root root 4096 Dec 16 10:26  ../
    -rwxr-xr-x  1 root root  200 Dec 16 10:30 'Code Composer Studio 12.1.0.desktop'*
    drwxr-xr-x  1 root root 4096 Dec 16 10:31  ccs/
    drwxr-xr-x  8 root root 4096 Dec 16 10:34  simplelink_cc13xx_cc26xx_sdk_6_30_01_03/
    drwxr-xr-x  1 root root 4096 Dec 16 10:35  sysconfig_1.14.0/
    drwxr-xr-x  5 root root 4096 Jan  5 13:41  ti-cgt-armllvm_2.1.2.LTS/
    drwxr-xr-x 10 root root 4096 Dec 16 10:34  xdctools_3_62_01_15_core/
    drwxr-xr-x 10 root root 4096 Dec 16 10:29  xdctools_3_62_01_16_core/
    root@41f703a51156:/workspace# 
    
     

    So it seems that the discovery call does not work or is not referenced correctly.

  • That is odd. In my scenario I manuall downloaded and installed clang 2.1.1 into /opt/ti (I already have 2.1.2 which comes with CCS 12.1 by default) and then ran the command to discover it. It worked. The command I used is pretty much the same:

  • Since CCS is already installed in /opt/ti, I would image that it should look in /opt/ti by default for any additional product installations. 

    What linux distro is being used? I assume you are using the same user account which installed CCS?

  • I use a docker container for this which takes ubuntu 20.04 as distro.

    CCS is installed in /opt/ti indeed and also when I look in the CCS folder in tools/compilers the 2.1.2 CLANG compiler is there as well.

    CCS is installed via the docker compose file so as root normally.

  • What is the exact CCS version? I assume it is not 12.1.

  • CCS12.1.0.00007_linux-x64

  • I assume it is not 12.1.

    oh, wait. i can see that you are using 12.1. 12.1 should come with clang 2.1.2 (in /ccs/tools/compiler). It should be already discovered by CCS...

  • YEs, correct it should already be included. And with earlier versions before clang I never needed to install the compiler separately.

    Now, because I got this error with building I started to install the compiler manually.

  • Do you see clang 2.1.2 in /ccs/tools/compiler?

  • yes

    root@41f703a51156:/opt/ti/ccs/tools/compiler# ll
    total 20
    drwxr-xr-x 5 root root 4096 Dec 16 10:29 ./
    drwxr-xr-x 4 root root 4096 Dec 16 10:27 ../
    drwxr-xr-x 3 root root 4096 Dec 16 10:29 dmed/
    drwxr-xr-x 6 root root 4096 Dec 16 10:27 ti-cgt-arm_20.2.7.LTS/
    drwxr-xr-x 5 root root 4096 Dec 16 10:27 ti-cgt-armllvm_2.1.2.LTS/
    root@41f703a51156:/opt/ti/ccs/tools/compiler# 
    

  • Hi Ki,

    Yes, indeed that seemed to be the issue.

    I installed libtinfo5 in my docker container and now the compiler is recognized automatically by ccs.

    So also no need to install compiler separately because CCS recognizes it builtin version of 2.1.2LTS

    Thanks for your help!