Closed mattcaves closed 1 year ago
This isn't a picoprobe bug. As you can see from the openocd trace, you have a debug session. If you still have the issue on v1.5.0 of the SDK, open an issue there.
@mattcaves I'm not sure if this is still a problem for you but I've found that adding multicore_reset_core1();
before the multicore_launch_core1(...);
call solves the issue. I had similar issues with even v.1.5.0. I'm new to openOCD as well. There might be a better way...
@igalex Thank you!
I've just revisited using the latest picoprobe-cmsis-v1.0.2, it was still a problem, hanging at multicore_launch_core1(...);
Adding multicore_reset_core1();
fixes it!
Thanks for the solution, much appreciated!
Hi there, I also ran into this issue, and adding multicore_reset_core1() also worked for me. I suspect it's some difference between openocd as packaged on the RPI repositories and OpenOCD mainline. Thanks for helping me find the problem!
Rebuilding and reinstalling openocd from master did resolve this issue. I think the version I had a problem with was v0.12.0. Possibly because SMP mode landed slightly later?
I'm not sure if this is related to https://github.com/raspberrypi/picoprobe/issues/45
I've just changed over from the custom Picoprobe implementation to the latest CMSIS-DAP implementation. The dev environment has been working fine for the last couple of months with the custom implementation. This is my first time using openOCD, so I don't have a lot of knowledge about it!
The issue is when I run
multicore_launch_core1(_second_core_code);
it hangs the pico, it seems to get stuck in the function below in multicore.cmy launch.json
and terminal output