Unable to install new NCS from the Toolchain Manager

I get this error when I try to install the v2.5.0 version of the NCS from the toolchain manager.

There are multiple errors:

  • Failed to clone the repositories: Error: Cloning into 'C:\ncs\v2.5.0.west\manifest-tmp'... error: RPC failed; curl 18 transfer closed with outstanding read data remaining error: 3313 bytes of body are still expected fetch-pack: unexpected disconnect while reading sideband packet fatal: early EOF fatal: fetch-pack: invalid index-pack output FATAL ERROR: command exited with status 128: git clone --branch v2.5.0 github.com/.../sdk-nrf 'C:\ncs\v2.5.0.west\manifest-tmp' Error: Launched process exited with non-zero status: 128 Error: Subprocess C:\Users\Abdelali\AppData\Roaming\nrfconnect\nrfutil-sandboxes\toolchain-manager\0.14.1\bin\nrfutil-toolchain-manager.exe failed with unexpected exit code Some(128)

  • Error: Cloning into 'C:\ncs\v2.5.0.west\manifest-tmp'... error: RPC failed; curl 18 transfer closed with outstanding read data remaining error: 3313 bytes of body are still expected fetch-pack: unexpected disconnect while reading sideband packet fatal: early EOF fatal: fetch-pack: invalid index-pack output FATAL ERROR: command exited with status 128: git clone --branch v2.5.0 github.com/.../sdk-nrf 'C:\ncs\v2.5.0.west\manifest-tmp' Error: Launched process exited with non-zero status: 128 Error: Subprocess C:\Users\Abdelali\AppData\Roaming\nrfconnect\nrfutil-sandboxes\toolchain-manager\0.14.1\bin\nrfutil-toolchain-manager.exe failed with unexpected exit code Some(128)

  • Hello,

    The first thing I noticed was that the path set to clone into was weird: it's missing a slash between v2.5.0 and .west. It is not clear what the reason for this is, so please provide the following information:

    Does this error happen only for NCS v2.5.0?

    Are you able to install NCS v2.5.0 with other methods? I.e. from VS Code or manually from command line?

    Please create a system report from the ABOUT tab and share the contents with us.

    Best regards,

    Maria

  • Just today I was also facing the exact same issue while installing NCS v2.5.1. After a lot of struggle, I found that it was because of the firewall. My organization's security was not allowing this installation. After discussing this with the concerned person from IT, he helped me to resolve this issue by disabling the firewall temporarily. The installation went well then.

  • Hi Maria, Thanks for your inputs.

    For the questions:

    • This happens not only for the v2.5.0.

    Log for the trying with the 2.5.1

    [ There are multiple errors:
    Failed to clone the repositories: Error: Cloning into 'C:\ncs\v2.5.1.west\manifest-tmp'... fatal: unable to access 'github.com/.../': Failed to connect to github.com port 443 after 21113 ms: Timed out FATAL ERROR: command exited with status 128: git clone --branch v2.5.1 github.com/.../sdk-nrf 'C:\ncs\v2.5.1.west\manifest-tmp' Error: Launched process exited with non-zero status: 128 Error: Subprocess C:\Users\Abdelali\AppData\Roaming\nrfconnect\nrfutil-sandboxes\toolchain-manager\0.14.1\bin\nrfutil-toolchain-manager.exe failed with unexpected exit code Some(128)

    Error: Cloning into 'C:\ncs\v2.5.1.west\manifest-tmp'... fatal: unable to access 'github.com/.../': Failed to connect to github.com port 443 after 21113 ms: Timed out FATAL ERROR: command exited with status 128: git clone --branch v2.5.1 github.com/.../sdk-nrf 'C:\ncs\v2.5.1.west\manifest-tmp' Error: Launched process exited with non-zero status: 128 Error: Subprocess C:\Users\Abdelali\AppData\Roaming\nrfconnect\nrfutil-sandboxes\toolchain-manager\0.14.1\bin\nrfutil-toolchain-manager.exe failed with unexpected exit code Some(128) ]

    • Can't install that from VS Code too. Here's the output I get from there:

    [Command failed: west init -m github.com/.../sdk-nrf --mr v2.5.2
    Cloning into 'c:\ncs\v2.5.2\.west\manifest-tmp'...
    error: RPC failed; curl 18 transfer closed with outstanding read data remaining
    error: 628 bytes of body are still expected
    fetch-pack: unexpected disconnect while reading sideband packet
    fatal: early EOF
    fatal: fetch-pack: invalid index-pack output
    FATAL ERROR: command exited with status 128: git clone --branch v2.5.2 github.com/.../sdk-nrf 'c:\ncs\v2.5.2\.west\manifest-tmp']

    • Here's my system report:

    # nRFConnect System Report - 2024-02-01T22-13-59.993Z

    - System:     Dell Inc. Latitude 5490
    - BIOS:       Dell Inc. DELL   - 1072009
    - CPU:        1 x Intel CoreTm i5-8350U 1.7 GHz 8 cores (4 physical)
    - Memory:     398.2 MB free of 7.9 GB total
    - Filesystem: C: (NTFS) 237.3 GB 92.9% used

    - OS:         Microsoft Windows 10 Pro (10.0.19045) Windows x64

    - Versions
        - kernel: 10.0.19045
        - git: 2.43.0.windows.1
        - node: 16.17.1
        - python: 3.10.6
        - python3:
    - Connected devices:

    Thanks again,

    Abdelali

  • Thank you!

    I have tried to disable the default one on my Windows machine, but I still get the error.

  • Thank you for checking that the error occurs for several NCS releases.

    When searching for an explanation for it, I found that the error is from git, and it indicated a network issue. If your network connection is slow, cloning large repositories can end in a timeout which causes the error. This thread on Stack overflow has some solutions you can try. For a few people, the issue was resolved by upgrading their internet connection.

    rmptxf said:
    error: RPC failed; curl 18 transfer closed with outstanding read data remaining
    error: 628 bytes of body are still expected
    fetch-pack: unexpected disconnect while reading sideband packet
    fatal: early EOF
    fatal: fetch-pack: invalid index-pack output

    Searching for the above part of the error log may lead you to some other methods to solve your issue as well.

    I hope some of this helps you. There's not much we can do since the error is from git and the cause could be with your network.

    Also, I will also give a thank you to Prashant for sharing their solution in this thread. If more people in the DevZone community has solved a similar issue, please share your findings!

    Best regards,

    Maria

Related