strange error code 13313 (0x3401) returned by sd_ble_gatts_hvx()

RE: strange error code 13313 (0x3401) returned by sd_ble_gatts_hvx()

sam — Tue, 07 Jun 2016 02:10:13 GMT

Hi Martin,

i have the same problem with yours, my sd_ble_gatts_hvx always return 0x08 because I can't find a way t enable the notify, i tried using sd_ble_gatts_sys_attr_set when device is re-connected but not works, please let me know if you have solved the problem, thanks..

RE: strange error code 13313 (0x3401) returned by sd_ble_gatts_hvx()

Martin — Fri, 18 Apr 2014 10:39:33 GMT

I tested that for attributes with notify I have to use sd_ble_gatts_hvx() and for attributes without notify I use sd_ble_gatts_value_set(). So I made custom function with branching according what type of attribute to update and it seems to work well...

uint32_t ble_app_usr_attr_update(USR_ATTR_T *p_usr_attr)
{
  uint32_t err_code;
  ble_gatts_hvx_params_t params;
  uint16_t len=p_usr_attr->length;
  
  memset(&params, 0, sizeof(params));
  if ((p_usr_attr->props.notify!=0) || (p_usr_attr->props.indicate!=0))
    { 
    if (p_usr_attr->props.notify!=0)
      params.type=BLE_GATT_HVX_NOTIFICATION;
    if (p_usr_attr->props.indicate!=0) 
      params.type=BLE_GATT_HVX_INDICATION;
    params.handle=p_usr_attr->app_char_handles.value_handle;
    params.p_data=p_usr_attr->data;
    params.p_len=&len;
    err_code=sd_ble_gatts_hvx(ble_conn_handle, &params);
    }
  else 
    err_code=sd_ble_gatts_value_set(p_usr_attr->app_char_handles.value_handle, 0, &len, p_usr_attr->data);
  DPRINTF("BLE usr.attr update of service %u: len=%u, conn_h=%u, val_h=%u, err=%04Xh\n", p_usr_attr->service_index, *params.p_len, ble_conn_handle, p_usr_attr->app_char_handles.value_handle, err_code);
  return(err_code); 
}

I still get error 8 if notify is not enabled on the client side but the attribue value is updated successfully so I ignore this error in this case. When client enable notify it returns 0 (success). Attributes without notify on server side updated by sd_ble_gatts_value_set() returns 0 (success) and updated value can be readed by client as expected. As this works I keep this code and going forward...

RE: strange error code 13313 (0x3401) returned by sd_ble_gatts_hvx()

Charles Horkin — Mon, 07 Apr 2014 22:03:22 GMT

Having same issue...let me know if you resolve it.

RE: strange error code 13313 (0x3401) returned by sd_ble_gatts_hvx()

Martin — Mon, 07 Apr 2014 11:07:22 GMT

In comments of BLE_App_UART code I can found: "This function returns NRF_ERROR_INVALID_STATE if the device is not connected to a peer or if the notification of the RX characteristic was not enabled by the peer. It returns NRF_ERROR_NULL if the pointer p_nus is NULL."

So this seems that it's normal to get NRF_ERROR_INVALID_STATE when client didn't enabled notification yet. OK but what should I do then? I still need to update the value that client could read it itself by read command. It is already updated by sd_ble_gatts_hvx so could I ignore error int his case? Or should I need to use different function? What about sd_ble_gatts_value_set ? Then I would need make a branching and test some way if notification was or wasn't enabled and call 2 different function for each case.

RE: strange error code 13313 (0x3401) returned by sd_ble_gatts_hvx()

Martin — Fri, 04 Apr 2014 18:01:07 GMT

After I moved sd_ble_gatts_sys_attr_set(ble_conn_handle, NULL, 0) to BLE_GAP_EVT_CONNECTED event I'm getting error 8 - NRF_ERROR_INVALID_STATE instead of 0x3401, otherwise the same...

Body of my update attr func:

  memset(&params, 0, sizeof(params));
  params.type=BLE_GATT_HVX_NOTIFICATION;
  params.handle=p_svcs->app_char_handles.value_handle;
  params.p_data=p_usr_attr->data;
  params.p_len=&len;
  err_code=sd_ble_gatts_hvx(ble_conn_handle, &params);

RE: strange error code 13313 (0x3401) returned by sd_ble_gatts_hvx()

Martin — Fri, 04 Apr 2014 17:13:41 GMT

BTW it would be very helpful to have some single document with all error codes because tracking by error numbers is hard as it's defined by combinations like 0x2000+0x0100+0x0030+0x0001 and I cannot simply search for 0x2131 string...

RE: strange error code 13313 (0x3401) returned by sd_ble_gatts_hvx()

Martin — Fri, 04 Apr 2014 16:58:00 GMT

I tried again with some more printings on event but found that BLE_GATTS_EVT_SYS_ATTR_MISSING event didn't come so sd_ble_gatts_sys_attr_set() is not called. I only captured event BLE_GAP_EVT_CONN_PARAM_UPDATE on which I do nothing - shoul I? I tried multiple read/write from client and write (notify) on server but BLE_GATTS_EVT_SYS_ATTR_MISSING didn't come up. When I turned notification on the client I got BLE_GATTS_EVT_WRITE (BLE remote client write to CCCD handle: 16) and after this happen the error disappear (code 0) on notify the attribute. If I disable notification on client and notify again on server I got error 8 but I can read new value if I tap read button on client.

