• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 52 subscribers
  • Views 1202 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.

Original question:

CCS/SIMPLELINK-CC13X0-SDK: How to add simplelink sdk installation?

CCS/CC2640R2F: Specify location of SimpleLink SDK

Hans Jorgensen
Prodigy 50 points

Part Number: CC2640R2F

Tool/software: Code Composer Studio

Hi,

I have a setup with a build server that checks out the project including the "simplelink_cc2640r2_sdk_3_20_00_21" as it has been customized to our own board, the last checkout location of the SDK was “C:/agent/_work/16/s/BLE/packages”

As of default CCS looks for the SDK in “c:\ti” according to the Product discovery path resulting in following error:
"Product 'SimpleLink CC2640R2 SDK' v3.20.0.21 is not currently installed and no compatible version is available"

As the checkout path could change from time, I do not like the solution of just adding the checkout location to the product discovery path, so my question is:

- Is there a way to specify the SDK location relative to the project instead of using the Product discovery path
- Can I supply an option for the headless build that change the Product discovery path or the SDK location?

I can always copy the SDK to the "C:\ti" before executing the build but that will not allowing me to run 2 builds in parallel, so another solution would be prefered.

Hans

CCS 8.1.0.00011

  • 0
    TI__Guru**** 173310 points

    I believe this FAQ answers your question. Let us know if that does not help. 


  • 0 in reply to AartiG
    Prodigy 50 points

    It is closer to the solution but I still have issues after running the following command from a batch script

    call eclipsec -nosplash -data %sourcedir% -application com.ti.common.core.initialize -rtsc.productDiscoveryPath "%sourcedir%package

    Take a look at the picture below

    The path is added, but BLE/test also contains 3.20.0.21 and it seems to takes priority over the newly added path,
    Can I somehow clear the existing Product discovery path before adding the new one?

    Also i can not find the documentation for running -application com.ti.common.core.initialize except for the FAQ which was refered to in previuse reply.

  • 0 in reply to Hans Jorgensen
    TI__Guru**** 173310 points

    Hans Jorgensen said:
    The path is added, but BLE/test also contains 3.20.0.21 and it seems to takes priority over the newly added path,

    That is correct. If the discovery paths detect two copies of the same version only one of them will be discovered/installed. 

    Hans Jorgensen said:
    Can I somehow clear the existing Product discovery path before adding the new one?

    You can do it from the GUI (deselect the discovery path) but I don't believe there is a way to do this from command line. 

    However, it appears that your SDK is installed to a directory within your workspace directory, is that so? If so, I would instead advise keeping them in separate locations. That way you can perform the initialize command and set up discovery paths at a per workspace level. In other words, start with a clean workspace that has nothing but the two default discovery paths (highlighted in yellow) and add just the desired product discovery path.

    Hans Jorgensen said:
    Also i can not find the documentation for running -application com.ti.common.core.initialize except for the FAQ which was refered to in previuse reply.

    Sorry but we currently do not have any published documentation on this. I will discuss with the expert if we can put something together in the future.

  • 0 in reply to AartiG
    Prodigy 50 points

    AartiG said:
    However, it appears that your SDK is installed to a directory within your workspace directory, is that so? If so, I would instead advise keeping them in separate locations. That way you can perform the initialize command and set up discovery paths at a per workspace level. In other words, start with a clean workspace that has nothing but the two default discovery paths (highlighted in yellow) and add just the desired product discovery path.

    It appears as if the search path is not related to the workspace, but instead the tool itself (CCS 8.1.0). When creating a new empty workspace it already includes the search paths.

    I think I will go for the solution with copying the SDK from git to the C:\ti folder.