ble_nus_data_send error

RE: ble_nus_data_send error

Einar Thorsrud — Thu, 10 Sep 2020 12:14:49 GMT

Hi,

[quote user="eleven-x_devteam"]But You mean putting sd_ble_gatts_sys_attr_set in the BLE_GAP_EVT_CONNECTED case of ble evt handler like the code below?[/quote]

Yes. This is just to set it as early as possible.

[quote user="eleven-x_devteam"]I found these 2 posts below about the errors and I filtered out the errors so that the device will not be reset by app error check and it seems the issues were fixed. Does it also make sense?[/quote]

I am not sure how this is relevant, but this post provided a viable solution, as long as you are happy with the ble_nus_data_send() call failing silently and you set the system attributes later. The key is that this will fail until the system attributes is set, and you can handle it in several different ways.

RE: ble_nus_data_send error

eleven-x_devteam — Wed, 09 Sep 2020 14:29:45 GMT

Thank you for your answer.

I have already the code in the BLE_GATTS_EVT_SYS_ATTR_MISSING case of ble evt handler.

But You mean putting sd_ble_gatts_sys_attr_set in the BLE_GAP_EVT_CONNECTED case of ble evt handler like the code below?

static void ble_evt_handler(ble_evt_t const* p_ble_evt, void* p_context)

{

uint32_t err_code;

switch(p_ble_evt->header.evt_id)

{

case BLE_GAP_EVT_CONNECTED:

m_conn_handle = p_ble_evt->evt.gap_evt.conn_handle;

err_code = nrf_ble_qwr_conn_handle_assign(&m_qwr, m_conn_handle);

APP_ERROR_CHECK(err_code);

err_code = sd_ble_gatts_sys_attr_set(m_conn_handle, NULL, 0, 0);

APP_ERROR_CHECK(err_code);

break;

This issue happens just sometimes with ble connecting & disconnecting with other scheduled jobs.

Also, there is another reset with sd_ble_gap_conn_param_update returning NRF_ERROR_INVALID_STATE in the same test condition.

I found these 2 posts below about the errors and I filtered out the errors so that the device will not be reset by app error check and it seems the issues were fixed. Does it also make sense?

https://devzone.nordicsemi.com/f/nordic-q-a/50227/ble-uart-issue/200615#200615

https://devzone.nordicsemi.com/f/nordic-q-a/52433/stopping-ble_conn_params-c-s-timers-while-supporting-concurrent-connections/211500#211500

RE: ble_nus_data_send error

eleven-x_devteam — Wed, 09 Sep 2020 14:24:28 GMT

Thank you for your answer!

RE: ble_nus_data_send error

Einar Thorsrud — Wed, 09 Sep 2020 12:45:21 GMT

Hi,

As allready mentioned, the error code is BLE_ERROR_GATTS_SYS_ATTR_MISSING. You can probably fix the issue by calling this before (for instance when handling the connected event):

err_code = sd_ble_gatts_sys_attr_set(m_conn_handle, NULL, 0, 0);
APP_ERROR_CHECK(err_code);

RE: ble_nus_data_send error

hmolesworth — Tue, 08 Sep 2020 18:36:28 GMT

It's here, in ble_gatts.h, 0x3401:

#define BLE_ERROR_GATTS_SYS_ATTR_MISSING    (NRF_GATTS_ERR_BASE + 0x001) /**< System Attributes missing. */

* @retval ::BLE_ERROR_GATTS_SYS_ATTR_MISSING System attributes missing, use @ref sd_ble_gatts_sys_attr_set to set them to a known value.

Maybe there is a full decoded list in the docs, but usually I scroll back through the nested definitions; not so helpful but maybe a starting point