Damien George

> It might be possible to provide our own `pico_util` with a more MicroPython-friendly alternative for that function, or just to shim `localtime_r`, eg: Good idea.... but I tried your...

> Here's an extended version of @Gadgetoid's patch that gets the code size all the way down (PICO_W binary size is actually slightly smaller than the current master). Thanks for...

> decide on board name: `RPI_PICO2` vs `RPI_PICO_2` (latter matches `RPI_PICO_W`, and officially it's `Pico 2`) The decision is to stick with `RPI_PICO2`, and then also `RPI_PICO2_W` (eventually), because that...

> I know you’re probably still working your way down here, but don’t miss the PWM patch above! Thanks for that, I checked your patch and cherry-picked it to this...

> You might want to add PICO_EMBED_XIP_SETUP=1 to the compile definitions Good idea, thanks! > though I must admit I have no idea why some tests get slower! On an...

I verified that enabling `PICO_EMBED_XIP_SETUP=1` also improves performance of the RP2350 in RISCV mode, and it improves more than the ARM case. Also, enabling this option on ARM doesn't increase...

I've now made the rp2350 builds default to 150MHz, using the new `SYS_CLK_KHZ` macro provided by the pico-sdk. I also updated TinyUSB to the latest release 0.17.0. > I'm happy...

Thanks, this change looks OK. The CI passes and that uses `make submodules` a lot, so that's a good check.

It looks like you have a custom board definition, and you have not configured it correctly. Please share your board configuration files to make progress here with debugging.

> #define MICROPY_OBJ_REPR (MICROPY_OBJ_REPR_C) You can't use this object representation with double precision float (which the H750 has). I suggest just removing this line and using the default object representation...