Check the err_code variable in the debugger. You will only hit NRF_BREAKPOINT_COND if err_code was non-zero.
A non-zero err_code means there was an error in the previous function or SD call.
Identifying and fixing the bug will be OPs task - we don't see any source code.
Check the err_code variable in the debugger. You will only hit NRF_BREAKPOINT_COND if err_code was non-zero.
A non-zero err_code means there was an error in the previous function or SD call.
Identifying and fixing the bug will be OPs task - we don't see any source code.
Thanks for the reply.
Yeah, I did that first thing. Surprisingly, value of err_code is zero and I still get NRF_BREAKPOINT_COND. That's why, for now, I commented out the APP_ERROR_CHECK(err_code) call which is not a great solution.
How did you test the value of err_code? In some cases the debugger might lie to you.
APP_ERROR_CHECK( 0 ) should not execute anything besides the zero value test.
Commenting out the APP_ERROR_CHECK just ignores the error, which usually also means some function won't work properly.