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: Console install of products does not work anymore with CCS 10.4.0

Part Number: CODECOMPOSER

Hi

So up til now I could install extensions (in this example the mmwave SDK) using

%CCS_EXE% -noSplash -data %QUM_DIR% -application com.ti.common.core.initialize -rtsc.productDiscoveryPath "%QUM_TI_DIR%\mmwave_sdk_03_05_00_04"

For our purposes we had to recompile some of the SDK libraries and hence have moved the SDK onto our own git repo. With the latest version of CCS the installation of such a product does not work anymore.

Even though the command ends successful

!ENTRY com.ti.common.core 1 0 2021-07-12 14:05:50.980
!MESSAGE path=ccs_base/DebugServer

!ENTRY com.ti.common.core 1 0 2021-07-12 14:05:50.980
!MESSAGE debugServerDir=C:/ti/ccs1040/ccs/ccs_base/DebugServer

Searching for deleted extension-sites to uninstall:
        Finished!

Searching for new extension-sites to install:
        Finished!

In my project I get the message that "Product XXX is not currently installed and no compatible version is available. Please install this product or a compatible version.". Even if I add the path manually in CCS it does not recognize the product (the SDK in this case). This was working seamlessly in previous versions.

How can I now install/add changed products (such as an SDK, which evidently needs some modification sometimes)?

  • Hello,

    This should still work in 10.4 I tried it out myself and it worked as expected. 

    If you check the list of discovered products in CCS, do you see both the path to the SDK and the desired version appear?

    If not, can you check to see if the .metadata folder still exists in the root SDK directory?

    Thanks

    ki

  • Hi

    Thanks for testing. I managed to get it working with mmwave_sdk_03_05_00_04 but only if I do not change libs. So I changed some code in uart, spi and other libs and compiled them. When I then push to git and clone somewhere else I can not install the package anymore. With a clean copy of the package it works. However, it does not work with bios_6_73_01_01 at all when I have pulled it from the remote repo.

    My steps are as follows:
    1) setup ccs project and include libs (I download bios and other packages from TI)
    2) initialize git repo
    3) git push of everything including lib/bios_6_73_01_01 (and other packages in lib/*)

    4) on another instance I checkout the git repo with a clean install of CCS. I then run above command for all the packages in the lib folder (lib/*) and expect them to be installed in the fresh CCS instance. I then import the project and expect it to work as on the initial instance (steps 1-3). However, the bios package can not be installed. It seems like a) CCS does some local compilation/installation outside of the project directories when I install bios on the first instance, and hence I am missing some files to be pushed on the Git repo.

    (see my other question here: Tampered Package. I posed the question here because initially I had the same issue with mmwave_sdk_03_05_00_04, and still do once I change and recompile some of its libs.)

    It seems like the package installer of ccs command line does not allow changed packages (which is weird because more often than not people might want to change some libs or processing?)

  • mmwave_sdk_03_05_00_04 but only if I do not change libs. So I changed some code in uart, spi and other libs and compiled them. When I then push to git and clone somewhere else I can not install the package anymore. With a clean copy of the package it works.

    The clean copy that works... is that also if pushed to git and cloned somewhere else? Will that still work as long as the package is not modified?

  • exactly. with SDK it is the case. i can push to remote and clone somewhere else and successfully install. but only if i have not touched SDK.
    same does apply for most other packages i tried (dsplib, matlib, xdctools, ...) except BIOS.

  • Thanks. I will need to set up a git environment to try this on. I'll keep you posted of any updates here.

  • Would it be possible to zip up one of the packages that cannot be detected and provide that to me (maybe shared via google drive or something similar)? Preferably one of the smaller packages. If this is ok, please start a private E2E conversation with me.

    Thanks

    ki