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

sd_ble_gattc_write() returns NRF_ERROR_BUSY. Why?

hi, nordic staff.

i'm working at s110(v6.0.0) and s120(v1.0.0). s110 provides notification and indication.

when s120 receives indication value from s110, s120 returns confirmation using sd_ble_gattc_hv_confirm() and sends back data using sd_ble_gattc_write() which write_op is BLE_GATT_OP_WRITE_REQ and get NRF_ERROR_BUSY error code.

before calling sd_ble_gattc_write(), i'm waiting BLE_GATTC_EVT_WRITE_RSP event for each call.

i wonder why becomes busy. please, give me a tip.

  • I have the same problem. have not found a solution yet. Does NRF_ERROR_BUSY halt the execution of the SoftDevice? For me, it breaks;

  • I'm having trouble understanding exactly what you are doing. Can you please edit your question? Please try to be a bit more clear, including some code might also be of help, and specify when you get NRF_ERROR_BUSY error code.

  • I got the NRF_ERROR_BUSY as soon as I tried to do a service discovery. The problem for me was, that I was using APP_ERROR_CHECK after calling the softdevice which put my program in the app error handler which in turn ended in an infinite loop. I had to exclude the NRF_ERROR_BUSY from going in the infinite loop. Of course, I will change the app error handler when I am finished with debugging and developing.

Related