sd_ble_gatts_hvx gives error as NRF_ERROR_RESOURCES and my code gets stuck

RE: sd_ble_gatts_hvx gives error as NRF_ERROR_RESOURCES and my code gets stuck

Edvin — Mon, 18 Nov 2024 14:42:20 GMT

So what does it return?

I did notice that you didn't follow the suggestion that I mentioned in my pseudo code snippet, to leave the event and trigger the sending from another place (see what I did with the send_data_flag parameter).

However, when you are stuck, what does ble_cus_sensor_state_update() return? It is not NRF_ERROR_RESOURCES, because according to your ble_cus_send_sensor_data(), because if it did, it would be passed onto the APP_ERROR_CHECK(err_code), and the application would restart.

Does it return BLE_ERROR_GATTS_SYS_ATTR_MISSING? If so, what is the expected behavior? Because now it will keep trying, but your timer parameter will not change.

Best regards,

Edvin

RE: sd_ble_gatts_hvx gives error as NRF_ERROR_RESOURCES and my code gets stuck

Mushtakh Shaikh — Mon, 18 Nov 2024 05:24:27 GMT

Hi Edwin,

Can you please suggest any changes if required?

Or any mistake in my implementations??

RE: sd_ble_gatts_hvx gives error as NRF_ERROR_RESOURCES and my code gets stuck

Mushtakh Shaikh — Fri, 15 Nov 2024 06:54:44 GMT

Yes, Edwin, it is stuck in ble_cus_send_sensor_data and the below function returns the error.

uint32_t ble_cus_sensor_state_update(ble_cus_t * p_cus, int8_t * p_buttons_states, int length, uint16_t conn_handle)
{
ble_gatts_hvx_params_t params;
uint16_t len = length;
uint32_t err_code;

memset(&params, 0, sizeof(params));
params.type = BLE_GATT_HVX_NOTIFICATION;//BLE_GATT_HVX_NOTIFICATION;
params.handle = p_cus->leds_states_char_handles.value_handle;
params.p_data = p_buttons_states;
params.p_len = &len;

return sd_ble_gatts_hvx(conn_handle, &params);
}

RE: sd_ble_gatts_hvx gives error as NRF_ERROR_RESOURCES and my code gets stuck

Edvin — Thu, 14 Nov 2024 14:17:39 GMT

Where is it stuck? In ble_cus_send_sensor_data()?

BR,

Edvin

RE: sd_ble_gatts_hvx gives error as NRF_ERROR_RESOURCES and my code gets stuck

Mushtakh Shaikh — Wed, 13 Nov 2024 10:42:03 GMT

devzone.nordicsemi.com/.../4861.main.c devzone.nordicsemi.com/.../7838.ble_5F00_cus.c devzone.nordicsemi.com/.../5775.ble_5F00_cus.h

Hi Edvin,

Now,as you mentioned, there are two different event hanler,
1. ble_evt_handler in main.c
2. ble_cus_on_ble_evt in ble_cus.c

Now, when I trying to send packets continuously,my code is getting stuck and I am unable to send the data to BLE.
I tried above suggestions, somehow it doesn't seem to work for me, as the code is getting stuck. Please check the code and let me know if any changes required in order to solve the issue.

I would really appreciate if you can let me know on how to apply your suggested changes in my code.

thanks

RE: sd_ble_gatts_hvx gives error as NRF_ERROR_RESOURCES and my code gets stuck

Edvin — Mon, 11 Nov 2024 14:54:30 GMT

Hello,

I believe you are waiting in an interrupt with equal or higher priority than the BLE_GATTS_EVT_HVN_TX_COMPLETE event (ble_evt_handler()).

In fact, I suspect that the interrupt you are waiting in is the ble_evt_handler(), or the equivalent handler that you registered for your custom service handler. As long as you are not leaving the interrupt, the BLE_GATTS_EVT_HVN_TX_COMPLETE event will not be able to execute, to tell your application that the softdevice has freed up some buffers.

So one way to handle this is to keep track of what you have queued successfully. So you need to queue up as much as you can, until your ble_cus_sensor_state_update() returns NRF_ERROR_RESOURCES. When it does, keep track of how much data you queued in your send_current_data(), and return from this function, so that the interrupt is released. Then you can wait for the BLE_GATTS_EVT_HVN_TX_COMPLETE event, which means that at least one of your packets was acked. Then you can set a flag in the TX_COMPLETE callback, that you can check in your main-loop, and use this to continue where you left off, queuing more packets, until it returns NRF_ERROR_RESOURCES again, or you have successfully queued all your packets.

Something like this:

volatile uint32_t packet_counter = 0;
volatile bool send_data_flag = false;

ble_evt_handler()
{
    ...
    case BLE_GATTS_EVT_HVN_TX_COMPLETE:
        if ( **check if more data needs to be sent**)
        {
            send_data_flag = true;
        }
}

send_data()
{
    for (int i=0; i<100; i++)
    {
        err = NRF_SUCCESS;
        while(err = NRF_SUCCESS)
        {
            sd_ble_gatts_hvx(...);
            if (err = NRF_SUCCESS)
            {
                packet_counter = i;
                i++;
            }
        }
        break;
    }
}
cust_data_handler()
{
    send_data_flag = true;
}

int main()
{
...
    while (true)
    {
        if (send_data_flag)
        {
            send_data_flag = false;
            send_data();
        }
        idle_state_handle();
    }
}

Best regards,

Edvin