• State Verified Answer
  • Replies 1 reply
  • Subscribers 88 subscribers
  • Views 1084 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 268161
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

BLE can advertise but when user tries to connect, NRF_ERROR_NO_MEM occurs at conn_params_error_handler

MarvinNeil

Hello,

Currently, I am having a problem with my BLE application. I am using nRF5_SDK_17.0.2_d674dde version. The BLE can advertise and can be seen by my phone. When my phone tries to connect to the service, I get NRF_ERROR_NO_MEM.

The NRF_ERROR_NO_MEM comes from conn_params_error_handler which is initialized via conn_params_init.

I am using NRF52832 with s132_nrf52_7.2.0_API soft device.

Parents
  • +1

    Hello,

    Please make sure that you are initializing app timer module in your code. I was able to replicate the same issue here after I removed the app_timer_init() call from my startup initialization routine. This is because the the app_timer_start() function in  ble_conn_params.c::on_connect()->conn_params_negotiation() will return with NRF_ERROR_NO_MEM if the module is not initialized.

Reply
  • +1

    Hello,

    Please make sure that you are initializing app timer module in your code. I was able to replicate the same issue here after I removed the app_timer_init() call from my startup initialization routine. This is because the the app_timer_start() function in  ble_conn_params.c::on_connect()->conn_params_negotiation() will return with NRF_ERROR_NO_MEM if the module is not initialized.

Children
No Data
Related