Here's my debug log: bleinit OK advstart OK BLE app event: 10h BLE client connected, handle=2579 BLE app event: 12h BLE connection parameters updated

seta[1]=20 // this I use to set atribute value and notify (calls sd_ble_gatts_hvx) BLE usr.attr update: len=1, conn_h=2579, svc_h=12, val_h=14, err=3401h OK seta[1]=30 BLE usr.attr update: len=1, conn_h=2579, svc_h=12, val_h=14, err=3401h OK BLE app event: 50h BLE usr.attr update from remote client: val_h=14, len=1, 1st Byte=50h seta[1]=40 BLE usr.attr update: len=1, conn_h=2579, svc_h=12, val_h=14, err=3401h OK BLE app event: 50h

// I enabled notification on client BLE remote client write to CCCD handle: 16 seta[1]=41 BLE usr.attr update: len=1, conn_h=2579, svc_h=12, val_h=14, err=0000h OK BLE app event: 01h BLE packet was transmitted, packet count: 1 seta[1]=42 BLE usr.attr update: len=1, conn_h=2579, svc_h=12, val_h=14, err=0000h OK BLE app event: 01h BLE packet was transmitted, packet count: 1 BLE app event: 50h BLE remote client write to CCCD handle: 16

// I disabled notification on client seta[1]=43 BLE usr.attr update: len=1, conn_h=2579, svc_h=12, val_h=14, err=0008h OK

RE: strange error code 13313 (0x3401) returned by sd_ble_gatts_hvx()

Ole Morten — Mon, 31 Mar 2014 14:22:44 GMT

I may have overlooked this, but as I said above, you could end up seeing the 0x3401 error right after connection. However, it should go away as soon as all events are handled, and the sd_ble_gatts_sys_attr_set() function has been called. (If you absolutely need to avoid seeing this error at all, you can try calling the _set() function from the connected event.) Do you see other behavior?

RE: strange error code 13313 (0x3401) returned by sd_ble_gatts_hvx()

Ole Morten — Mon, 24 Mar 2014 09:28:37 GMT

If you already have this case, I'd expect this error to be returned only for a very short time, and then disappear as soon as the application has replied to the event.

If you know that you'll never have any system attributes stored (i.e. you don't use bonding), it should be fine to move the setting of system attributes to the connected event, if you for some reason need to avoid seeing this error at all.

RE: strange error code 13313 (0x3401) returned by sd_ble_gatts_hvx()

Martin — Fri, 21 Mar 2014 19:51:17 GMT

In current project I dont need bonding, it's based on ble-lbs where no bondmgr is used (no ble_bondmngr_cfg.h). CCCD setting I leaved same

memset(&cccd_md, 0, sizeof(cccd_md)) BLE_GAP_CONN_SEC_MODE_SET_OPEN(&cccd_md.read_perm); BLE_GAP_CONN_SEC_MODE_SET_OPEN(&cccd_md.write_perm); cccd_md.vloc=BLE_GATTS_VLOC_STACK; cccd_md.vlen=0;

RE: strange error code 13313 (0x3401) returned by sd_ble_gatts_hvx()

Martin — Fri, 21 Mar 2014 19:43:13 GMT

I already have this case block in on_ble_evt() function except without error checking. I added APP_ERROR_CHECK(err_code); line and no error appeared.

RE: strange error code 13313 (0x3401) returned by sd_ble_gatts_hvx()

Ole Morten — Fri, 21 Mar 2014 10:24:09 GMT

As the error suggests, it means that the softdevice doesn't yet have a set of system attributes. :-)

I'd recommend you to read this document to better understand the concept of bonding with regard to our softdevice, since it also applies to the system attributes.

As you can see, bonding data is split between encryption keys and the system attributes. System attributes includes for example values for CCCDs, and the softdevice therefore needs to get those before sending any notification. Hence, when you try to send a notification, if the peer device have not yet written to the CCCDs, the softdevice will ask the application whether it has any previous bonding data to be used, by giving a BLE_GATTS_EVT_SYS_ATTR_MISSING. If the device does use bonding, the bond manager will normally handle this event, and pass back whatever data has previously been written.

However, the system attributes are requested with the same event no matter if the device use bonding or not (the softdevice doesn't really know that). If a device does not use bonding, but in this case, you can just reply like this:


case BLE_GATTS_EVT_SYS_ATTR_MISSING:
    err_code = sd_ble_gatts_sys_attr_set(m_conn_handle, NULL, 0);
    APP_ERROR_CHECK(err_code);
    break;

No matter which of these happens, a call to sd_ble_gatts_hvx() may get this error back if it's done at the exact right time, but if the call is retried just a short time later, this error should disappear, once either the application or the bond manager have set system attributes.

RE: strange error code 13313 (0x3401) returned by sd_ble_gatts_hvx()

Martin — Thu, 20 Mar 2014 17:31:18 GMT

Aha, OK, BLE stack use higher error numbers. I cannot find them by search because of there are composed by addind 0x3000 + 0x400 + 1 that is BLE_ERROR_GATTS_SYS_ATTR_MISSING but still don't have idea what this means. I have attribute set by button_char_add() from original BLE LBS demo.