This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

softdevice not working on custom board, err_code 0xC

I am trying to run the ble-characteristics tutorial code on a custom nRF52832 board (MetaMotionR). The blinky example worked just fine after creating a custom_board.h file with the correct pins, but the ble-characteristics code wont start advertising.

With Segger-RTT-print statements I found out that code execution gets stuck somewhere in ble_stack_init() in the SOFTDEVICE_HANDLER_INIT() macro.

I debugged the code by breaking into the loop statement in app_error.c. The errorcode is 0x0000000C and file and line point to a piece of code in the main.c file:

static void uart_events_handler(app_uart_evt_t * p_event)
{
    switch (p_event->evt_type)
    {
        case APP_UART_COMMUNICATION_ERROR:
            APP_ERROR_HANDLER(p_event->data.error_communication); // <-- this is where line_num points to
            break;

        case APP_UART_FIFO_ERROR:
            APP_ERROR_HANDLER(p_event->data.error_code);
            break;

        default:
            break;
    }
}

So what does this mean, from what I heard the memory settings (ram, rom) and some settings in custom_board.h could be an issue when using custom boards. I programmed S132 with nRFgo Studio.

€: I just found out that 0x0C is NRF_ERROR_DATA_SIZE. But im surprised, why should that error occur only on some devices?

Parents Reply Children
No Data
Related