micropython-builder icon indicating copy to clipboard operation
micropython-builder copied to clipboard

RP2350 build?

Open cuedcad opened this issue 1 year ago • 5 comments

Apologies if I have missed it, but will you be adding a RP2350/Pico 2 build that makes use of the fpu in the CortexM33?

Many Thanks to the other versions!

cuedcad avatar Aug 27 '24 09:08 cuedcad

You mean the new chip, right? micropython doesn't seem to have a build script for that chip, so it would be a bit hard for me to include it here. But I would be happy to add it.

v923z avatar Aug 27 '24 19:08 v923z

Yes the new mcu from RPi. As you have probably seen there is a 'preview' uf2 (https://micropython.org/download/RPI_PICO2/) but reading around there may be issues with the gpio pins and https://www.youtube.com/watch?v=_O3Aeyv2ILM seems to indicate that there may need to be some care taken when compiling to get the best performance, but hopefully on the near future. Thank you again for your builds

cuedcad avatar Aug 28 '24 09:08 cuedcad

OK, thanks for the clarification! I would suggest that we keep the issue open, and pick it up again, once micropython officially supports the chip. If I happen to forget, just ping me!

v923z avatar Aug 28 '24 17:08 v923z

@v923z I'm also very keen to make use of this.

Are these the scripts you're referring to? Looks like there was some activity last week:

https://github.com/micropython/micropython/tree/master/ports/rp2/boards/RPI_PICO2

Derfies avatar Oct 22 '24 03:10 Derfies

Thanks for the pointer, I'll try to find some time to fix this.

v923z avatar Oct 22 '24 06:10 v923z

Hey @v923z any luck getting ulab working on the pico 2?

Derfies avatar Apr 30 '25 06:04 Derfies

I haven't yet had time to deal with this.

v923z avatar May 18 '25 18:05 v923z

I've been trying to compile the micropython firmware for RP2350 for a few weeks now. After running all the commands listed in the main micropython-ulab github repo, no .uf2 files are being generated. Some attention to this issue would be appreciated. Here are the commands I am running. I've also tried several variants of this including calling git submodule update --init for just the modules listed in the tutorial on the main repo. I've also tried using cmake instead of make in the last step although cmake doesn't seem to recognize RPI_PICO2_W when passed in with the -DPICO_BOARD flag, which is weird.

git clone https://github.com/micropython/micropython.git cd micropython git submodule update --init --recursive cd .. git clone https://github.com/v923z/micropython-ulab ulab

cd micropython/mpy-cross make -j4 cd ../ports/rp2 make BOARD=RPI_PICO2_W submodules make BOARD=RPI_PICO2_W clean make BOARD=RPI_PICO2_W USER_C_MODULES=../../../ulab/code/micropython.cmake

These lines give me the following error upon entering the build folder created inside ../ports/rp2.

*** No targets specified and no makefile found. Stop. make[1]: Leaving directory 'PiPico/micropython/ports/rp2/build-RPI_PICO2_W' See https://github.com/micropython/micropython/wiki/Build-Troubleshooting make: *** [Makefile:65: all] Error 1

Jay-Damodaran avatar Aug 11 '25 18:08 Jay-Damodaran

Can you compile the firmware without ulab first?

v923z avatar Aug 11 '25 19:08 v923z

No, it gives the same error. I wonder if it has to do with the picotool that's being used. Make gives a warning about not finding a picotool and then downloads it automatically from somewhere, but it mentions rp2040 when it's being downloaded.

Jay-Damodaran avatar Aug 15 '25 20:08 Jay-Damodaran

OK, but then this is not a ulab issue. What you could do is look at the workflow file https://github.com/micropython/micropython/blob/master/.github/workflows/ports_rp2.yml.

v923z avatar Aug 15 '25 20:08 v923z

I think this issue can be closed now.

Jay-Damodaran avatar Sep 10 '25 16:09 Jay-Damodaran