error code 13313 (0x3401) returned by ble_nus_string_send ?

RE: error code 13313 (0x3401) returned by ble_nus_string_send ?

Homer Lu — Thu, 19 Apr 2018 05:44:18 GMT

I am using SDK v14.2, NRF52832

// m_nus register a event handler ble_nus_on_ble_evt() by using marco BLE_NUS_DEF

BLE_NUS_DEF(m_nus);

// All event will be handled by ble_nus_on_ble_evt(), NOT only NUS related events

// If BLE_GAP_EVT_CONNECTED event comes,

// ble_nus_on_ble_evt() calls on_connect() then set p_nus->conn_handle to p_ble_evt->evt.gap_evt.conn_handle;

// (ble_nus.c LN63)

// That means "Any new connection will set m_nus.conn_handle to be the new connect handle"

// to resolve this issue, i use following code

// but this works only if you have only 1 peripheral

static ble_nus_t m_nus;
static void wrapper_ble_nus_on_ble_evt(ble_evt_t const * p_ble_evt, void * p_context)
{
uint16_t conn_handle;
uint16_t role;
ble_nus_t * p_nus = (ble_nus_t *)p_context;

if ((p_nus == NULL) || (p_ble_evt == NULL)) {
return;
}

conn_handle = p_ble_evt->evt.gap_evt.conn_handle;
role = ble_conn_state_role(conn_handle);

if (role == BLE_GAP_ROLE_PERIPH) {
ble_nus_on_ble_evt(p_ble_evt, p_context);
}
}
NRF_SDH_BLE_OBSERVER(m_nus_obs, BLE_NUS_BLE_OBSERVER_PRIO, wrapper_ble_nus_on_ble_evt, &m_nus);

RE: error code 13313 (0x3401) returned by ble_nus_string_send ?

David Elvig — Sun, 25 Mar 2018 21:37:53 GMT

I'm getting error 13313 on calls to:

    err_code = sd_ble_gatts_hvx(p_midi->conn_handle, &hvx_params);

(err_code == BLE_ERROR_GATTS_SYS_ATTR_MISSING)

I've tried adding the following code to

