The Pimoroni MicroPython build seems to be expecting the file system to be exactly as it would be for any other MicroPython so shouldn't need to be nuked when moving between MicroPython installs.īut it is possible there could be something in the file system, or something different with the filesystem, which could be causing Pimoroni MicroPython to be doing something which is stopping things working so, yes, it may be appropriate, even necessary in some cases, to nuke the Flash first. That should cause such programs to realise those areas have not been initialised and cause them to be initialised.īut doing that would only be a solution if not doing that were the cause of a problem, and I can't immediately see that it is the case here. What nuking is good for is resetting Flash beyond what the UF2 itself overwrites, for example the file system areas used by MicroPython and CircuitPython, non-volatile storage areas which may be used by other programs. Most times it doesn't make any difference whether Flash is nuked first or not. Nuking the Flash is in most cases pointless, it is simply replacing what was there with something different, either of which will then be overwritten by whatever UF2 is to be flashed. It places an "eyecatcher" pattern into the first page of Flash which I don't believe would be there if genuinely factory fresh, but would accept it is pretty much an irrelevancy in practice. There is a flash nuke file here that will reset it back to the factory default state.Īlmost. Is there a way I can reformat the Pico and start again?
Sadly, After doing what you said I still got this error message: Thonny didn't immediately recognise it, so I unplugged and plugged it back in - without holding BOOTSEL - and clicking the Stop/Restart icon in Thonny again got it recognised. I held BOOTSEL then plugged it in, downloaded the UF2. _uasyncio breakout_rgbmatrix5x5 picosystem uioīreakout_as7262 breakout_roundlcd picounicorn ujsonīreakout_bh1745 breakout_rtc picowireless ulabīreakout_bme280 breakout_sgp30 pimoroni uosīreakout_bme68x breakout_trackball pimoroni_i2c urandomīreakout_colourlcd160x80 cmath rp2 uselectīreakout_colourlcd240x240 ds18x20 uarray ustructīreakout_dotmatrix framebuf uasyncio/_init_ usysīreakout_icp10125 machine uasyncio/event uzlibīreakout_ltr559 micropython uasyncio/lockīreakout_matrix11x7 onewire uasyncio/stream _thread breakout_potentiometer picoscroll uhashlib _onewire breakout_paa5100 picoexplorer uctypes
_boot breakout_msa301 picodisplay2 ucollections _main_ breakout_mics6814 picodisplay ubinascii
Have I messed up my Pico altogether or is it recoverable?Ĭode: Select all MicroPython v1.17 on Raspberry Pi Pico with RP2040 MicroPython v1.17 on Raspberry Pi Pico with RP2040ĮRROR : Crash in backendįile "/usr/local/lib/python3.7/dist-packages/thonny/plugins/micropython/backend.py", line 142, in _init_įile "/usr/local/lib/python3.7/dist-packages/thonny/plugins/micropython/backend.py", line 181, in _prepare_rtcįile "/usr/local/lib/python3.7/dist-packages/thonny/plugins/micropython/backend.py", line 276, in _validate_timeįile "/usr/local/lib/python3.7/dist-packages/thonny/plugins/micropython/backend.py", line 270, in _get_time_for_rtcīackend terminated or disconnected. I also tried to use bootsel to load rp2-pico-20210902-v1.17.uf2 as well and had no success. It just goes to files on the computer as if the Pico wasn't there. uf2 file to this one: pimoroni-pico-v0.3.1-micropython-v1.17.uf2 (so that I could use the Omnibus and Pico Breakout Garden with my Pico) but once I'd done it I couldn't get Thonny to displaythe message which gives you a choice between opening files from This Computer or Raspberry Pi Pico.
0 kommentar(er)
