How to determine the fault when you arrive at NRF_BREAKPOINT_COND?

[BenBurch]

OK, I have an app that succeeds in starting advertising and then arrives in the main event loop, following which I go to the NRF_BREAKPOINT_COND trap.

Since I do not have a call stack at this point, how can I determine what happened here?  Is there any status saved that I can examine?

I know this is likely coming out of the softdevice, correct?

Thanks!

-Ben Burch

BTR Controls, Inc.

[BenBurch]

OK, I have figured this one out;  Place a breakpoint at app_error_handler, and the information is in the call parameters.