app: ERROR 4 [NRF_ERROR_NO_MEM] on connection

[jbmillard]

I am working on an application using the Rigado BMD-350 development board.  It uses the nRF52832.  Development is being done in Segger Embedded Studio with nRF_SDK_17.1.0.

I started the project using the ble_app_template example.  Quite a bit has changed.

I have one VS UUID with one characteristic (for testing, I'll add more later).

I had problems advertising and increased the NRF_SDH_BLE_VS_UUID_COUNT to 16 and adjusted RAM start and size per the debug messages.

Now I can advertise but when I try to connect (using BlueSee on the desktop), I get a NRF_ERROR_NO_MEM error.  The error position is in the following error handler function:

/**@brief Function for handling errors from the Connection Parameters module.
 *
 * @param[in] nrf_error  Error code containing information about what went wrong.
 */
static void app_conn_params_error_handler(uint32_t nrf_error)
{
	APP_ERROR_HANDLER(nrf_error);
}

This error handler is passed to ble_conn_params_init() in the error_handler member of the ble_conn_params_init_t structure.

I have a function that wraps APP_ERROR_CHECK to print any non-zero error codes and all returns of library code are checked.  I'm not seeing any error from a function return.

Is there something in sdk_config.h that I need to adjust? 

Thanks!

[Sigurd]

Hi,

There are several places in ble_conn_params.c that are calling send_error_evt()

Are you able to debug, look at the call-stack, and see where in ble_conn_params.c the error is coming from ? 

[jbmillard]

Yes, I've found the following calls:

conn_params_negotiation()
app_timer_start()
timer_req_schedule()
nrf_atfifo_item_alloc()
nrf_atfifo_wspace_req()

The last call nrf_atfifo_wspace_req() returns NULL.  

I had stupidly removed the call to app_timer_init() when I removed the timer creation from my code (I don't need them).  Now I'm connecting.

Thanks.