I am running a Raspberry Pi 400, and have been using pico-setup to reinstall the pico repositories on each release, but I have had multiple issues with the 2.0.0 release.
The first issue during install is "error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: CANCEL (err 8)". This issue APPEARS to be recoverable, in that re-running the ./pico-setup.sh script will get past this point (until it hits a later issue which does not appear to be related).
This error has never happened with past versions.
For context, I am running a Raspberry Pi 400, and "uname -a" provides the following output:
Linux raspberrypi 5.10.103-v7l+ #1529 SMP Tue Mar 8 12:24:00 GMT 2022 armv7l GNU/Linux
(I will file a separate issue for the subsequent error, as it does not appear to be related.)
I don't see anything obvious indicating that my system is missing any new pre-requisites.
Here is more context for the RPC failed error output:
Resolving deltas: 100% (5078/5078), done.
Submodule 'lib/btstack' (https://github.com/bluekitchen/btstack.git) registered for path 'lib/btstack'
Submodule 'lib/cyw43-driver' (https://github.com/georgerobotics/cyw43-driver.git) registered for path 'lib/cyw43-driver'
Submodule 'lib/lwip' (https://github.com/lwip-tcpip/lwip.git) registered for path 'lib/lwip'
Submodule 'lib/mbedtls' (https://github.com/Mbed-TLS/mbedtls.git) registered for path 'lib/mbedtls'
Submodule 'tinyusb' (https://github.com/hathach/tinyusb.git) registered for path 'lib/tinyusb'
Cloning into '/home/pi/devel/pico/pico-setup/pico/pico-sdk/lib/btstack'...
Cloning into '/home/pi/devel/pico/pico-setup/pico/pico-sdk/lib/cyw43-driver'...
Cloning into '/home/pi/devel/pico/pico-setup/pico/pico-sdk/lib/lwip'...
Cloning into '/home/pi/devel/pico/pico-setup/pico/pico-sdk/lib/mbedtls'...
error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: CANCEL (err 8)
fatal: the remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
fatal: clone of 'https://github.com/Mbed-TLS/mbedtls.git' into submodule path '/home/pi/devel/pico/pico-setup/pico/pico-sdk/lib/mbedtls' failed
Failed to clone 'lib/mbedtls'. Retry scheduled
Cloning into '/home/pi/devel/pico/pico-setup/pico/pico-sdk/lib/tinyusb'...
error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: CANCEL (err 8)
fatal: the remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
fatal: clone of 'https://github.com/hathach/tinyusb.git' into submodule path '/home/pi/devel/pico/pico-setup/pico/pico-sdk/lib/tinyusb' failed
Failed to clone 'lib/tinyusb'. Retry scheduled
Cloning into '/home/pi/devel/pico/pico-setup/pico/pico-sdk/lib/mbedtls'...
fatal: unable to access 'https://github.com/Mbed-TLS/mbedtls.git/': GnuTLS recv error (-9): Error decoding the received TLS packet.
fatal: clone of 'https://github.com/Mbed-TLS/mbedtls.git' into submodule path '/home/pi/devel/pico/pico-setup/pico/pico-sdk/lib/mbedtls' failed
Failed to clone 'lib/mbedtls' a second time, aborting
Cloning into '/home/pi/devel/pico/pico-setup/pico/pico-sdk/lib/tinyusb'...
I am running a Raspberry Pi 400, and have been using pico-setup to reinstall the pico repositories on each release, but I have had multiple issues with the 2.0.0 release.
The first issue during install is "error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: CANCEL (err 8)". This issue APPEARS to be recoverable, in that re-running the ./pico-setup.sh script will get past this point (until it hits a later issue which does not appear to be related). This error has never happened with past versions.
For context, I am running a Raspberry Pi 400, and "uname -a" provides the following output:
(I will file a separate issue for the subsequent error, as it does not appear to be related.)
I don't see anything obvious indicating that my system is missing any new pre-requisites.
Here is more context for the RPC failed error output: