Yes, exactly that. And that sounds like a good way to add hardware which would be missing from a PT52 system built using a Waveshare PiZero.Is it that the RM2 only needs SPI connection to work? Since the waveshare board is Pi Zero form factor making a hat with the module and maybe an option it could be I make a PT52 hat with the serial port and the audio output is also missing.
In fact, with some judicious selection of which pins are used on the 40-way header you might be able to create an "RM2 HAT" / "PT52 HAT" which would work with Pi Zero, A, B, A+, B+ and 2B as well.
I don't see it as being problematic. As a Pi Zero 3W (2W+ or 2W-) it will be just like every other Pi Zero and SBC, everything hidden behind abstraction layers, with only the bare metal fans having to deal with the really low-level stuff.I think the biggest issue with the idea is that once released then users would want to integrate it into there own designs and designing for the RP3A0 wouldn't be as easy as it is the RP235x and RP2040, But maybe I'm wrong about that.An enhanced Pi Zero 2W as a Pico
For Pico users getting a Pico 3W, just adding "-DPICO_BOARD=pico3_w" should be enough. Coding shouldn't be any worse than having differences between Pico, W, 2, 2W and third-party boards. I would expect MicroPython and CircuitPython to be compilable and runnable with just that.
I see it as similar to compiling with "-DPICO_PLATFORM=host" except it will generate a bare metal binary which boots and runs on a Pico 3W and will support everything a Pico W has.
HAL libraries will need to be written but that's no different to how it is already for Pico or any bare-metal coding.
I think I am going to have a play at adding support for "-DPICO_BOARD=pi_4b" and seeing if I can get an executable which runs on that rather than a UF2. Next step would be to add Zero 2W.
Statistics: Posted by hippy — Sun Sep 07, 2025 6:42 pm