• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 54 subscribers
  • Views 1003 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: CCS 9.2.0.00013 fails to run installer for SEGGER J-Link Support

CCS: CCS 10.0.0.00010 under Linux fails to install SEGGER J-Link Support 6.56.0.0

Chester Gillon
Guru 92251 points

Tool/software: Code Composer Studio

Under Ubuntu 16.04.6 LTS performed the following:

a. Performed a fresh install of CCS 10.0.0.00010 using the offline installer selecting to install all components.

b. After the initial CSS 10 install, SEGGER J-Link Support 16.44.0.b was installed. And looking at the installed files showed the following related to jlink drivers (the final one which contains the version number in the filename)

mr_halfword@haswell-ubuntu:~/ti/ccs1000$ find . -name '*jlink*so*' -ls
7494701 15360 -rwxr-xr-x 1 mr_halfword mr_halfword 15726880 Mar 15 2019 ./ccs/ccs_base/DebugServer/drivers/libjlinkarm.so
7494702 15360 -rwxr-xr-x 1 mr_halfword mr_halfword 15726880 Mar 15 2019 ./ccs/ccs_base/DebugServer/drivers/libjlinkarm.so.6
7494703 15360 -rwxr-xr-x 1 mr_halfword mr_halfword 15726880 Mar 15 2019 ./ccs/ccs_base/DebugServer/drivers/libjlinkarm.so.6.44.2

c. After the fresh CCS 10 install, checking for updates showed SEGGER J-Link Support 6.56.0.0 available. Selected to update the SEGGER J-Link support and CCS re-started without any obvious error being reported.

d. After the update, the Help -> About Code Composer Studio -> Installation Details -> Installed Software reported that "SEGGER J-Link Support (Linux) 6.56.0.0 com.segger.jlink.linux.feature.group Texas Instruments" was installed. However, looking again at the installation showed the following files had not been changed:

mr_halfword@haswell-ubuntu:~/ti/ccs1000$ find . -name '*jlink*so*' -ls
7494701 15360 -rwxr-xr-x 1 mr_halfword mr_halfword 15726880 Mar 15 2019 ./ccs/ccs_base/DebugServer/drivers/libjlinkarm.so
7494702 15360 -rwxr-xr-x 1 mr_halfword mr_halfword 15726880 Mar 15 2019 ./ccs/ccs_base/DebugServer/drivers/libjlinkarm.so.6
7494703 15360 -rwxr-xr-x 1 mr_halfword mr_halfword 15726880 Mar 15 2019 ./ccs/ccs_base/DebugServer/drivers/libjlinkarm.so.6.44.2

I.e. this appears to be similar to the related question which was reported with CCS 9.3

This issue has only been seen with CCS 10 under Linux. Under Windows 10 the SEGGER J-Link Support 6.56.0.0 updated appears to have been performed successfully, based upon the version number reported in the ccs/ccs_base/DebugServer/drivers/JLink_X86.dll after the update.

  • 0
    TI__Guru**** 480241 points

    Hello Chester.

    I tried updating the J-Link support package to 6.56 with my CCSv10 installation on Ubuntu 18.04.4. I ran into the update issue you reported the other day. When using the workaround you mentioned, the rest of the installation appeared to proceed. When checking the installation, I saw:

    I have that additional last entry fpo 6.56.

    I did use a different Ubuntu version. I can try on mu 16.04 distro and see if I can reproduce there.

    Thanks

    ki

  • 0 in reply to Ki
    Guru 92251 points

    Ki said:
    I ran into the update issue you reported the other day. When using the workaround you mentioned, the rest of the installation appeared to proceed.

    I manually ran the ccs_update_10.0.0.00010.run in the ccs/eclipse/downloads directory and confirm that that updated the Segger J-Link support on a CCS 10 installation on both:

    a. The laptop running Ubuntu 16.04.6 LTS on which I reported this problem.

    b. A desktop running Ubuntu 18.04.4 LTS.

    Which resulted in the same files as your case:

    mr_halfword@Haswell-Ubuntu:~/ti/ccs1000$ find . -name '*jlink*so*' -ls
    57808042 16092 -rwxr-xr-x 1 mr_halfword mr_halfword 16475152 Nov 22 17:14 ./ccs/ccs_base/DebugServer/drivers/libjlinkarm.so.6
    57808041 16092 -rwxr-xr-x 1 mr_halfword mr_halfword 16475152 Nov 22 17:14 ./ccs/ccs_base/DebugServer/drivers/libjlinkarm.so
    57805962 16092 -rwxr-xr-x 1 mr_halfword mr_halfword 16475152 Nov 22 17:14 ./ccs/ccs_base/DebugServer/drivers/libjlinkarm.so.6.56.0
    57808043 15360 -rwxr-xr-x 1 mr_halfword mr_halfword 15726880 Mar 15 2019 ./ccs/ccs_base/DebugServer/drivers/libjlinkarm.so.6.44.2

    What I also found is that if the update fails to apply then ccs/eclipse/downloads directory contains com.segger.jlink.linux.linux.x86_64_manifest.xml and JLinkTICCSPlugin_Linux_6.56.0_x86_64.zip files, which get deleted after ccs_update_10.0.0.00010.run has been manually run.

  • 0 in reply to Chester Gillon
    TI__Guru**** 480241 points

    Chester Gillon said:
    a. The laptop running Ubuntu 16.04.6 LTS on which I reported this problem.

    I can reproduce this on Ubuntu 16.04.6 LTS. We are investigating.

    Thanks

    ki

  • 0 in reply to Ki
    Guru 92251 points

    Ki said:
    I have that additional last entry fpo 6.56.

    The other thing which looks odd compared to the standard Linux practice is that the libjlinkarm.so, libjlinkarm.so.6 and libjlinkarm.so.6.56.0 files are all copies of each other.

    Whereas if look back at a CCS 8.3 installation the libjlinkarm.so and libjlinkarm.so.6 are symlinks as per standard Linux practice:

    Presumably the move from using sym-links to copies happened when as per the original question the Segger J-Link update format was switched from .tar.gz to .zip format.

  • 0 in reply to Chester Gillon
    TI__Guru**** 480241 points

    Thanks for the additional data Chester. I will need to follow up with Segger since they create and post the updates for J-Link.