You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See issue #1845
The problem should have been fixed but I'm still experiencing the same issue.
Describe the bug
when clicking the "run on device button" nothing happens but it stays in the "loading state". On the Sprig hardware, the screen stays the same (the "please upload a game" text)
To Reproduce
[I'm using the included usb-micro cable and google chrome]
-Go to a Sprig game
-click the "run on device" button
-select the serial port of the rpi pico
Expected behavior
The game gets uploaded to the sprig and I can play it
Actual behavior
The button never stops loading and nothing gets uploaded to the Sprig
Screenshots
the "run on device" button never stops loading
See issue #1845
The problem should have been fixed but I'm still experiencing the same issue.
Describe the bug
when clicking the "run on device button" nothing happens but it stays in the "loading state". On the Sprig hardware, the screen stays the same (the "please upload a game" text)
To Reproduce
[I'm using the included usb-micro cable and google chrome]
-Go to a Sprig game
-click the "run on device" button
-select the serial port of the rpi pico
Expected behavior
The game gets uploaded to the sprig and I can play it
Actual behavior
The button never stops loading and nothing gets uploaded to the Sprig
Screenshots
the "run on device" button never stops loading
What I've tried:
-redowloading and reuploading the pico-os.uf2 file
-resetting the flash memory and reuploading the pico-os.uf2 file (https://www.raspberrypi.com/documentation/microcontrollers/raspberry-pi-pico.html#resetting-flash-memory)
-tried the same using microsoft edge
-tried a different game
-tried a different cable
-tried a different usb port
-The pico seems to be fine, the arduino IDE has recognized it and I've managed to run the "blink" program on it.
The text was updated successfully, but these errors were encountered: