You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TLDR Breakpoints, in code run on core 1, are ignored after resetting via multicore_reset_core1()
Hi, I'm trying to debug some function on core1.
But when I set a breakpoint and start debugging, nothing happens. Only when I pause the execution and then resume it, the breakpoint gets hit.
Details
I have notices this only occurs when I call the multicore_reset_core1().
When I leave this multicore_reset_core1() out and just run multicore_launch_core1(core1_entry); everything works just fine.
Also, when this issue occurs, gdb throws this error:
Error: Failed to select multidrop rp2040.dap1
Polling target rp2040.core1 failed, trying to reexamine
This happens when starting to flashing or debugging.
This Error goes away when I leave out the multicore_reset_core1()-call.
Thank you in advance. This issue is plaguing me for a good month.
I first stubbled on this while using FreeRTOS, but it turned out this is a native sdk/debugger -issue and NOT a problem of FreeRTOS.
I'm using the VSCode-Plugin to set up the Project.
To reproduce, set a breakpoint at printf("Core 1\n"); and hit F5 to Debug and hit continue. Nothing will happen.
Open up a serial-monitor: Both Cores are printing something to serial monitor.
Then comment out multicore_reset_core1();, recompile, Reflash.
Debug again and now the breakpoint gets hit.
TLDR Breakpoints, in code run on core 1, are ignored after resetting via
multicore_reset_core1()
Hi, I'm trying to debug some function on core1.
But when I set a breakpoint and start debugging, nothing happens. Only when I pause the execution and then resume it, the breakpoint gets hit.
Details
I have notices this only occurs when I call the
multicore_reset_core1()
.When I leave this
multicore_reset_core1()
out and just runmulticore_launch_core1(core1_entry);
everything works just fine.Also, when this issue occurs, gdb throws this error:
This happens when starting to flashing or debugging.
This Error goes away when I leave out the
multicore_reset_core1()
-call.Thank you in advance. This issue is plaguing me for a good month.
I first stubbled on this while using FreeRTOS, but it turned out this is a native sdk/debugger -issue and NOT a problem of FreeRTOS.
Minimal working Example
My setup/Versions:
I'm using the VSCode-Plugin to set up the Project.
To reproduce, set a breakpoint at
printf("Core 1\n");
and hit F5 to Debug and hit continue. Nothing will happen.Open up a serial-monitor: Both Cores are printing something to serial monitor.
Then comment out
multicore_reset_core1();
, recompile, Reflash.Debug again and now the breakpoint gets hit.
issue-multicore-debug.cpp:
Here is the entire Project Directory for reproduction:
issue-multicore-debug.zip
Thank you in advance for helping!
The text was updated successfully, but these errors were encountered: