How to find what is causing APP_ERROR:ERROR:FATAL

RE: How to find what is causing APP_ERROR:ERROR:FATAL

brianreinhold — Tue, 26 Jan 2021 15:12:53 GMT

I just added the preprocessor in that ugly line. What I found was that the method sd_app_evt_wait() returns error code 2 which is NRF_ERROR_SVC_HANDLER_MISSING. I did not check for any error codes on this method because the documentation states it only returns NRF_SUCCESS.

Opps, error 2 is NRF_ERROR_SOFTDEVICE_NOT_ENABLED. Of course it is disabled. I disabled it. So how do I handle that final for(;;) loop? Should I just return and exit main?

RE: How to find what is causing APP_ERROR:ERROR:FATAL

brianreinhold — Tue, 26 Jan 2021 14:14:05 GMT

My file does not have that. s130 for soft device and SDK 12.3.0.

My file looks like this:

#include "app_error.h"

#define NRF_LOG_MODULE_NAME "APP_ERROR"
#include "nrf_log.h"
#include "nrf_log_ctrl.h"
/*lint -save -e14 */

/**
 * Function is implemented as weak so that it can be overwritten by custom application error handler
 * when needed.
 */
__WEAK void app_error_fault_handler(uint32_t id, uint32_t pc, uint32_t info)
{
    NRF_LOG_ERROR("Fatal\r\n");
    NRF_LOG_FINAL_FLUSH();
    // On assert, the system can only recover with a reset.
#ifndef DEBUG
    NVIC_SystemReset();
#else
    app_error_save_and_stop(id, pc, info);
#endif // DEBUG
}

It looks like I have to set a DEBUG preprocessor somewhere. The preprocessor list in Keil is one of the most user-unfriendly interfaces I have seen. One line of limited size where one has to enter one after the other. Horrible. Perhaps there is another way?

RE: How to find what is causing APP_ERROR:ERROR:FATAL

Susheel Nuguru — Tue, 26 Jan 2021 13:59:21 GMT

Enable the DEBUG preprecessor flagIf you can start your program in debugger, you should be able to see the call trace when the hit the breakpoint of the error like this