• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 54 subscribers
  • Views 663 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: ccs10 , latest Segger Jlink archive corrupt

v01d
Expert 1965 points
Other Parts Discussed in Thread: SEGGER

Tool/software: Code Composer Studio

After installing CCS v10 with Segger probe selected, after first start it wants to upgrade the Segger probe drivers.

This fails, because the pulled archive is corrupt / not correctly formatted and thus CCS install / update of it fails.  Exact problem is :

file JLinkTICCSPlugin_Linux_6.82.2_x86_64.tar.gz
JLinkTICCSPlugin_Linux_6.82.2_x86_64.tar.gz: Zip archive data, at least v1.0 to extract

This is not a tar  (or gz) format, and the internal script which runs in side CCS which tries to upgrade/extract these files will /does fail because it expects a tar. This is what I see it's trying to do essentially:

gunzip -c  /opt/ti/ccs1010/ccs/eclipse/downloads/JLinkTICCSPlugin_Linux_6.82.2_x86_64.tar.gz |  7za x -si -ttar "-o/tmp/cs1010/ccs" -y

(Ignore /tmp path , thats me testig)

gunzip fails with : 

gunzip JLinkTICCSPlugin_Linux_6.82.2_x86_64.tar.gz
gzip: JLinkTICCSPlugin_Linux_6.82.2_x86_64.tar.gz has more than one entry -- unchanged

