-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fresh CircuitPython install on Pico can't edit code #9935
Comments
I was finally able to get a writable CircuitPY drive by using the flash_nuke.uf2 and reinstalling circuitpython. |
Where did your RPi Pico come from, and it is the standard one? |
It's my usual test one, I think I originally got it at digikey? Some more details because I was very tired last night: I opened up the REPL, and eventually found this:
This was when I downgraded the first time, and loaded a new Circuitpython version. As that didn't fix the issue, eventually I found and executed:
This got back the drive name and default contents, but now I still couldn't transfer files. At some point I tried doing it via the terminal, which was when I realized it was read-only:
At the end, things didn't timeout, but fail immediatly |
CircuitPython version
Code/REPL
Behavior
Neither Mu nor the file manager can save this code to the pico.
I carefully followed https://learn.adafruit.com/getting-started-with-raspberry-pi-pico-circuitpython/circuitpython-programming-basics and I fail at the step
Save the file
. The drive is read-only!Googling around, it looks like boot.py is misconfigured, except that I don't have boot.py in the CIRCUITPY drive
Attempting to use the boot.py lines in the terminal, I get:
Googling this leads to results of "edit your boot.py file", which the documentation doesn't explain how to do when I can't save files!
This is an extremely terrible first-time user experience because following the documentation leads to a non-working pico.
Description
No response
Additional information
I've tried a few versions of circuitpython, and I've even reformatted the drive a few times with
Nothing has affected this issue
The text was updated successfully, but these errors were encountered: