VS Code can't clone nrf connect SDK

I am learning development with nrf connect sdk. I installed vs code and in vs code downloaded the nrf connect for vs code extension pack, everything downloads well. On the nrf connect extension menu I go to download toolchain and the toolchain installs okay. but then downloading SDK always throws this error.

The error codes are as follows

 

[00:39:13] Command failed: west init -m https://github.com/nrfconnect/sdk-nrf --mr v2.4.2
Cloning into 'c:\ncs\v2.4.2\.west\manifest-tmp'...
error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: CANCEL (err 8)
error: 4674 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.4.2 https://github.com/nrfconnect/sdk-nrf 'c:\ncs\v2.4.2\.west\manifest-tmp'

Please help I am stuck on this for 2 days now.
Thanks in advance.

Parents
  • Hi Syed, 
    I'm not sure why you get the error. But a quick search pointed me to this video: https://www.youtube.com/watch?v=UFhiF3IzbUw

    The poster has the same issue as yours and he managed to get around by using a different network. 

    In your case it seems that you had the same issue even with a different network ? 

    Could you try to test using nRF Connect for Desktop -> Toolchain manager ? 

    If you do installing manually, at which step did it stop ?

  • Is it possible that someone else download this for and then make a zip file of the ncs folder and share with me. and I then extract the file in my C:\ folder, will this work with VS code nrf connect extension?

  • well this time it passed the west init line but now it gives error on west update.

    c:\ncs>west init -m https://github.com/nrfconnect/sdk-nrf --mr v2.5.0
    === Initializing in c:\ncs
    --- Cloning manifest repository from https://github.com/nrfconnect/sdk-nrf, rev. v2.5.0
    Cloning into 'c:\ncs\.west\manifest-tmp'...
    remote: Enumerating objects: 200532, done.
    remote: Counting objects: 100% (140/140), done.
    remote: Compressing objects: 100% (82/82), done.
    remote: Total 200532 (delta 61), reused 116 (delta 58), pack-reused 200392
    Receiving objects: 100% (200532/200532), 133.38 MiB | 450.00 KiB/s, done.
    
    Resolving deltas: 100% (150050/150050), done.
    Note: switching to '1fae141fc6713dd331b797fc96c90dc84552242d'.
    
    You are in 'detached HEAD' state. You can look around, make experimental
    changes and commit them, and you can discard any commits you make in this
    state without impacting any branches by switching back to a branch.
    
    If you want to create a new branch to retain commits you create, you may
    do so (now or later) by using -c with the switch command. Example:
    
      git switch -c <new-branch-name>
    
    Or undo this operation with:
    
      git switch -
    
    Turn off this advice by setting config variable advice.detachedHead to false
    
    Updating files: 100% (8085/8085), done.
    --- setting manifest.path to nrf
    === Initialized. Now run "west update" inside c:\ncs.
    
    c:\ncs>west update
    === updating zephyr (zephyr):
    --- zephyr: initializing
    Initialized empty Git repository in C:/ncs/zephyr/.git/
    --- zephyr: fetching, need revision v3.4.99-ncs1
    remote: Enumerating objects: 927552, done.
    remote: Counting objects: 100% (92/92), done.
    remote: Compressing objects: 100% (58/58), done.
    error: RPC failed; curl 92 HTTP/2 stream 5 was not closed cleanly: CANCEL (err 8)
    error: 3336 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: fetch -f --tags -- https://github.com/nrfconnect/sdk-zephyr v3.4.99-ncs1
    

  • Thanks, I will let you know if we find any problem. But from what you described, it's quite clear that the issue is related to your network. 

  • My internet is pretty stable I have cloned a good number of repositories and downloaded other stuff as well without any problems. So maybe there is something that can be improved from your side. Thank you Hung Bui for your assistance I will try to find some other network and install the SDK.

  • also if you can update the documentation on the choco list -lo because the -lo argument has been removed from chocolatey.

  • Thanks for the report Syed. I will forward it to the team. 

Reply Children
No Data
Related