• State Resolved
  • Locked Locked
  • Replies 17 replies
  • Subscribers 54 subscribers
  • Views 3566 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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 not detecting installed compiler tools in Windows Docker container for CI build

kevin fry
Prodigy 10 points
Other Parts Discussed in Thread: CC2640, CCSTUDIO, CC2538

CCS not detecting installed compiler tools in Windows Docker container for CI build

Hello all

BACKGROUND: I'm trying to set up a CI build for a CC2640 processor using a Windows Docker container. I need to use Windows and not Linux because the BLE SDK for CC2640 only supports windows development (ugh)

So far I have a Docker container built and working with CCS and the various SDKs and libs that we need:
CCS (i've tried 11.2.0.00007 and the latest 12.4.0.00007)
CC2640 BLE SDK 2.01.00.44423
SimpleLink TIRTOS 2.13.00.06
Compiler: TI CGT TMS470 16.9.3LTS (also tried latest version 16.9.11 LTS)
 
The install of all of these tools is successful and working.

PROBLEM:

When I go to build my code in the Docker container, the CGT TMS470 compiler is not found by CCS.

I'm following this documentation for using CCS on the command line software-dl.ti.com/.../ccs_projects-command-line.html

The other SDK packages are found and included just fine with this command

eclipsec.exe -noSplash -data C:\\workspace1 -application com.ti.common.core.initialize -rtsc.productDiscoveryPath c:\ti\tirtos_simplelink_2_13_00_06
eclipsec.exe -noSplash -data C:\\workspace1 -application com.ti.common.core.initialize -rtsc.productDiscoveryPath c:\ti\xdctools_3_31_01_33_core

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
C:\ti\ccs1240\ccs\eclipse>eclipsec.exe -noSplash -data C:\\workspace1 -application com.ti.common.core.initialize -rtsc.productDiscoveryPath c:\ti\tirtos_simplelink_2_13_00_06
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:
Discovered new extension-site: c:\ti\tirtos_simplelink_2_13_00_06
Installing new extension-sites... done!
Finished!
C:\ti\ccs1240\ccs\eclipse>eclipsec.exe -noSplash -data C:\\workspace1 -application com.ti.common.core.initialize -rtsc.productDiscoveryPath c:\ti\xdctools_3_31_01_33_core
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!
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX


However the CCS compiler search fails

eclipsec -nosplash -data C:\\workspace1 -application com.ti.common.core.initialize -ccs.toolDiscoveryPath C:\ti\ccs1240\ccs\tools\compiler\ti-cgt-arm_16.9.11.LTS

Here is the compiler dir, I run the commands from CMD instead  of powershell as powershell hs issues with CCS.

Fullscreen
1
2
3
4
5
6
7
8
9
10
PS C:\ti\ccs1240\ccs\eclipse> dir ..\tools\compiler\
Directory: C:\ti\ccs1240\ccs\tools\compiler
Mode LastWriteTime Length Name
---- ------------- ------ ----
d----- 9/28/2023 3:59 PM ti-cgt-arm_16.9.11.LTS
d----- 9/28/2023 3:58 PM ti-cgt-arm_16.9.3.LTS
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX


Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
C:\ti\ccs1240\ccs\eclipse>eclipsec -nosplash -data C:\\workspace1 -application com.ti.common.core.initialize -ccs.toolDiscoveryPath C:\ti\ccs1240\ccs\tools\compiler\ti-cgt-arm_16.9.11.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!
C:\ti\ccs1240\ccs\eclipse>
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX



When I run:

eclipsec.exe -verbose -noSplash -data C:\\workspace1 -application com.ti.ccstudio.apps.inspect -ccs.product

I don't see the compiler but I see the packages installed.

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
C:\ti\ccs1240\ccs\eclipse>eclipsec.exe -verbose -noSplash -data C:\\workspace1 -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: C:/ti/ccs1240/ccs
Compilers:
Products:
sysconfig [SysConfig]:
1.17.0 [C:/ti/ccs1240/ccs/utils/sysconfig_1.17.0]
com.ti.rtsc.TIRTOSsimplelink [TI-RTOS for SimpleLink Wireless MCUs]:
2.13.0.06 [c:/ti/tirtos_simplelink_2_13_00_06]
com.ti.rtsc.XDCtools [XDCtools]:
3.62.1.16_core [C:/ti/ccs1240/xdctools_3_62_01_16_core]
3.31.1.33_core [C:/ti/xdctools_3_31_01_33_core]
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Now I searched around and after I run the compiler search command I see this file

c:\ti\ccs1240\ccs\eclipse\configuration\com.ti.common.project.core>type compilerProperties.cache.log

Fullscreen
1
2
3
4
5
6
7
Total tool discovery time: 203 ms
Discovered a total of 2 tools:
C:\ti\ccs1240\ccs\tools\compiler\ti-cgt-arm_16.9.11.LTS : 16.9.11.LTS
C:\ti\ccs1240\ccs\tools\compiler\ti-cgt-arm_16.9.3.LTS : 16.9.3.LTS
C:\ti\ccs1240\ccs\eclipse\configuration\com.ti.common.project.core>
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

and the cache file shows it too, so I see that CCS is detecting the compiler and just not installing them.

c:\ti\ccs1240\ccs\eclipse\configuration\com.ti.common.project.core>type compilerProperties.cache

Fullscreen
1
2
3
4
5
cacheFileNamet ↕Ljava/lang/String;L ♣indext ☼Ljava/util/Map;xpt ↑compilerProperties.cachesr ↨java.util.LinkedHashMap4�N\►l��☻ ☺Z ♂accessOrderxr ◄java.util.HashMap♣���▬`�♥ ☻F
��♥ ☺L ♦pathq ~ ☺xpt 7C:\ti\ccs1240\ccs\tools\compiler\ti-cgt-arm_16.9.11.LTSw☻ \xsr 9com.ti.common.project.core.tools.AToolType$ToolProperties ☺☻ ♥L
propertiesq ~ ☻L ◄toolTypeClassNameq ~ ☺L versionq ~ ☺xpsq ~ ♣?@ ♀ ► ☺t
toolFamilyt ♥Armx t *com.ti.ccstudio.buildmodel.CodegenToolTypet ♂16.9.11.LTSsq ~t 6C:\ti\ccs1240\ccs\tools\compiler\ti-cgt-arm_16.9.3.LTSw☻ \xsq ~ ♂sq ~ ♣?@ ♀ ► ☺q ~ ♫q ~ ☼x q ~ ►t
16.9.3.LTSx
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX



Interestingly enough this does work when I run this on my local machine that I've been doing development with in the CCS UI, and the compiler gets installed. But this commandline compiler stuff doesn't work in the docker system.

My Dockerfile to setup the system looks liek this

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
#Dockerfile
# Full windows base image.
FROM mcr.microsoft.com/windows:ltsc2019
# Metadata indicating an image maintainer.
LABEL maintainer="xxx"
SHELL ["cmd", "/S", "/C"]
RUN "mkdir work"
ADD CCS12.4.0.00007_win64.zip 'c:/work'
ADD ble_cc26xx_setupwin32_2_01_00_44423.exe 'c:/work'
ADD ble_sdk_install.bat 'c:/work'
ADD tirtos_simplelink_setupwin32_2_13_00_06.exe 'c:/work'
ADD ti_cgt_tms470_16.9.3.LTS_windows_installer.exe 'c:/work'
ADD ti_cgt_tms470_16.9.11.LTS_windows_installer.exe 'c:/work'
ADD python-3.11.5-amd64.exe 'c:/work'
ADD fw.tar 'c:/work'
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0
    TI__Genius 16490 points

    Hi Kevin, thank you for the very detailed and complete problem description. The topic expert is away today but we will investigate this further on Monday.

  • 0 in reply to AndyW
    Prodigy 10 points

    Excellent, thank you I look forward to it!

  • 0 in reply to kevin fry
    TI__Genius 9175 points

    Hi Kevin, could you please attach your workspace log file?  It is the file C:/workspace1/.metadata/.log.  Thanks!

  • 0 in reply to Baltasar Belyavsky
    Prodigy 10 points

    here is the log file

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    c:\workspace1\.metadata>type .log
    !SESSION 2023-10-08 18:25:52.933 -----------------------------------------------
    eclipse.buildId=4.23.0.I20220308-0310
    java.version=11.0.13
    java.vendor=Eclipse Adoptium
    BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
    Framework arguments: -application com.ti.common.core.initialize -rtsc.productDiscoveryPath c:\ti\tirtos_simplelink_2_13_00_06
    Command-line arguments: -os win32 -ws win32 -arch x86_64 -data C:\\workspace1 -application com.ti.common.core.initialize -rtsc.productDiscoveryPath c:\ti\tirtos_simplelink_2_13_00_06
    !ENTRY com.ti.common.core 1 0 2023-10-08 18:25:57.980
    !MESSAGE path=ccs_base/DebugServer
    !ENTRY com.ti.common.core 1 0 2023-10-08 18:25:57.980
    !MESSAGE debugServerDir=C:/ti/ccs1240/ccs/ccs_base/DebugServer
    !SESSION 2023-10-08 18:26:20.524 -----------------------------------------------
    eclipse.buildId=4.23.0.I20220308-0310
    java.version=11.0.13
    java.vendor=Eclipse Adoptium
    BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
    Framework arguments: -application com.ti.common.core.initialize -rtsc.productDiscoveryPath c:\ti\xdctools_3_31_01_33_core
    Command-line arguments: -os win32 -ws win32 -arch x86_64 -data C:\\workspace1 -application com.ti.common.core.initialize -rtsc.productDiscoveryPath c:\ti\xdctools_3_31_01_33_core
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to kevin fry
    TI__Genius 9175 points

    Ki Kevin,

    The log file does not show anything unexpected.

    I am not familiar with Docker, but there are a few things to look into:

    1. See if you can invoke the compiler tools from the Docker environment.  The tool's "cl" executable must be runnable from the Docker environment in order for CCS to use it.

    2. Ensure that the user is consistent between installing CCS and running CCS.  Many issues people run into end up being the side effect of installing CCS as one user, but then running it as a different user.

    3. Ensure that filesystem access permissions are consistent between installing CCS and running CCS.  Similar to #2, many issues will result if the filesystem location where CCS is installed is writable during installation, but then read-only when running CCS.

    If you want, we could have a call to have a look at your set up.

    - Baltasar

  • 0 in reply to Baltasar Belyavsky
    Prodigy 10 points

    Hi Baltasar thanks for the quick response

    1. Yes the cl exe is runnable

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    c:\ti\ccs1240\ccs\tools\compiler\ti-cgt-arm_16.9.11.LTS\bin>armcl.exe -version
    TI ARM C/C++ Compiler v16.9.11.LTS
    Build Number 1TAUK-I3E26%M8-RTARQ-SAR-C08D
    TI ARM EABI C/C++ Parser v16.9.11.LTS
    Build Number 1TAUK-I3E26%M8-RTARQ-SAR-C08D
    TI ARM C/C++ File Merge v16.9.11.LTS
    Build Number 1TAUK-I3E26%M8-RTARQ-SAR-C08D
    TI ARM C/C++ Optimizer v16.9.11.LTS
    Build Number 1TAUK-I3E26%M8-RTARQ-SAR-C08D
    TI ARM C/C++ Codegen v16.9.11.LTS
    Build Number 1TAUL-I3E26%M8-RTARQ-SAR-C08D
    TI ARM Assembler v16.9.11.LTS
    Build Number 1TAUL-I3E26%M8-RTARQ-SAR-C08D
    TI ARM Embed Utility v16.9.11.LTS
    Build Number 1TAUK-I3E26%M8-RTARQ-SAR-C08D
    TI ARM C Source Interlister v16.9.11.LTS
    Build Number 1TAUK-I3E26%M8-RTARQ-SAR-C08D
    TI ARM Linker v16.9.11.LTS
    Build Number 1TAUL-I3E26%M8-RTARQ-SAR-C08D
    TI ARM Absolute Lister v16.9.11.LTS
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    2 and 3. I just tested by running the CCS installer, then compiler installer back to back on command line without changing permissions or user or anything and it still fails

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    C:\work\CCS12.4.0.00007_win64>ccs_setup_12.4.0.00007.exe --mode unattended --disable-components PF_MSP430,PF_MSP432
    C:\work\CCS12.4.0.00007_win64>dir c:\ti
    Volume in drive C has no label.
    Volume Serial Number is C2F9-CD1F
    Directory of c:\ti
    10/09/2023 03:12 PM <DIR> .
    10/09/2023 03:12 PM <DIR> ..
    10/09/2023 03:12 PM <DIR> ccs1240
    0 File(s) 0 bytes
    3 Dir(s) 136,014,143,488 bytes free
    ...
    c:\work>ti_cgt_tms470_16.9.11.LTS_windows_installer.exe --mode unattended --prefix C:\ti\ccs1240\ccs\tools\compiler
    c:\ti\ccs1240\ccs\eclipse>eclipsec.exe -verbose -noSplash -data C:\\workspace1 -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
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Could the fact that the user is "user manager\containeradministrator" be an issue? IT doesn't seem to fail or have issues at any other point.

    here is the .log from the workspace dir

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    c:\ti\workspacekevin\.metadata>type .log
    !SESSION 2023-10-09 16:39:09.003 -----------------------------------------------
    eclipse.buildId=4.23.0.I20220308-0310
    java.version=11.0.13
    java.vendor=Eclipse Adoptium
    BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
    Framework arguments: -application com.ti.common.core.initialize -ccs.toolDiscoveryPath C:\ti\ccs1240\ccs\tools\compiler\ti-cgt-arm_16.9.11.LTS
    Command-line arguments: -os win32 -ws win32 -arch x86_64 -data C:\ti\workspacekevin -application com.ti.common.core.initialize -ccs.toolDiscoveryPath C:\ti\ccs1240\ccs\tools\compiler\ti-cgt-arm_16.9.11.LTS
    !ENTRY com.ti.common.core 1 0 2023-10-09 16:39:11.081
    !MESSAGE path=ccs_base/DebugServer
    !ENTRY com.ti.common.core 1 0 2023-10-09 16:39:11.081
    !MESSAGE debugServerDir=C:/ti/ccs1240/ccs/ccs_base/DebugServer
    !SESSION 2023-10-09 16:39:35.366 -----------------------------------------------
    eclipse.buildId=4.23.0.I20220308-0310
    java.version=11.0.13
    java.vendor=Eclipse Adoptium
    BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
    Framework arguments: -application com.ti.common.core.initialize -ccs.toolDiscoveryPath C:\ti\ccs1240\ccs\tools\compiler\
    Command-line arguments: -os win32 -ws win32 -arch x86_64 -data C:\ti\workspacekevin -application com.ti.common.core.initialize -ccs.toolDiscoveryPath C:\ti\ccs1240\ccs\tools\compiler\
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to kevin fry
    Prodigy 10 points

    At this point a call sounds like it would be necessary, when would be a good time?

  • 0 in reply to kevin fry
    TI__Genius 9175 points

    Hi Kevin,

    I noticed one strange thing in the output of you running the 'inspect' command - it shows nothing under the "Compilers:" heading.  Normally, it should list all the known device-families, and then all the discovered compilers under those device-families.  If no compilers are discovered, it should still list all known device-families with the string "<none>" under each.  So I'm suspecting that maybe your CCS installation does not include any devices.

    Can you try re-installing your CCS without disabling any components?  I.e. install the full CCS, with all the device families.  And then let's see what the output of 'inspect' command would be.

    Thanks,

    - Baltasar

  • 0 in reply to Baltasar Belyavsky
    Prodigy 10 points

    Hello Baltasar,

    When I install CCS 11.2.0, it acts the same with respect to not finding the arm compiler when I direct it to. But the 'inspect' command also shows the C7000 device with 'none' for compiler so I know that devices are getting installed.

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    C:\ti\ccs1120\ccs\eclipse>eclipsec.exe -verbose -noSplash -data C:\\workspace1 -application com.ti.ccstudio.apps.inspect -ccs.product
    Product location: C:/ti/ccs1120/ccs
    Compilers:
    C7000:
    <none>
    Products:
    sysconfig [SysConfig]:
    1.12.0 [C:/ti/ccs1120/ccs/utils/sysconfig_1.12.0]
    com.ti.rtsc.XDCtools [XDCtools]:
    3.62.1.16_core [C:/ti/ccs1120/xdctools_3_62_01_16_core]
    C:\ti\ccs1120\ccs\eclipse>
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to Baltasar Belyavsky
    Prodigy 10 points

    And the reason I can't install with the "PF_MSP430,PF_MSP432" components is that when I do install with those, the 'unattended' no GUI install fails because a dialog tries to pop up to install an MSP430  simulator or something and that hangs the installer when it needs to be unattended and there is no GUI.

    But I've tested it on my local machine and the MSP430 isn't needed to install other devices as far as I can tell

  • 0 in reply to kevin fry
    TI__Genius 9175 points

    Hi Kevin,

    It does look like your CCS is somehow failing to install all device-families.  In your case, you should see the "Arm" family under "Compilers:" when you run the "inspect" command.  It should look something like this:

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    PS C:\CCS\12.5.0.00006\ccs\eclipse> .\eclipsec.exe -nosplash -data workspace -application com.ti.ccstudio.apps.inspect "-ccs.product"
    Product location: C:/CCS/12.5.0.00006/ccs
    Compilers:
    Arm:
    TI v20.2.7.LTS [C:/CCS/12.5.0.00006/ccs/tools/compiler/ti-cgt-arm_20.2.7.LTS]
    TI Clang v3.2.0-beta.1.20230912.2231+6f7ba078b6c957dda2026c007925a72e0699771f [C:/Work/tools/TICLANG/ARM/ti-cgt-armllvm_3.2.0-beta.1.20230912.2231-6f7ba078b6c957dda2026c007925a72e0699771f]
    TI Clang v3.2.0.LTS [C:/CCS/12.5.0.00006/ccs/tools/compiler/ti-cgt-armllvm_3.2.0.LTS]
    GNU v8.3.1 (Energia) [C:/Users/a0389310/AppData/Local/Energia15/packages/energia/tools/arm-none-eabi-gcc/8.3.1-20190703]
    GNU v6.3.1 (Energia) [C:/TI/energia_tool_arm-none-eabi-gcc_6.3.1-20170620]
    GNU v4.8.4 (Energia) [C:/Users/a0389310/AppData/Local/Energia15/packages/energia/tools/arm-none-eabi-gcc/4.8.4-20140725]
    C2000:
    TI v22.6.1.LTS [C:/CCS/12.5.0.00006/ccs/tools/compiler/ti-cgt-c2000_22.6.1.LTS]
    TI Clang v0.17.2 [C:/Work/tools/TICLANG/C2900/ti-cgt-c29_0.17.2]
    C5500:
    <none>
    C6000:
    TI v8.3.12 [C:/CCS/12.5.0.00006/ccs/tools/compiler/ti-cgt-c6000_8.3.12]
    C7000:
    <none>
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Could you try running the "inspect" command on your CCS install that is outside of the Docker environment?  I.e. the install that you say works as expected...

    Could you also please try running this command to dump the full list of devices in your Docker setup?:

       eclipsec -nosplash -data workspace -application com.ti.ccstudio.apps.inspect "-ccs.devices" "-ccs.devices:groupBy:family"

    And one more thing - could you please attach the file <ccs>/ccs/install_logs/<xxxxxx>/ccs_install_12.<x.x.xxxxx>.log

  • 0 in reply to Baltasar Belyavsky
    Prodigy 10 points

    Hmm if I try to install CCS in Docker without the --disable-components

    The install fails and I get this error in the install log

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    [15:31:38] CCS_INFO: Done installing repository MSP430_BUILD_DEBUG
    [15:31:38] CCS_INFO: Looking for binaries to install...
    [15:31:38] CCS_INFO: Found C:\ti\ccs1240\ccs\eclipse\downloads\ti_msp430pack_header_files_setup_11.1.0.exe from repo type component MSP430_BUILD_DEBUG, installing now
    [15:31:38] CCS_INFO: Installing MSP430_BUILD_DEBUG
    [15:31:38] showprogress = false
    [15:31:39] CCS_INFO: Installing C:\ti\ccs1240\ccs\eclipse\downloads\ti_msp430pack_header_files_setup_11.1.0.exe
    [15:31:39] CCS_INFO: Actual executable C:\ti\ccs1240\ccs\eclipse\downloads\ti_msp430pack_header_files_setup_11.1.0.exe
    Executing C:\ti\ccs1240\ccs\eclipse\downloads\ti_msp430pack_header_files_setup_11.1.0.exe --prefix "c:\ti\ccs1240/ccs" --eclipseprefix "c:/ti/ccs1240/ccs/eclipse" --mode unattended --installer-log "c:\ti\ccs1240/ccs/install_logs
    /20231019152838" --ccs true
    Script exit code: 0
    Script output:
    Ignoring option ccs
    Script stderr:
    [15:31:51] CCS_WARNING: Found C:\ti\ccs1240\ccs\install_logs\ti_msp430pack_header_files11.1.0_install.log, component installer needs to be updated.
    [15:31:52] CCS_INFO: Done installing executable MSP430_BUILD_DEBUG C:\ti\ccs1240\ccs\eclipse\downloads\ti_msp430pack_header_files_setup_11.1.0.exe
    [15:31:53] CCS_INFO: Found C:\ti\ccs1240\ccs\eclipse\downloads\ti_msp430pack_setup64_11.1.0.exe from repo type component MSP430_BUILD_DEBUG, installing now
    [15:31:53] CCS_INFO: Installing MSP430_BUILD_DEBUG
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to Baltasar Belyavsky
    Prodigy 10 points

    Here is the 'inspect' command output outside of the docker env in my regular win10 install that works, but of course that already has the arm compiler installed

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    C:\ti\ccs1120\ccs\eclipse>eclipsec.exe -verbose -noSplash -data C:\\workspace1 -application com.ti.ccstudio.apps.inspect -ccs.product
    Product location: C:/ti/ccs1120/ccs
    Compilers:
    Arm:
    TI v20.2.5.LTS [C:/ti/ccs1120/ccs/tools/compiler/ti-cgt-arm_20.2.5.LTS]
    TI v16.9.11.LTS [C:/ti/ccs1120/ccs/tools/compiler/ti-cgt-arm_16.9.11.LTS]
    TI v16.9.3.LTS [C:/ti/ccs1120/ccs/tools/compiler/ti-cgt-arm_16.9.3.LTS]
    TI Clang v1.3.1.LTS [C:/ti/ccs1120/ccs/tools/compiler/ti-cgt-armllvm_1.3.1.LTS]
    C7000:
    <none>
    Products:
    sysconfig [SysConfig]:
    1.12.0 [C:/ti/ccs1120/ccs/utils/sysconfig_1.12.0]
    com.ti.rtsc.TIRTOSsimplelink [TI-RTOS for SimpleLink Wireless MCUs]:
    2.13.0.06 [C:/ti/tirtos_simplelink_2_13_00_06]
    com.ti.rtsc.XDCtools [XDCtools]:
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Here is the inspect commands in the Docker install for CCS 11 and CCS 12

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    docker ccs11.2.0
    C:\ti\ccs1120\ccs\eclipse>eclipsec.exe -verbose -noSplash -data c:\\workspae2 -application com.ti.ccstudio.apps.inspect -ccs.product
    Product location: C:/ti/ccs1120/ccs
    Compilers:
    C7000:
    <none>
    Products:
    sysconfig [SysConfig]:
    1.12.0 [C:/ti/ccs1120/ccs/utils/sysconfig_1.12.0]
    com.ti.rtsc.XDCtools [XDCtools]:
    3.62.1.16_core [C:/ti/ccs1120/xdctools_3_62_01_16_core]
    C:\ti\ccs1120\ccs\eclipse>eclipsec.exe -verbose -noSplash -data c:\\workspae2 -application com.ti.ccstudio.apps.inspect "-ccs.devices" "-ccs.devices:groupBy:family"
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to kevin fry
    Prodigy 10 points

    And here is the install log from my Docker container..

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    Log started 09/28/2023 at 15:45:30
    Preferred installation mode : unattended
    Trying to init installer in mode unattended
    Mode unattended successfully initialized
    [15:45:30] CCS_INFO: Installer timestamp 20230928154530
    [15:45:31] Installer arguments --mode unattended --disable-components PF_MSP430,PF_MSP432
    [15:45:31] CCS_INFO: Initialization sets components_download_url to http://software-dl.ti.com/ccs/esd/CCSv12/CCS12.4.0.00007_win64/components
    [15:45:31] CCS_INFO: Reboot required: false
    Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\Texas Instruments\Code Composer Studio 12.4.0.00007 Version. Setting variable oldVersion to empty value
    [15:45:31] createshortcuts set to true
    [15:45:32] CCS_INFO: Temporary folder set to C:\Users\ContainerAdministrator\AppData\Local\Temp/ccs_cfed6d61-8c64-4578-5de3-fb94cd6db1d6
    [15:45:33] CCS_INFO: Product families available: PF_MSP430,PF_MSP432,PF_MSPM0,PF_CC2X,PF_CC3X,PF_CC2538,PF_C28,PF_TM4C,PF_HERCULES,PF_SITARA,PF_SITARA_MCU,PF_OMAPL,PF_DAVINCI,PF_OMAP,PF_TDA_DRA,PF_C55,PF_C6000SC,PF_C66AK_KEYSTONE,PF_MMWAVE,PF_C64MC,PF_DIGITAL_POWER,PF_PGA
    [15:45:33] CCS_INFO: Components available: ARM_CGT_HELP,BBONE_FTDI_DRIVERS,C2000_CGT_HELP,C6000_CGT_HELP,CCS_DOC,CCS_LAUNCHER,CCS_UTILS,CGT_DEFAULTLIBS_C2800,CGT_DEFAULTLIBS_C6000_V8P,CGT_DEFAULTLIBS_MSP430,CGT_DEFAULTLIBS_TMS470,CLOUDAGENT,DEV_SUPPORT_AUTOMOTIVE,DEV_SUPPORT_C55XX,DEV_SUPPORT_C6000,DEV_SUPPORT_CC2538,DEV_SUPPORT_CC26XX,DEV_SUPPORT_CC3220,DEV_SUPPORT_CC3230,DEV_SUPPORT_CC32XX,DEV_SUPPORT_CC32XX_COMMON,DEV_SUPPORT_DAVINCI,DEV_SUPPORT_INTEGRA,DEV_SUPPORT_MMWAVE,DEV_SUPPORT_OMAP,DEV_SUPPORT_PGA,DEV_SUPPORT_SHARED,DEV_SUPPORT_SITARA,DEV_SUPPORT_SITARA_MCU,DEV_SUPPORT_UCD31XX,DMED,DS,DS_FLASH,DVT,ECLIPSE,EMU_BH,EMU_C2000,EMU_C2000_FLASH,EMU_HERCULES,EMU_TI,IDE,IDE_CHROME,IDE_GC,IDE_TOOLS_COMMON,INSTALLER,JRE,KEYSTONE2,MSP430_BUILD_DEBUG,MSP430_CGT_HELP,MSP430_GCC_SUPPORT,MSP432_BUILD_DEBUG,MSPM0,MSVC_REDIST_LATEST,NODEJS,P2APP,P2TOOLS,SEGGER_J_LINK,SEGGER_J_LINK_DRIVERS,SYSCONFIG,TARGETDB_DEF_PROPS,TARGET_CONTENT_CORE,TIREX,TIREX4,TIVA_STELLARIS_DRIVERS,TIVA_TM4C,TIVA_TM4E,TI_ARM_CLANG,USERGUIDE,core
    [15:45:34] PFsToBeInstalled: PF_MSP430 PF_MSP432 PF_MSPM0 PF_CC2X PF_CC3X PF_CC2538 PF_C28 PF_TM4C PF_HERCULES PF_SITARA PF_SITARA_MCU PF_OMAPL PF_DAVINCI PF_OMAP PF_TDA_DRA PF_C55 PF_C6000SC PF_C66AK_KEYSTONE PF_MMWAVE PF_C64MC PF_DIGITAL_POWER PF_PGA
    [15:45:34] Running in unattended mode, must validate system.
    [15:45:34] CCS_INFO: Running in unattended mode, must validate installdir c:/ti/ccs1240.
    [15:45:35] CCS_INFO: Testing c:/program files/ in install path c:/ti/ccs1240
    [15:45:35] CCS_INFO: Testing c:/program files \(x86\)/ in install path c:/ti/ccs1240
    [15:45:35] CCS_INFO: Testing c:/program files/ in install path c:/ti/ccs1240
    [15:45:36] Logdir = c:\ti\ccs1240/ccs/install_logs/20230928154530
    [15:45:36] CCS_INFO: CCStudio set to c:/ti/ccs1240/ccs/eclipse/ccstudio.exe
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to kevin fry
    Prodigy 10 points

    So I just found something interesting! I have a PC with a clean install  of win10, and I installed CCS 11.2 with the command line "--mode unattended --disable-components PF_MSP430,PF_MSP432"

    And then installed the arm compiler and tried to use the command line command to find the arm compiler and it failed just like the docker container! So you can reproduce this yourself just on a normal system, no docker required.

    So it seems you are right I need to NOT disable those components. However if I try to install in a docker container without disabling the components, the install hangs. I posted the hanging install log from the Docker container above, but here it is again

    the ccs dirs:

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    Directory of C:\ti\ccs1240
    10/19/2023 04:47 PM <DIR> .
    10/19/2023 04:47 PM <DIR> ..
    10/19/2023 04:49 PM <DIR> ccs
    0 File(s) 0 bytes
    3 Dir(s) 136,045,027,328 bytes free
    C:\ti\ccs1240>cd ccs
    C:\ti\ccs1240\ccs>dir
    Volume in drive C has no label.
    Volume Serial Number is C2F9-CD1F
    Directory of C:\ti\ccs1240\ccs
    10/19/2023 04:49 PM <DIR> .
    10/19/2023 04:49 PM <DIR> ..
    10/19/2023 04:49 PM <DIR> install_logs
    0 File(s) 0 bytes
    3 Dir(s) 136,045,027,328 bytes free
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    And then here are the logs

    ccs_install_12.4.0.00007.log

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    Log started 10/19/2023 at 16:46:16
    Preferred installation mode : unattended
    Trying to init installer in mode unattended
    Mode unattended successfully initialized
    [16:46:17] CCS_INFO: Installer timestamp 20231019164617
    [16:46:17] Installer arguments --mode unattended
    [16:46:17] CCS_INFO: Initialization sets components_download_url to http://software-dl.ti.com/ccs/esd/CCSv12/CCS12.4.0.00007_win64/components
    [16:46:18] CCS_INFO: Reboot required: false
    Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\Texas Instruments\Code Composer Studio 12.4.0.00007 Version. Setting variable oldVersion to empty value
    [16:46:18] createshortcuts set to true
    [16:46:18] CCS_INFO: Temporary folder set to C:\Users\ContainerAdministrator\AppData\Local\Temp/ccs_2811f384-3ff6-4670-5a38-998a9508e4d4
    [16:46:19] CCS_INFO: Product families available: PF_MSP430,PF_MSP432,PF_MSPM0,PF_CC2X,PF_CC3X,PF_CC2538,PF_C28,PF_TM4C,PF_HERCULES,PF_SITARA,PF_SITARA_MCU,PF_OMAPL,PF_DAVINCI,PF_OMAP,PF_TDA_DRA,PF_C55,PF_C6000SC,PF_C66AK_KEYSTONE,PF_MMWAVE,PF_C64MC,PF_DIGITAL_POWER,PF_PGA
    [16:46:20] CCS_INFO: Components available: ARM_CGT_HELP,BBONE_FTDI_DRIVERS,C2000_CGT_HELP,C6000_CGT_HELP,CCS_DOC,CCS_LAUNCHER,CCS_UTILS,CGT_DEFAULTLIBS_C2800,CGT_DEFAULTLIBS_C6000_V8P,CGT_DEFAULTLIBS_MSP430,CGT_DEFAULTLIBS_TMS470,CLOUDAGENT,DEV_SUPPORT_AUTOMOTIVE,DEV_SUPPORT_C55XX,DEV_SUPPORT_C6000,DEV_SUPPORT_CC2538,DEV_SUPPORT_CC26XX,DEV_SUPPORT_CC3220,DEV_SUPPORT_CC3230,DEV_SUPPORT_CC32XX,DEV_SUPPORT_CC32XX_COMMON,DEV_SUPPORT_DAVINCI,DEV_SUPPORT_INTEGRA,DEV_SUPPORT_MMWAVE,DEV_SUPPORT_OMAP,DEV_SUPPORT_PGA,DEV_SUPPORT_SHARED,DEV_SUPPORT_SITARA,DEV_SUPPORT_SITARA_MCU,DEV_SUPPORT_UCD31XX,DMED,DS,DS_FLASH,DVT,ECLIPSE,EMU_BH,EMU_C2000,EMU_C2000_FLASH,EMU_HERCULES,EMU_TI,IDE,IDE_CHROME,IDE_GC,IDE_TOOLS_COMMON,INSTALLER,JRE,KEYSTONE2,MSP430_BUILD_DEBUG,MSP430_CGT_HELP,MSP430_GCC_SUPPORT,MSP432_BUILD_DEBUG,MSPM0,MSVC_REDIST_LATEST,NODEJS,P2APP,P2TOOLS,SEGGER_J_LINK,SEGGER_J_LINK_DRIVERS,SYSCONFIG,TARGETDB_DEF_PROPS,TARGET_CONTENT_CORE,TIREX,TIREX4,TIVA_STELLARIS_DRIVERS,TIVA_TM4C,TIVA_TM4E,TI_ARM_CLANG,USERGUIDE,core
    [16:46:20] PFsToBeInstalled:
    [16:46:20] Running in unattended mode, must validate system.
    [16:46:20] CCS_INFO: Running in unattended mode, must validate installdir c:/ti/ccs1240.
    [16:46:21] CCS_INFO: Testing c:/program files/ in install path c:/ti/ccs1240
    [16:46:21] CCS_INFO: Testing c:/program files \(x86\)/ in install path c:/ti/ccs1240
    [16:46:21] CCS_INFO: Testing c:/program files/ in install path c:/ti/ccs1240
    [16:46:22] Logdir = c:\ti\ccs1240/ccs/install_logs/20231019164617
    [16:46:22] CCS_INFO: CCStudio set to c:/ti/ccs1240/ccs/eclipse/ccstudio.exe
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    ti_msp430pack_header_files_setup_11.1.0_install.log

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    Log started 10/19/2023 at 16:49:21
    Preferred installation mode : unattended
    Trying to init installer in mode unattended
    Mode unattended successfully initialized
    [16:49:21] Error reading AppFolder property from c:/ti/ccs1240/ccs/eclipse/ccs.properties
    [16:49:21] Using default AppFolder property Texas Instruments/Code Composer Studio
    [16:49:21] eclipsedir = c:/ti/ccs1240/ccs/eclipse
    Preparing to Install
    Preparing to Install
    Creating directory C:\ti\ccs1240\ccs\ccs_base\msp430
    Creating directory C:\ti\ccs1240\ccs\ccs_base\msp430\include
    Creating directory C:\ti\ccs1240\ccs\ccs_base\msp430\lib
    Creating directory C:\ti\ccs1240\ccs\ccs_base\msp430\lib\4xx
    Creating directory C:\ti\ccs1240\ccs\ccs_base\msp430\lib\5xx_6xx_FRxx
    Creating directory C:\ti\ccs1240\ccs\ccs_base\msp430\lib\FR2xx
    Creating directory C:\ti\ccs1240\ccs\ccs_base\msp430\lib\FR57xx
    Creating directory C:\ti\ccs1240\ccs\ccs_base\msp430\lib\FR59xx
    Creating directory C:\ti\ccs1240\ccs\ccs_base\msp430\templates
    Creating directory C:\ti\ccs1240\ccs\ccs_base\msp430\templates\msp430_noport1
    Creating directory C:\ti\ccs1240\ccs\ccs_base\msp430\templates\msp430fr59xx
    Creating directory C:\ti\ccs1240\ccs\ccs_base\msp430\templates\msp430g20x0
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    ti_msp430pack_header_files11.1.0_install.log

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    Log started 10/19/2023 at 16:49:21
    Preferred installation mode : unattended
    Trying to init installer in mode unattended
    Mode unattended successfully initialized
    [16:49:21] Error reading AppFolder property from c:/ti/ccs1240/ccs/eclipse/ccs.properties
    [16:49:21] Using default AppFolder property Texas Instruments/Code Composer Studio
    [16:49:21] eclipsedir = c:/ti/ccs1240/ccs/eclipse
    Preparing to Install
    Preparing to Install
    Creating directory C:\ti\ccs1240\ccs\ccs_base\msp430
    Creating directory C:\ti\ccs1240\ccs\ccs_base\msp430\include
    Creating directory C:\ti\ccs1240\ccs\ccs_base\msp430\lib
    Creating directory C:\ti\ccs1240\ccs\ccs_base\msp430\lib\4xx
    Creating directory C:\ti\ccs1240\ccs\ccs_base\msp430\lib\5xx_6xx_FRxx
    Creating directory C:\ti\ccs1240\ccs\ccs_base\msp430\lib\FR2xx
    Creating directory C:\ti\ccs1240\ccs\ccs_base\msp430\lib\FR57xx
    Creating directory C:\ti\ccs1240\ccs\ccs_base\msp430\lib\FR59xx
    Creating directory C:\ti\ccs1240\ccs\ccs_base\msp430\templates
    Creating directory C:\ti\ccs1240\ccs\ccs_base\msp430\templates\msp430_noport1
    Creating directory C:\ti\ccs1240\ccs\ccs_base\msp430\templates\msp430fr59xx
    Creating directory C:\ti\ccs1240\ccs\ccs_base\msp430\templates\msp430g20x0
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    and finally ti_msp430pack11.1.0_install.log

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    Log started 10/19/2023 at 16:49:34
    Preferred installation mode : unattended
    Trying to init installer in mode unattended
    Mode unattended successfully initialized
    [16:49:34] Error reading AppFolder property from c:/ti/ccs1240/ccs/eclipse/ccs.properties
    [16:49:34] Using default AppFolder property Texas Instruments/Code Composer Studio
    [16:49:34] eclipsedir = c:/ti/ccs1240/ccs/eclipse
    Preparing to Install
    Preparing to Install
    Directory already exists: C:\ti\ccs1240\ccs\ccs_base\common
    Directory already exists: C:\ti\ccs1240\ccs\ccs_base\common\targetdb
    Creating directory C:\ti\ccs1240\ccs\ccs_base\common\targetdb\drivers
    Creating directory C:\ti\ccs1240\ccs\ccs_base\common\targetdb\drivers\TI_reg_ids
    Unpacking files
    Unpacking C:\ti\ccs1240\ccs\ccs_base\common\targetdb\drivers\msp430_emu.xml
    Unpacking C:\ti\ccs1240\ccs\ccs_base\common\targetdb\drivers\TI_reg_ids\MSP430_regids.xml
    Creating directory C:\ti\ccs1240\ccs\ccs_base\DebugServer
    Creating directory C:\ti\ccs1240\ccs\ccs_base\DebugServer\drivers
    Unpacking files
    Unpacking C:\ti\ccs1240\ccs\ccs_base\DebugServer\drivers\MSP430.dll
    Directory already exists: C:\ti\ccs1240\ccs\ccs_base\common
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • +1 in reply to kevin fry
    TI__Genius 9175 points

    Hi Kevin,

    So, somehow installing with the '--disable-components' flag ends up installing nothing but the C7000 family.  This could be a bug in CCS installer.

    Can you try using the '--enable-components' flag instead?  E.g. "--enable-components PF_MSPM0,PF_SITARA_MCU", and pick only the families that you need out of this list of available families:

    PF_MSP430,PF_MSP432,PF_MSPM0,PF_CC2X,PF_CC3X,PF_CC2538,PF_C28,PF_TM4C,PF_HERCULES,PF_SITARA,PF_SITARA_MCU,PF_OMAPL,PF_DAVINCI,PF_OMAP,PF_TDA_DRA,PF_C55,PF_C6000SC,PF_C66AK_KEYSTONE,PF_MMWAVE,PF_C64MC,PF_DIGITAL_POWER,PF_PGA

  • +1 in reply to Baltasar Belyavsky
    Prodigy 10 points

    Wow thank you so much, that workaround for the disable-components installer bug worked!

    I now have in the Dockerfile

    RUN ["powershell.exe", "Start-Process -FilePath 'ccs_setup_11.2.0.00007.exe' -ArgumentList '--mode unattended --enable-components PF_CC2X,PF_CC3X,PF_CC2538,PF_C28,PF_C55' -WorkingDirectory 'work/CCS11.2.0.00007_win64' -Wait"]

    It now installs CCS correctly with the arm stuff, and then picks up the compiler after I install it and run the toolDiscoveryPath command

    I appreciate the help