So whole update fails.

  • 0
    Guru 92251 points

    I can repeat this. I had a CCS 10.1 installation under Ubuntu in which Segger J-Link v6.56.0 was already installed.

    Trying to update to v6.82.2 failed with the following during the installation:

    Unable to unzip /home/mr_halfword/ti/ccs1010/ccs/eclipse/downloads/JLinkTICCSPlugin_Linux_6.82.2_x86_64.tar.gz: Error running /tmp/ccs_846f0b8b-1ea0-4ade-4d4c-7bcf4f464163/util/7za x -so "/home/mr_halfword/ti/ccs1010/ccs/eclipse/downloads/JLinkTICCSPlugin_Linux_6.82.2_x86_64.tar.gz" | /tmp/ccs_846f0b8b-1ea0-4ade-4d4c-7bcf4f464163/util/7za x -si -ttar "-o/home/mr_halfword/ti/ccs1010/ccs" -y:
    7-Zip (A) [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
    p7zip Version 9.20 (locale=en_GB.UTF-8,Utf16=on,HugeFiles=on,12 CPUs)

    Processing archive: /home/mr_halfword/ti/ccs1010/ccs/eclipse/downloads/JLinkTICCSPlugin_Linux_6.82.2_x86_64.tar.gz

    Extracting ccs_base
    Extracting ccs_base/DebugServer
    Extracting ccs_base/DebugServer/drivers
    Extracting ccs_base/DebugServer/drivers/libjlinkarm.so.6.82.2.
    Do you want to retry?

    It does appear to be a valid zip file:

    $ file  /home/mr_halfword/ti/ccs1010/ccs/eclipse/downloads/JLinkTICCSPlugin_Linux_6.82.2_x86_64.tar.gz
/home/mr_halfword/ti/ccs1010/ccs/eclipse/downloads/JLinkTICCSPlugin_Linux_6.82.2_x86_64.tar.gz: Zip archive data, at least v1.0 to extract
$ unzip -t /home/mr_halfword/ti/ccs1010/ccs/eclipse/downloads/JLinkTICCSPlugin_Linux_6.82.2_x86_64.tar.gz
Archive:  /home/mr_halfword/ti/ccs1010/ccs/eclipse/downloads/JLinkTICCSPlugin_Linux_6.82.2_x86_64.tar.gz
    testing: ccs_base/                OK
    testing: ccs_base/DebugServer/    OK
    testing: ccs_base/DebugServer/drivers/   OK
    testing: ccs_base/DebugServer/drivers/libjlinkarm.so.6.82.2   OK
    testing: ccs_base/DebugServer/drivers/JLINK2GTIAdapter.dvr   OK
    testing: ccs_base/DebugServer/drivers/libjlinkarm.so   OK
    testing: ccs_base/DebugServer/drivers/libjlinkarm.so.6   OK
    testing: ccs_base/common/         OK
    testing: ccs_base/common/targetdb/   OK
    testing: ccs_base/common/targetdb/connections/   OK
    testing: ccs_base/common/targetdb/connections/segger_j-link_connection.xml   OK
    testing: ccs_base/common/targetdb/drivers/   OK
    testing: ccs_base/common/targetdb/drivers/jlinkcs_dap.xml   OK
    testing: ccs_base/common/targetdb/drivers/jlinkcortexm3.xml   OK
    testing: ccs_base/common/targetdb/drivers/jlinkcortexr5.xml   OK
    testing: ccs_base/common/targetdb/drivers/jlink_pru.xml   OK
    testing: ccs_base/common/targetdb/drivers/JLINKetb11.xml   OK
    testing: ccs_base/common/targetdb/drivers/jlink_icepick_d.xml   OK
    testing: ccs_base/common/targetdb/drivers/jlinkcortexa8.xml   OK
    testing: ccs_base/common/targetdb/drivers/jlink_csstm.xml   OK
    testing: ccs_base/common/targetdb/drivers/jlinkc64xp.xml   OK
    testing: ccs_base/common/targetdb/drivers/jlinkdap_pc.xml   OK
    testing: ccs_base/common/targetdb/drivers/JLINKicepick_c.xml   OK
    testing: ccs_base/common/targetdb/drivers/jlinkcortexr4.xml   OK
    testing: ccs_base/common/targetdb/drivers/jlink_scriptfiles/   OK
    testing: ccs_base/common/targetdb/drivers/jlink_scriptfiles/OMAP-L138.JLinkScript   OK
    testing: ccs_base/common/targetdb/drivers/jlink_scriptfiles/AM3517.JLinkScript   OK
    testing: ccs_base/common/targetdb/drivers/jlink_scriptfiles/ScriptBeagleBoard_OMAP3530.JLinkScript   OK
    testing: ccs_base/common/targetdb/drivers/jlink_scriptfiles/TMS570.JLinkScript   OK
    testing: ccs_base/common/targetdb/drivers/jlink_scriptfiles/AM3715.JLinkScript   OK
    testing: ccs_base/common/targetdb/drivers/jlink_scriptfiles/TMS470M.JLinkScript   OK
    testing: ccs_base/common/targetdb/drivers/jlink_scriptfiles/am180x.JLinkScript   OK
    testing: ccs_base/common/targetdb/drivers/jlink_scriptfiles/am170x.JLinkScript   OK
    testing: ccs_base/common/targetdb/drivers/jlink_scriptfiles/OMAP4430_CortexA9.JLinkScript   OK
    testing: ccs_base/common/targetdb/drivers/jlinketbcs.xml   OK
    testing: ccs_base/common/targetdb/drivers/jlinkcortexm4.xml   OK
    testing: ccs_base/common/targetdb/drivers/jlinkcs_child.xml   OK
    testing: ccs_base/common/targetdb/timestamp   OK
No errors detected in compressed data of /home/mr_halfword/ti/ccs1010/ccs/eclipse/downloads/JLinkTICCSPlugin_Linux_6.82.2_x86_64.tar.gz.

    I will try the work-around suggested in CCS: CCS 9.2.0.00013 fails to run installer for SEGGER J-Link Support which is to manually extract the archive into the CCS installation.

  • 0 in reply to Chester Gillon
    Guru 92251 points

    Manually extracting the archive worked:

    mr_halfword@Haswell-Ubuntu:~$ cd ~/ti/ccs1010/ccs
mr_halfword@Haswell-Ubuntu:~/ti/ccs1010/ccs$ unzip eclipse/downloads/JLinkTICCSPlugin_Linux_6.82.2_x86_64.tar.gz
Archive:  eclipse/downloads/JLinkTICCSPlugin_Linux_6.82.2_x86_64.tar.gz
  inflating: ccs_base/DebugServer/drivers/libjlinkarm.so.6.82.2  
replace ccs_base/DebugServer/drivers/JLINK2GTIAdapter.dvr? [y]es, [n]o, [A]ll, [N]one, [r]ename: y
  inflating: ccs_base/DebugServer/drivers/JLINK2GTIAdapter.dvr  
replace ccs_base/DebugServer/drivers/libjlinkarm.so? [y]es, [n]o, [A]ll, [N]one, [r]ename: y
  inflating: ccs_base/DebugServer/drivers/libjlinkarm.so  
replace ccs_base/DebugServer/drivers/libjlinkarm.so.6? [y]es, [n]o, [A]ll, [N]one, [r]ename: y
  inflating: ccs_base/DebugServer/drivers/libjlinkarm.so.6  
replace ccs_base/common/targetdb/connections/segger_j-link_connection.xml? [y]es, [n]o, [A]ll, [N]one, [r]ename: y
  inflating: ccs_base/common/targetdb/connections/segger_j-link_connection.xml  
replace ccs_base/common/targetdb/drivers/jlinkcs_dap.xml? [y]es, [n]o, [A]ll, [N]one, [r]ename: y
  inflating: ccs_base/common/targetdb/drivers/jlinkcs_dap.xml  
replace ccs_base/common/targetdb/drivers/jlinkcortexm3.xml? [y]es, [n]o, [A]ll, [N]one, [r]ename: y
  inflating: ccs_base/common/targetdb/drivers/jlinkcortexm3.xml  
replace ccs_base/common/targetdb/drivers/jlinkcortexr5.xml? [y]es, [n]o, [A]ll, [N]one, [r]ename: y
  inflating: ccs_base/common/targetdb/drivers/jlinkcortexr5.xml  
replace ccs_base/common/targetdb/drivers/jlink_pru.xml? [y]es, [n]o, [A]ll, [N]one, [r]ename: y
  inflating: ccs_base/common/targetdb/drivers/jlink_pru.xml  
replace ccs_base/common/targetdb/drivers/JLINKetb11.xml? [y]es, [n]o, [A]ll, [N]one, [r]ename: y
  inflating: ccs_base/common/targetdb/drivers/JLINKetb11.xml  
replace ccs_base/common/targetdb/drivers/jlink_icepick_d.xml? [y]es, [n]o, [A]ll, [N]one, [r]ename: y
  inflating: ccs_base/common/targetdb/drivers/jlink_icepick_d.xml  
replace ccs_base/common/targetdb/drivers/jlinkcortexa8.xml? [y]es, [n]o, [A]ll, [N]one, [r]ename: y
  inflating: ccs_base/common/targetdb/drivers/jlinkcortexa8.xml  
replace ccs_base/common/targetdb/drivers/jlink_csstm.xml? [y]es, [n]o, [A]ll, [N]one, [r]ename: y
  inflating: ccs_base/common/targetdb/drivers/jlink_csstm.xml  
replace ccs_base/common/targetdb/drivers/jlinkc64xp.xml? [y]es, [n]o, [A]ll, [N]one, [r]ename: y
  inflating: ccs_base/common/targetdb/drivers/jlinkc64xp.xml  
replace ccs_base/common/targetdb/drivers/jlinkdap_pc.xml? [y]es, [n]o, [A]ll, [N]one, [r]ename: y
  inflating: ccs_base/common/targetdb/drivers/jlinkdap_pc.xml  
replace ccs_base/common/targetdb/drivers/JLINKicepick_c.xml? [y]es, [n]o, [A]ll, [N]one, [r]ename: y
  inflating: ccs_base/common/targetdb/drivers/JLINKicepick_c.xml  
replace ccs_base/common/targetdb/drivers/jlinkcortexr4.xml? [y]es, [n]o, [A]ll, [N]one, [r]ename: y
  inflating: ccs_base/common/targetdb/drivers/jlinkcortexr4.xml  
replace ccs_base/common/targetdb/drivers/jlink_scriptfiles/OMAP-L138.JLinkScript? [y]es, [n]o, [A]ll, [N]one, [r]ename: A
  inflating: ccs_base/common/targetdb/drivers/jlink_scriptfiles/OMAP-L138.JLinkScript  
  inflating: ccs_base/common/targetdb/drivers/jlink_scriptfiles/AM3517.JLinkScript  
  inflating: ccs_base/common/targetdb/drivers/jlink_scriptfiles/ScriptBeagleBoard_OMAP3530.JLinkScript  
  inflating: ccs_base/common/targetdb/drivers/jlink_scriptfiles/TMS570.JLinkScript  
  inflating: ccs_base/common/targetdb/drivers/jlink_scriptfiles/AM3715.JLinkScript  
  inflating: ccs_base/common/targetdb/drivers/jlink_scriptfiles/TMS470M.JLinkScript  
  inflating: ccs_base/common/targetdb/drivers/jlink_scriptfiles/am180x.JLinkScript  
  inflating: ccs_base/common/targetdb/drivers/jlink_scriptfiles/am170x.JLinkScript  
  inflating: ccs_base/common/targetdb/drivers/jlink_scriptfiles/OMAP4430_CortexA9.JLinkScript  
  inflating: ccs_base/common/targetdb/drivers/jlinketbcs.xml  
  inflating: ccs_base/common/targetdb/drivers/jlinkcortexm4.xml  
  inflating: ccs_base/common/targetdb/drivers/jlinkcs_child.xml  
 extracting: ccs_base/common/targetdb/timestamp

  • 0 in reply to Chester Gillon
    Expert 1965 points

    I think the key to note for TI here is , wrongly formatted and/or identified file and wrong tool they trying to use for it.   

    I also was able to use unzip on it before posting, but did want to note it's broken.

    So, either use properly formatted *.tar.gz with gunzip or tar, or  may be switch to zip / unzip.

    Also, it's a bit strange that, after failed update, next time CCS starts it "thinks" update succeeded and there was no need to re-try / no update pending.
    It was showing that latest Segger JLink was installed , even with failed un-archiving above.

  • 0 in reply to v01d
    TI__Guru**** 434511 points

    v01d said:
    I think the key to note for TI here is , wrongly formatted and/or identified file and wrong tool they trying to use for it.   

    Yes, agreed. We are investing. Thank you for reporting this issue

    ki

  • 0 in reply to v01d
    Guru 92251 points

    v01d said:
    Also, it's a bit strange that, after failed update, next time CCS starts it "thinks" update succeeded and there was no need to re-try / no update pending.

    Agreed.

    I found that when attempted to install another set of updates, to the compilers, at that point CCS tried and again failed to install the J-Link update.

    v01d said:
    It was showing that latest Segger JLink was installed , even with failed un-archiving above.

    Not sure if that is due to the standard way Eclipse handles updates, or if the CCS installer can be enhanced to better handle failed updates, e.g. to provide a way to roll-back to the previous version of the affected files.

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

    Update: We are working with Segger to resolve this. It appears to be a packaging error om their end.

    Thanks

    ki

  • 0 in reply to Ki
    TI__Guru**** 434511 points

    Ki said:
    Update: We are working with Segger to resolve this. It appears to be a packaging error om their end.

    SEGGER has addressed the issue in v6.82d. See the release note: https://www.segger.com/downloads/jlink/ReleaseNotes_JLink.html

    Thanks

    ki

  • 0 in reply to Ki
    Guru 92251 points

    Ki said:
    SEGGER has addressed the issue in v6.82d.

    CCS 10.1 under Linux showed there was an update for SEGGER J-Link Support (Linux) 6.82.4.0, which was installed without error.

  • 0 in reply to Ki
    Expert 1965 points

    Thank you indeed & nice to know.

    (Btw, it's not once now I've directly complained to Segger about their package management, for Linux.  They do get that wrong, few times now.  (I'm referring to Linux package management archives such as rpm))