MicroPython • Re: Running SDK-C Code on Core in MicroPython

So something to do with stacks I would presume. Perhaps launching Core 1 without a specified stack is smashing Core 0's stack ?

Serendipitously, a change to MicroPython which broke the build of my fork of MicroPython, produced this linker report for vanilla MicroPython for the RP2040 -It seems to me the linker script MicroPython uses treats Scratch X and Y as a single 8KB area and not as the two 4KB areas they normally are for Pico SDK builds, as I think MicroPython also did some time ago.

I don't know what affect calling 'multicore_launch_core1' with a default stack now has. Smashing Core 0's stack may be the result, or it may be triggering the stack guard for that.

Statistics: Posted by hippy — Thu May 28, 2026 7:19 pm

---