@Peter, did you have any luck with getting MicroPython working? I meant to reply sooner but hadn’t joined the forum when I first saw this.
When you tried copying main.py over, was it to a drive named RPI-RP2? that is the label for the hdd that MrObvious suggested. I have the PicoSystem, I just confirmed. You hold the X button and power on to get that drive. If you have the Pimoroni MicroPython UF2 on the PicoSystem, holding the A button and powering on shows a PicoSystem logo, plays a sound then shows a few demos you can run, and it lists any other .py files you have uploaded to the filesystem on the PicoSystem.
MicroPython doesn’t share the filesystem like CircuitPython does with its CIRCUITPY drive. I’ve still only used Thonny to work with MicroPython on a RP2040 based device, I don’t know exactly how Thonny copies the files to the PicoSystem or how it reads what files are there already, I’ll get to learning that eventually.
I just tested three different UF2 files:
I had to use the first because the Thonny install based on the instructions MrObvious linked to didn’t work, it had some error about an expired certificate.
The rp2-pico-20220117-v1.18.uf2 file worked and I could create a main.py file in Thonny and use the code print("Hello World")
to see output on the console but likely not the screen without a lot of code if it’s even possible.
pimoroni-pico-v1.18.1-micropython-v1.18.uf2 is a file I had downloaded recently while testing for a different post (Need some RV3028, Pico, Micro Python, Date Time, help). That was using a Raspberry Pi Pico but that does work on the PicoSystem and seems to have a picosystem frozen module but looking on GitHub (pimoroni-pico/picosystem.py at main · pimoroni/pimoroni-pico · GitHub) it seems to be a minimal example not the PicoSystem API from Pimoroni.
picosystem-v0.1.2-micropython-v1.17.uf2 is the file for the PicoSystem API from Pimoroni.
And something interesting about those testes:
- The rp2 and pimoroni-pico versions seem to share the same MicroPython area in flash memory used for the filesystem on the Pico / PicoSystem
- Flashing with the picosystem file shows different files
- They don’t overlap because swapping back and forth between those .UF2 files does not delete the main.py files
- changes to the main.py while on the rp2 UF2 are shown when running the pimoroni-pico UF2 and vice versa
- While I was testing C++ on the Pico, I found the nuke example on the page: GitHub - raspberrypi/pico-examples
- That nuke example erases everything on the flash memory, maybe only possible in a C++ UF2 file, it states: “An example of a NO_FLASH binary (UF2 loaded directly into SRAM and runs in-place there).”
Basically, there are all sorts of interesting things to learn about the RP2040, Raspberry Pi Pico and PicoSystem then the growing selection of other boards and devices created using the RP2040. Which is partly why I got carried away and this ended up a long post :).