Put a breakpoint on up_assert.
You can also then set the PC and SP to the saved value to see the
context of the assertion.
On 3/6/2023 1:01 PM, Tim Hardisty wrote:
Am I being dumb again? With CONFIG_DEBUG_ASSERTIONS set, the system doesn't
halt with a DEBUGASSERT (in a driver), and ends up i
Am I being dumb again? With CONFIG_DEBUG_ASSERTIONS set, the system doesn't
halt with a DEBUGASSERT (in a driver), and ends up in a while(true) type loop
and I have to pause the debug session and hope that the call stack helps (a
50:50 chance for reasons I am yet to understand).
The assert is i
