|
|
|
@ -17,3 +17,33 @@ draft: true
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
## Raspberry Pi 4
|
|
|
|
|
|
|
|
|
|
4GB version, if that information is of any use.
|
|
|
|
|
|
|
|
|
|
## Raspberry Pi 3
|
|
|
|
|
|
|
|
|
|
## Raspberry Pi 2
|
|
|
|
|
|
|
|
|
|
## Raspberry Pi Pico W
|
|
|
|
|
|
|
|
|
|
### Using MicroPython
|
|
|
|
|
|
|
|
|
|
<https://micropython.org/download/RPI_PICO_W/>
|
|
|
|
|
|
|
|
|
|
I did the dumb thing and made the `boot.py` file break which led to an endless
|
|
|
|
|
loop showing me only the Error code and restarting...
|
|
|
|
|
|
|
|
|
|
I was able to stop the script by quickly pressing <kbd>CTRL+D</kbd>,
|
|
|
|
|
<kbd>CTRL+C</kbd> on the serial console but never was able to update the broken
|
|
|
|
|
file without it doing a soft-reboot which loads `boot.py` again instantly...
|
|
|
|
|
|
|
|
|
|
After some research I was glad I found [pico-nuke](https://github.com/polhenarejos/pico-nuke/releases).
|
|
|
|
|
|
|
|
|
|
Boot into uf2 loading (pressing BOOTSEL while power on) and place the correct .uf
|
|
|
|
|
file (`pico_nuke_pico_w-1.1.uf2`) on the mounted device.
|
|
|
|
|
|
|
|
|
|
On OpenBSD there is no response but you can see the filesystem unmounted/removed.
|
|
|
|
|
Unplug the USB and plug it in again booting into uf2 loading, copying over the
|
|
|
|
|
MicroPython uf2 file again.
|
|
|
|
|
|
|
|
|
|