Okay, but then which is / where is the micropython.cmake file you were referencing?
Yeah, I tried to make heads or tails out of the Pimoroni process and it gave me a splitting headache so I had to stop. Just cloning wonât work, but honestly, Iâm not sure there IS an easy/direct way to reconcile all the Pimoroni release changes versus the PicoCalc-micropython-driver changes. Not giving up, but just added a bunch more complexity to the setup and/or build process, I suspect.
Okay, so I tried using the latest Pimoroni Pico Plus 2W uf2 image from the PicoCalc_micropython_driver repo, but am still having issues. The image is booting fine, but appears to be booting off its internal fs, rather than SDCard. I get the micropython prompt across the USB serial port, but the fs doesnât automount, so not sure what to do there.
I suspect the problem is I simply need Laikaâs boot.py by itself on the internal fs, Iâm just not entirely sure how to get it there when all I have is the mpy console on the device. Suggestions?
Yes, micropython utilizes the internal 16MB flash (On the Plus models) for system files.
Do you have a computer available?
Thonny can automatically interact with the Internal FS and allows uploading/downloading files, or you can use mpremote: MicroPython remote control: mpremote â MicroPython latest documentation, which would offer a command line environment that allows mounting the internal FS or copying and whatnot.
As a side note, it would not really help for no boot.py, however once I finally receive my Plus 2W I will work on porting wget, which would help with pulling non-system critical scripts.
For GGâs repository it would follow the same path as the updated instructions, which is already updated for the correct main repository name.
It is worth noting that due to Pimoroniâs library being a pain to use, and introducing mysterious errors to my console specifically, I have begun using a hacky workaround to compile instead, modifying the stock Pico 2 definitions with the correct flash size and PSRAM support.
I may just end up exporting my own board definition to compile with to simplify this process greatly, let me know if you are interested.
It would not require any of the added Pimoroni libs, just the stock micropython repository.
MPY: soft reboot
Traceback (most recent call last):
File "boot.py", line 11, in <module>
ImportError: can't import name checksd
MicroPython v1.25.0-preview.389.gf187c77da on 2025-04-17; Raspberry Pi Pico2 with RP2350
Type "help()" for more information.
Thatâs in picocalc_system.py, and itâs supposedly built into the firmware. You can try copying that file directly into the root or /lib of the micropython filesystem via thonny to debug.
for which model? we support both normal pico with and without wifi, as well as the pimoroni plus models. The libraries differ due to micropython being built for each platform, itâs mostly up to the official maintainers what is supported by default.
Its definetly not, I donât know why gg wrote the instructions like that. At the very least, I wrote picocalc_system myself, and made no attempt to embed it like that.
I personally copy over all of the picocalc_files folder as well.
This is where Iâm getting confused. I can load the micropython firmware and get the serial prompt for it. Nothing comes up on the screen, but reading this thread its pretty obvious that more files are needed by micropython to activate the screen. Do I just copy all of the files in âpico_filesâ (there is not âpicocalc_filesâ) into the root directory or do I preserve the âmodulesâ directory when I copy those over?
Not sure how correct it is, but I got things to work if I copied all the files under âpico_filesâ into the root directory. For anyone trying, here are the steps I used.
Hold down the bootselect button and insert the cable between my computer and the micro USB (Not USB-C)
Copy the âpicocalc_micropython_pico.uf2â from the git checkout to the directory to the mount point for the Pico.
Once itâs done copying the pico will reboot and present a micropython prompt to the serial console on the micro USB port.
I used ampy to copy all the files under pico_files in the git checkout to the root directory. No directories on the pico. This includes everything under root and modules.
Unplug the micro USB cable and turn on the picocalc.
Now I have the micropython prompt on the picocalc screen.
After abandoning the Lyra/Linux thing today and installing Pico 2W/MicroPython, I found putting all the files from the modules folder into a /lib folder on the Pico works perfectly fine. I hate having a cluttered root directory. For whatever reason the boot.py from the primary github repo does not work for me. So I ended up using the main.py from the PicoCalc github and then writing my own boot.py to mount the SD card and connect to my Wifi network.
The âpicocalc_systemâ module included in the Pico2 image in the github repo does not seem to have the âchecksdâ module.
So I copied all the .py files in the pico_files/modules/ to the root folder of Pico2 and it worked.
(It did not work under /lib in Pico2 either.)
>>> help(picocalc_system)
object <module 'picocalc_system' from 'picocalc_system.py'> is of type module
disk -- <function disk at 0x2000ced0>
os -- <module 'os'>
__file__ -- picocalc_system.py
initsd -- <function initsd at 0x2000cf70>
prepare_for_launch -- <function prepare_for_launch at 0x2000ccc0>
run -- <function run at 0x2000cc80>
human_readable_size -- <function human_readable_size at 0x2000cc60>
__name__ -- picocalc_system
killsd -- <function killsd at 0x2000cf90>
machine -- <module 'machine'>
gc -- <module 'gc'>
memory -- <function memory at 0x2000ce50>
sdcard -- <module 'sdcard' from 'sdcard.py'>
uos -- <module 'os'>
files -- <function files at 0x2000ceb0>