DFU serial failed

[schef]

Hi guys,

i'm using DFU over serial and i get the error 4 in NRF_DRV_UART_EVT_ERROR.

This was not happening before and suddenly started.

<debug> nrf_dfu_flash: nrf_fstorage_write(addr=0x00040300, len=0x100 bytes), queue usage: 1
<info> dfu_req_handling: Storing 256 bytes at: 0x00040300
<debug> nrf_dfu_flash: Flash write success: addr=0x00040300, pending 0
<debug> nrf_dfu_flash: nrf_fstorage_write(addr=0x00040400, len=0x100 bytes), queue usage: 1
<info> dfu_req_handling: Storing 256 bytes at: 0x00040400
<debug> nrf_dfu_flash: Flash write success: addr=0x00040400, pending 0
<debug> nrf_dfu_flash: nrf_fstorage_write(addr=0x00040500, len=0x100 bytes), queue usage: 1
<info> dfu_req_handling: Storing 256 bytes at: 0x00040500
<debug> nrf_dfu_flash: Flash write success: addr=0x00040500, pending 0
<error> app: Received an error: 0x00000004
<info> app: Inside main

What could be the issue?

SDK: 14.1

board: nrf52832

[schef]

Here is more information from gdb:

#0 app_error_handler_bare (error_code=4) at ../../main.c:73
#1 0x000775a0 in uart_event_handler (p_event=<optimized out>, p_context=<optimized out>, p_event=<optimized out>) at ../../sdk_edited/components/libraries/bootloader/serial_dfu/nrf_serial_dfu.c:403
#2 0x00076534 in uarte_irq_handler (p_uarte=0x40002000, p_cb=<optimized out>) at ../../../../sdk/nRF5_SDK_14.2.0_17b948a/components/drivers_nrf/uart/nrf_drv_uart.c:912
#3 UARTE0_UART0_IRQHandler () at ../../../../sdk/nRF5_SDK_14.2.0_17b948a/components/drivers_nrf/uart/nrf_drv_uart.c:963
#4 <signal handler called>
#5 0x00013d6e in ?? ()
#6 0x00013d6c in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb)

[Hung Bui]

Hi Schef, 

Do you have HWFC on UART ? At which baudrate you were running   ? 

Error 4 is NRF_ERROR_NO_MEM. We need to track down which function throwing that error. Could you test using the bootloader debug version and turn optimization off to see more debug information ? 

[schef]

Are you sure that Error 0x04 in:

static void uart_event_handler(nrf_drv_uart_event_t * p_event, void * p_context)
{
    switch (p_event->type)
    {
        case NRF_DRV_UART_EVT_TX_DONE:
            nrf_dfu_req_handler_reset_if_dfu_complete();
            break;

        case NRF_DRV_UART_EVT_RX_DONE:
            ...
            break;

        case NRF_DRV_UART_EVT_ERROR: {
	        APP_ERROR_HANDLER(p_event->data.error.error_mask);
            break;
            }
    }
}

is not based on enum nrf_uart_error_mask_t which would be NRF_UART_ERROR_FRAMING_MASK?

infocenter.nordicsemi.com/index.jsp

[schef]

Framing error as described here http://ltxfaq.custhelp.com/app/answers/detail/a_id/85/~/serial-port-framing-errors is some HW staff which has sense because on one board i don't have this errors and on another i have (i found that out yesterday).

I have no flow control, and baud-rate used is 9600.

[Hung Bui]

You are right. It's the UART ERROR and bit 3 is Framing error. You can to monitor the UART communication with a logic analyzer to look for the error. Do you have a long UART cable/track ? any parasitic capacitance ? 

[schef]

Is it possible to recover from this issue using software only? Reinit uart and repeat the packet. CRC will fail and then i can try to send it again.

I tried to enable nrf_drv_uart_rx but after that i got <error> app: Received a fault! id: 0x00004002, pc: 0x00000000, info: 0x2003FEF8

do you have any suggestions?