ble_evt_handler() {
...
switch(p_ble_evt->header.evt_id) {
...
case BLE_GATTS_EVT_SYS_ATTR_MISSING:
     err_code = sd_ble_gatts_sys_attr_set(m_conn_handle, NULL, 0, 0);               APP_ERROR_CHECK(err_code);
     break;
...

A breakpoint in this case never gets caught.

I added code to the end of the code in ble_evt_handler()

      case BLE_GAP_EVT_CONNECTED:
         // actually this calls the customer service's onConnect handler,
         // which calls...

         sd_ble_gatts_sys_attr_set(p_midi->conn_handle, NULL, 0, 0);

That eliminates the 13313 error, but now a new error presents in the call to sd_ble_gatts_hvx() (8).

This appears to be because I have the Characteristic set to Notify, and the nRF Connect app has not yet started responding to Notify events.

I "eat" the error 8 as long as it persists, and that error stops occurring when I press the "Toggle Notifications" button (a green triangle adjacent to the Characteristic's UUID). I discovered this by accident.

So... I think I'm on to something, but I am not sure I have the best practices going.
For example, the BLE_GATTS_EVT_SYS_ATTR_MISSING never fired

Any guidance?


Thanks!

RE: error code 13313 (0x3401) returned by ble_nus_string_send ?

alex kim — Thu, 22 Mar 2018 06:30:59 GMT

"static void ble_evt_handler (ble_evt_t const * p_ble_evt, void * p_context)" contains the corresponding case statement
Did you add "case BLE_GATTS_EVT_SYS_ATTR_MISSING:" to any function in ble_uart_peripheral application?

RE: error code 13313 (0x3401) returned by ble_nus_string_send ?

alex kim — Wed, 21 Mar 2018 04:27:17 GMT

4. "<error> ble_gatt: sd_ble_gap_data_length_update () (request) on connection 0x0 returned unexpected value 0x13." Is output to the terminal.

==> In NUS example in the nRF5 SDK v14, NRF_SDH_BLE_GAP_EVENT_LENGTH is 3 and it's not proper value. Please change it from 3 to 5 or 6

Thanks to JustinLee.

But I have not solved "<error> app: ERROR 13313 [Unknown error code] at :0" yet.

RE: error code 13313 (0x3401) returned by ble_nus_string_send ?

alex kim — Mon, 19 Mar 2018 10:44:37 GMT

Thanks for your advice

When I checked it, I found the case statement in the function void ble_evt_handler (ble_evt_t const * p_ble_evt, void * p_context).

I took the test with the procedure below.


1. Power on the PCA10040. 
2. Run nRFToolbox -> UART on my cell phone. 
3. Press the 'connect' button on my cell phone 
4. "<error> ble_gatt: sd_ble_gap_data_length_update () (request) on connection 0x0 returned unexpected value 0x13." Is output to the terminal. 
5. After the BLE connection, data is received on my cell phone. 
6. Click Disconnect. 
7. My phone does not receive data 
8. Press the Connect button again. 
9. "<error> ble_gatt: sd_ble_gap_data_length_update () (request) on connection 0x0 returned unexpected value 0x13. <info> app: Connected <error> app: Fatal error <error> app: ERROR 13313 [Unknown error code] at: 0 " is output to the terminal. 
10. While operating the above procedure, I set the breakpoint at BLE_GATTS_EVT_SYS_ATTR_MISSING and run the program. The program at breakpoint did not stop

RE: error code 13313 (0x3401) returned by ble_nus_string_send ?

FormerMember — Mon, 19 Mar 2018 09:37:25 GMT

Error code 13313 = 0x 3401 = BLE_ERROR_GATTS_SYS_ATTR_MISSING

The reason for the error code is that the system attributes haven't been set. In our SDK, "gatts_cache_manager" --> gscm_local_db_cache_apply() handles this upon the event BLE_ERROR_GATTS_SYS_ATTR_MISSING.

If you don't use gatt_cache_manager and gatts_chache_manager, your will have to make your application handle this. If your application doesn't use bonding, you can do 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;

RE: error code 13313 (0x3401) returned by ble_nus_string_send ?

alex kim — Fri, 16 Mar 2018 08:36:22 GMT

Thanks for your answer

RE: error code 13313 (0x3401) returned by ble_nus_string_send ?

FormerMember — Fri, 16 Mar 2018 08:12:23 GMT

Which error code does ble_nus_string_send() return?

Could you double check the value of all the parameters that are passed into ble_nus_string_send() at runtime? (debug mode) Could you also write their value here?

RE: error code 13313 (0x3401) returned by ble_nus_string_send ?

alex kim — Thu, 15 Mar 2018 07:10:35 GMT

Thanks for your answer.
I have attached a debug message.
I modified the code as advised, but the same thing.
Please advise.

RE: error code 13313 (0x3401) returned by ble_nus_string_send ?

FormerMember — Tue, 13 Mar 2018 11:34:45 GMT

Could you double check the value of "length" that is being passed to ble_nus_string_send?

I would think the correct length should be the following:

uint16_t length = sizeof(string)/sizeof(uint8_t);

RE: error code 13313 (0x3401) returned by ble_nus_string_send ?

alex kim — Tue, 13 Mar 2018 10:45:59 GMT

Thank you for your quick response.
Please refer to the attached file below.

RE: error code 13313 (0x3401) returned by ble_nus_string_send ?

FormerMember — Tue, 13 Mar 2018 10:21:50 GMT

By default, the maximum length of a notification packet is 20 bytes. For "enabling" increased MTU size, there has to be an MTU exachange, where both devices agree on the new length.

In your case, what is the result from the MTU exchange between the nRF52 and the phone?