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/CCSTUDIO: Command line install products TivaC and XDC Tools

Part Number: CCSTUDIO

Tool/software: Code Composer Studio

I am trying to create a script to set up a development environment for my team, but am running into a problem where I can't figure out how to get CCS 10.1.0 to recognize products I've already installed on Windows. I have TivaC 2.16.01.14 installed at C:\ti\tirtos_tivac_2_16_01_14 and XDC Tools 3.32.00.06 installed at C:\ti\xdctools_3_32_00_06_core. When I try to build the project I have already imported into my workspace I get the following error:

PS C:\src\MyProject> .\Scripts\Cmd\EclipseBuild.bat

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
CCS headless build starting... [Thu Jul 09 08:34:48 CDT 2020]
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

================================================================================
Pre processing...


================================================================================
Building...


**** Build Finished ****
Buildfile generation error occurred..
Product com.ti.rtsc.TIRTOStivac v2.16.1.14 is not currently installed and no compatible version is available. Please install this product or a compatible version.
Build stopped..


================================================================================
CCS headless build complete! 1 out of 1 projects have errors.

The only way I know how to resolve this is by manually opening the project in the CCS GUI, opening Window > Preferences, navigating to Code Composer Studio > Products, clicking on the Refresh button, and selecting the two products it discovers in the locations I mentioned above.

How can I get CCS to recognize these installed products without requiring a human to open the CCS GUI?

  • I did come across that in my research and tried it, but it didn't do anything for me. Is the expected result from using that command that those products will be displayed under the Discovered products when you go to Windows > Preferences and navigate to Code Composer Studio > Products?

    When I executed that command I got the following output:

    PS C:\src\MyProject> eclipsec.exe -noSplash -data "C:\Users\Me\workspace_v10" -application com.ti.common.core.initialize -rtsc.productDiscoveryPath "C:\ti\tirtos_tivac_2_16_01_14;C:\ti\xdctools_3_32_00_06_core"

    Searching for deleted extension-sites to uninstall:
    Finished!

    Searching for new extension-sites to install:
    Finished!

    Then I executed my script and got the same error as I had in my post.

    When I manually opened the CCS GUI and look at the Windows > Preferences > Code Composer Studio > Products I do not see those two paths added under Product discovery path. As far as I can tell there is no typo in my command and I can confirm I'm opening CCS using the same workspace path.

    Should I expect to see those show up? Is there something else I can do to show more debug output to help troubleshoot this?

  • Erich Schroeter said:
    . Is the expected result from using that command that those products will be displayed under the Discovered products when you go to Windows > Preferences and navigate to Code Composer Studio > Products?

    Yes.

    Erich Schroeter said:
    Searching for new extension-sites to install:
    Finished!

    Assuming that the products were not discovered before, I would expect some additional messages about extension site for each product being discovered like in my example below:

    Those messages would not appear if they are already discovered by CCS

    Erich Schroeter said:
    When I manually opened the CCS GUI and look at the Windows > Preferences > Code Composer Studio > Products I do not see those two paths added under Product discovery path.

    They would not show up in the discovery search path but should appear in the discovered products list like so:

    can you try pressing the "Refresh" button to auto search? When you get the list to install, press the "Not Now" button to decline installing anything. However, this action may refresh the discovered products list. See if the missing products appear. I don't think this will work since your build fails but it is worth a try to rule it out.

    Thanks

    ki

  • Oh good lord, thank you for including that screenshot of your command prompt! Without it I wouldn't have tried executing my script in Command Prompt, because I've been using PowerShell to execute everything. I get the same result as you when I execute the command in a Command Prompt.

    Now, do you happen to know why that is? It's not important necessarily for resolving this issue, but it would be nice to know why eclipsec appears to silently fail when executing via PowerShell and now Command Prompt.

    EDIT:

    I may have prematurely clicked the resolve button. I still needed to manually open CCS GUI and click the Refresh in Windows > Preferences > Code Composer Studio > Products for my version of XDCtools (3.32.00.06) to be recognized. Without doing that it appeared to keep the default XDCtools (3.61.2.27) and the building failed.

  • Erich Schroeter said:
    I may have prematurely clicked the resolve button. I still needed to manually open CCS GUI and click the Refresh in Windows > Preferences > Code Composer Studio > Products for my version of XDCtools (3.32.00.06) to be recognized. Without doing that it appeared to keep the default XDCtools (3.61.2.27) and the building failed.

    Does that only happen with the XDCtools package? Or do you have the same issue with TI-RTOS?

  • As far as I can tell only the XDCtools package, because before I click the Refresh button the TI-RTOS for TivaC v2.16.1.14 shows up and the XDCtools only shows 3.61.2.27_core. After I click the Refresh button the XDCtools 3.32.0.06_core shows up. I can then close out of the CCS GUI and run my script and it succeeds.

  • Ok, I think there is some issue with XDCtools. I see the same issue with the package. Not sure it is that specific version or all XDCtools. I'll have to investigate further...

  • I tried a few version of XDCtools. It looks like there is some limitation there. I'll need to escalate to engineering

  • Ki said:
    I tried a few version of XDCtools. It looks like there is some limitation there. I'll need to escalate to engineering

    Turns out that it is a known issue. It will be fixed in the upcoming CCS 10.2.0 release planned later this year. Sorry for the inconvenience.

    ki

  • Ok, thanks! I'll mark this as resolved after I verify it when 10.2.0 gets released.