In an effort to track down an unrelated problem, I switched back to using my H7 DISCO board and the HSEM_CoreSync sample application. If I debug only the CM7 code, or only the CM4 code, I can step through any/all lines. However, if I try to multi-core debug, single stepping on the CM7 says it is performing a step:
(before hitting F5)
(after hitting F5)
but it really doesn't. As you can see by the left red circle, it claims it is performing a step. In reality it did not step into MPU_Config, it actually performed a continue and is in the Error_Handler call shown in the right hand red circle.
Even if I set breakpoints in MPU_Config, hitting any step/continue button will cause it to skip the breakpoint(s) and end up in the Error_Handler. Pausing the CM7 shows the stack as calling that instance of the Error_Handler, and the Fault Analyzer always shows no faults.
The compiler options are all set to maximum (-g3), so this shouldn't be a problem of trying to debug optimized code.
Does anyone have a solution to this problem?
Thanks
C-Coder
