• State
  • Locked Locked
  • Replies 9 replies
  • Subscribers 53 subscribers
  • Views 2454 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.

Original question:

CCS/CC2640: CCS 8.2 installer ccs_setup_8.2.0.00007 hangs at "Downloading all features"

CCS/EVMK2H: CCS 8.2 Windows online installer ccs_setup_8.2.0.00007 hangs at "Downloading all features"

Chester Gillon
Guru 92251 points

Part Number: EVMK2H

Tool/software: Code Composer Studio

I have having the same problem at the related thread running the CCS 8.2.0.00007 online installer on Windows 10 Pro (version 1803 OS build 17134.320).

I have tried three installs, which all hung when the CCS installer gets to "Downloading all features". I have now left the installer running for over an hour, and it isn't making any progress apart from outputting a period character every so often.

Notes:

1. Windows Defender real time protection is running on the PC.

2. When the installer starts I get a pop-up from the Windows Defender asking if to allow tclsh.exe through the firewall and I granted permission.

3. After the installer had hung the netstat program reports that eclipsec.exe has a port in the CLOSE_WAIT state:

C:\Windows\system32>netstat /b /n

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    192.168.0.3:49673      40.67.251.132:443      ESTABLISHED
  WpnService
 [svchost.exe]
  TCP    192.168.0.3:49698      40.67.251.132:443      ESTABLISHED
 [OneDrive.exe]
  TCP    192.168.0.3:50649      23.195.139.170:443     CLOSE_WAIT
 [eclipsec.exe]
  TCP    192.168.0.3:50946      52.138.216.83:443      TIME_WAIT

The reported IP address 23.195.137.170 is for one of the servers which I think TI uses for downloads:

C:\Windows\system32>nslookup.exe 23.195.137.170
Server:  dsldevice.lan
Address:  192.168.0.1

Name:    a23-195-137-170.deploy.static.akamaitechnologies.com
Address:  23.195.137.170

4. Wireshark was left running during the install attempt. The traffic on connection eclipsec.exe has to 23.195.137.170 was the following:

It looks like after approx 370 seconds of inactivity on the TCP connection that the server closes the connection, leaving the socket in CLOSE_WAIT state as the eclipsec.exe program hasn't detected the server has close the connection.

I think this points at a bug in the eclipsec.exe installer, as opposed to the Windows defender firewall blocking the connection.

The install_logs directory from the hung online installer is attached 0647.install_logs.zip

I will now try the offline installer.

  • 0
    Guru 92251 points

    The offline installer was successful. I left the Windows defender real-time scanning enabled during the successful offline install.

  • 0
    TI__Mastermind 22060 points

    Hi Chester,

    Is it possible for you to do a test installation for us, reproducing the web installer issue? Please install in a different directory so as not to affect your actual install.

    If you can, please do the following:

    Open a cmd prompt as admin.

    Run the cmd below

    ccs_setup_8.2.0.00007.exe --test true

    Let it run till it hangs.

    cd to your temp folder, look for the latest ccs_<guid> folder.  Zip up the workspace and configuration folder from there and post here.

    Thank you for your help,

    Danish

  • 0 in reply to danishinnis
    Guru 92251 points

    danishinnis said:

    Run the cmd below

    ccs_setup_8.2.0.00007.exe --test true

    Let it run till it hangs.

    I don't have access to the original Windows 10 Pro PC at the moment, so I tried that on a different Windows 10 Home PC. Rather than hanging, this PC failed with an error while "Downloading all features":

    The attached zip file contains the configuration and workspace directories after the above error. configuration.zip

    I will be able to repeat the test on the original Windows 10 Pro PC at the weekend.

  • 0 in reply to Chester Gillon
    TI__Mastermind 22060 points
    Thanks Chester. This installation failed during the download due to repository timeouts, but it doesn't have anything to do with the original issue. I appreciate your trying the install on a weekend!
  • 0 in reply to danishinnis
    Guru 92251 points

    danishinnis said:

    Run the cmd below

    ccs_setup_8.2.0.00007.exe --test true

    Let it run till it hangs.

    OK, I have done that on the original Windows 10 Pro PC on which saw the problem. The installer hung while "Downloading all features". At the point the installer hung, as indicated by the Windows Task Manager reporting zero percent CPU, the ccsv8\eclipse\downloads directory in the installation directory contained 597 MB.

    The attached zip file contains the configuration and workspace directories after the installer had hung. 1856.configuration.zip

  • 0 in reply to Chester Gillon
    TI__Mastermind 22060 points
    Hi Chester,
    Thank you for trying this out. Did you get the configuration and workspace from the %TEMP%\ccs_<guid> folder?
    Danish
  • 0 in reply to danishinnis
    Guru 92251 points

    danishinnis said:
    Did you get the configuration and workspace from the %TEMP%\ccs_<guid> folder?

    Yes.

    After one hang of the online installer the configuration directory was empty. On the second attempt, for which the files were attached, the configuration and workspace directories were populated.

  • 0 in reply to Chester Gillon
    TI__Mastermind 22060 points

    Hmm, there was no log file generated (normally, there's a .log file in the .metadata folder). Is it possible that you didn't grab that? That would tell us why the eclipse call is hanging (I think).

  • 0 in reply to danishinnis
    Guru 92251 points

    danishinnis said:
    Hmm, there was no log file generated (normally, there's a .log file in the .metadata folder). Is it possible that you didn't grab that?

    I checked, and the ccs_<guid>\workspace\.metadata directory created during the failed Windows 10 online ccs_setup_8.2.0.00007.exe doesn't contain a .log file.

    The online ccs_setup_8.2.0.00007.exe was originally failing on a new Windows 10 Pro PC in which no previous CCS versions had been installed. The online ccs_setup_8.2.0.00007.exe was tried on another Windows 10 Pro PC in which had previously successfully run the online installer for previous CCS 7 or CCS 8 releases and, and online ccs_setup_8.2.0.00007.exe is also hanging at the "Downloading all features" on the other Windows 10 Pro PC.

    Looking at installer with Process Explorer shows the process tree:

    ccs_setup_8.2.0.00007.exe
     \__ tclsh.exe
          \__ eclipsec.exe

    Where eclipsec.exe is used to download the CCS features.

    There seems to be two failure modes:

    a. eclipsec.exe runs to completion and exits, and the CCS Installer GUI hangs on "Download all features" with only a few period characters displayed.

    b. eclipsec.exe hangs with a some sockets in the CLOSE_WAIT state, and the CCS Installer GUI remains at "Download all features" but outputting period characters at a regular interval.

    In the CCS ccs_setup_8.2.0.00007.exe online installer has there been any changes in the setup programs compared to previous CCS releases?