I think it would help and say why you want to disable core 1.I have this project I want to explicitly disable core1 by calling multicore_reset_core1() at program start
However, when this function call is in there, OpenOCD will not attach. Using a PicoProbe.
I suppose it's because core1 gets reset unexpectedly from OpenOCD's point of view.
I have not played around accessing core 2 and assume it is dormant until used programmatically. Core 1 will be where the Pico firmware is running. Remember, you are not dealing with an OS here. Disabling Core 1 effectively would cause the Pico to stop working IMHO.
Statistics: Posted by DS256 — Wed Apr 09, 2025 1:23 pm