NRF_ERROR_BUSY while enabling several notifications

RE: NRF_ERROR_BUSY while enabling several notifications

Einar Thorsrud — Tue, 12 Oct 2021 14:41:24 GMT

Hi,

Yes, then waiting for BLE_GATTC_EVT_WRITE_RSP should do the trick. Could it be that you do not have a full overview of your application, and that some you start a new GATT procedure somewhere else? Perhaps you end up somehow making two calls to sd_ble_gattc_write() after the BLE_GATTC_EVT_WRITE_RSP? That is just speculation, though.

Have you done any debugging to see what happens? Do you get the BLE_GATTC_EVT_WRITE_RSP at some point after getting NRF_ERROR_BUSY returned from sd_ble_gattc_write()?

RE: NRF_ERROR_BUSY while enabling several notifications

User1321 — Tue, 12 Oct 2021 13:58:44 GMT

Since it is calling the sd_ble_gattc_write , i thought it was required to wait for the BLE_GATTC_EVT_WRITE_RSP event.

static uint32_t cccd_configure(uint16_t conn_handle, uint16_t cccd_handle, bool enable)
{
    //NRF_LOG_INFO("Configuring CCCD. CCCD Handle = %d, Connection Handle = %d",  cccd_handle,conn_handle);
    uint8_t buf[BLE_CCCD_VALUE_LEN];

    buf[0] = enable ? BLE_GATT_HVX_NOTIFICATION : 0;
    buf[1] = 0;

    ble_gattc_write_params_t const write_params =
    {
        .write_op = BLE_GATT_OP_WRITE_REQ,
        .flags    = BLE_GATT_EXEC_WRITE_FLAG_PREPARED_WRITE,
        .handle   = cccd_handle,
        .offset   = 0,
        .len      = sizeof(buf),
        .p_value  = buf
    };

    return sd_ble_gattc_write(conn_handle, &write_params);
}

RE: NRF_ERROR_BUSY while enabling several notifications

Einar Thorsrud — Tue, 12 Oct 2021 12:03:43 GMT

Hi,

You write that you get NRF_ERROR_BUSY from cccd_configure(), which is implemented in most service implementations.Most likely the issue is that a GATT procedure is already active, and you need to wait for it to finish. To know more we would need to know which function within cccd_configure() is it that returns this? The further down you follow this the better.