Debugging Preparation

[thestumbler]

A couple of weeks back, I attempted to run some non-trivial code on two cores. Despite my best efforts, it would not work, with the second core crashing / freezing. Reading the issues here and elsewhere, it looked like I wasn't the only one, and that I was going to need to debug the problem. I ordered a Pi Debug probe for this future debugging effort, and in the meantime I refactored by code to work on one core. I knew it was possible to run on one core, but the timing was quite tricky.

The debugger should arrive soon, and I'll have time for this in a week or so. What are some good references to review in the meantime? I'm generally comfortable debugging STM32F4 families with either STLink-based or BMP/OpenOCD tools.

-Chris

[earlephilhower]

The method here is plain GDB. If you've used it for the STM32, it's the same. You have some number of HW breakpoints, can single step, etc. for multicore there is also the thread command to swap between the cores. Things like USB and I/O will probably fail in the stoped state, but that's not unique to this chip.