Custom error handler for cli

[pctj101]

In this file: components/libraries/cli/uart/nrf_cli_uart.c

The function as defined:

static void uart_error_handle(app_uart_evt_t * p_event)
{
    if (p_event->evt_type == APP_UART_COMMUNICATION_ERROR)
    {
        APP_ERROR_HANDLER(p_event->data.error_communication);
    }
    else if (p_event->evt_type == APP_UART_FIFO_ERROR)
    {
        APP_ERROR_HANDLER(p_event->data.error_code);
    }
}

Totally strips out the error type to the point that a custom error handler:

__WEAK void app_error_fault_handler(uint32_t id, uint32_t pc, uint32_t info)

Is unable to determine the original evt_type and thus unable to handle / ignore errors on an evt_type basis.

What's the normal way of overriding uart_error_handle()?

Or... is there a way to handle APP_UART_COMMUNICATION_ERROR and APP_UART_FIFO_ERROR differently in app_error_fault_handler()?

[Sigurd]

Hi,

See this answer.

If you want to handle the e.g. the event APP_UART_COMMUNICATION_ERROR in a different way, you need to do this yourself in the uart_error_handle() directly.

if (p_event->evt_type == APP_UART_COMMUNICATION_ERROR)
{
    //Your custom code on how to handle this error
}

[pctj101]

Hi Sigurd, thanks for your note. I was trying to avoid modifying the "base" components/libraries/* code.

Is it typical to dive into sdk/components/* and modify code there directly when trying to handle errors?

[Sigurd]

Yes, you should avoid modifying the "base" components/libraries/*. Usually the different libraries found in components/libraries does not use the APP_ERROR_HANDLER(), but will return the error_code to the higher level code, where the event_handler / error_handler is declared(e.g. in main.c).

Please note that the nrf_cli_uart.c is reworked in SDK 14, and no longer uses the APP_ERROR_HANDLER().