This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

NRF52 NRF_ERROR_BUSY when calling ble_db_discovery_start()

Hi, I have nrf52 setup as central and peripheral.

As central it connects to another peripheral and everything works just fine. After it did connect I turn of peripheral and when I turn it on again NRF52 connects to it, but then I get NRF_ERROR_BUSY when calling ble_db_discovery_start Here is the log that leads to the error:

 0> APP:DEBUG:ble_db_discovery_on_ble_evt, evt_id=17
 0> APP:DEBUG:on_ble_central_evt
 0> APP:INFO:LBS central link 0x1 disconnected (reason: 8)
 0> APP:INFO:link 0x1 established, start discovery on it

Seems like its still discovering old connection or something like that? Any idea?

Thanks!

Parents
  • Petter, yes indeed discovery_in_progress is still true. I was expecting that discovery stops once we actually start using the service, but it seems not the case? Do I have to manually stop it somehow?

    ble_db_discovery_start() is called only at one place when we receive case BLE_GAP_EVT_CONNECTED event. so on the second call after we disconnected and reconnected to peripheral the discovery is still in progress for some reason.

Reply
  • Petter, yes indeed discovery_in_progress is still true. I was expecting that discovery stops once we actually start using the service, but it seems not the case? Do I have to manually stop it somehow?

    ble_db_discovery_start() is called only at one place when we receive case BLE_GAP_EVT_CONNECTED event. so on the second call after we disconnected and reconnected to peripheral the discovery is still in progress for some reason.

Children
No Data
Related