• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 1033 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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 does not find SimpleLink when installed from command line

Alexander Eck-Zimmer
Prodigy 10 points
Other Parts Discussed in Thread: SYSCONFIG, CCSTUDIO

I am trying to install CCS + SimpleLink unattended in a Docker container. This should act as the container for automated CD/CI builds. So the goal is to install CCS12 and the necessary tools (.SIMPLELINK_CC13X2_26X2_SDK and sysconfig 1.8.0) in a container (without having a GUI) with a Linux OS.

The problem is that I cannot build my project because the SimpleLink SDK I used in the project would not be found by CCS, although I have installed and registered it,

First: I have read the standard pages over and over again which describe how CCS would "discover" things like the SimpleLink SDK:

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

https://software-dl.ti.com/ccs/esd/documents/ccs_projects-command-line.html#is-there-a-command-line-option-to-specify-a-path-for-a-new-discoverable-software-product-c2000ware-simplelink-sdk-etc-so-ccs-can-detect-it- 

So, I know how to register the "discovery path" so that CCS should detect the installed SimpleLink SDK.

If tried it more than one way:

1. install CSS12 in default directory (/root/ti/ccs1220/ccs/...) and install SimpleLink in default directory (/opt/ti)
2. install CSS12 in default directory (/root/ti/ccs1220/ccs/...) and install SimpleLink speecific directory and the register this folder as "discovery path" using:


$PATH_TO_CCS/ccs/eclipse/eclipse -nosplash -data /workspace/ -application com.ti.common.core.initialize -ccs.toolDiscoveryPath "/ccs/plugins"


Basically I did this over and over again, but cannot get CCS to recognize the SimpleLink SDK, no matter which variant I tried.

I know that it didn't work because:


1. the check with

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

would not display any SimpleLink SDK found.

2. the build fails with the message "Product com.ti.SIMPLELINK_CC13X2_26X2_SDK v5.10.0.48 is not currently installed and no compatible version is available."

So what could have gone wrong? I have no idea at the moment ...

Thanks for any hints!

  • 0
    TI__Guru**** 472261 points

    Hello,

    Alexander Eck-Zimmer said:
    $PATH_TO_CCS/ccs/eclipse/eclipse -nosplash -data /workspace/ -application com.ti.common.core.initialize -ccs.toolDiscoveryPath "/ccs/plugins"

     -ccs.toolDiscoveryPath is for discovering compilers

    -ccs.productDiscoveryPath is for products like SDKs.

    Please try using -ccs.productDiscoveryPath

    Thanks

    ki

  • +1 in reply to Ki
    Prodigy 10 points

    Thanks, that helped to some extend, but I had another flaw:

    I tried to install two "plugins" to CCS:

    • Sysconfig 1.8
    • Simplelink (simplelink_cc13x2_26x2_sdk_5_10_00_48)

    And even with your hint, I could only register Sysconfig, but Simplelink would just not show up.

    But I found out my mistake: I installed both (Sysconfig and Simplelink) into the same directory with:

    /tmp/simplelink_cc13x2_26x2_sdk_5_10_00_48.run --mode unattended --prefix /ccs/plugins
    /tmp/sysconfig-1.8.0_1863-setup.run --mode unattended --prefix /ccs/plugins

    I interpreted the "prefix" parameter as the "base folder" - and each tool would create its own subfolder in it. But instead it is exactly the directory into which the tool would be installed.

    So I ended up in both tools living with all their files in the same folder. Some files would apparently be overridden by each other - presumably exact the "metadata" file which CCS needs to recognize the tools, so CCS discovered only one of them.

    As soon as I installed each with its own "installation prefix", both have successfully registered via - Ki, again thanks! - the -ccs.productDiscoveryPath.

    So, problem solved!