• State Verified Answer
  • Replies 23 replies
  • Subscribers 68 subscribers
  • Views 4603 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 236349
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

"BLE_ERROR_GATTS_SYS_ATTR_MISSING" (0x3401) occurs during continuous BLE transmission

yokokawa

OS in development environment ：Windows7
HARD :(Taiyo Yuden)EBSHSN Series Evaluation Board : Central / Peripherals
CPU :(Nordic) nRF52832 / ARMR Cortex-M4F 32 bit processor 28-pin Land Grid Array / 15GPIOs / SWD
Soft Ver:nRF5_SDK_15.3.0_59ac345

“BLE_ERROR_GATTS_SYS_ATTR_MISSING” occurs when 2k bytes of data are sent repeatedly.
Please tell me how to resolve.

* This does not occur when sending a single shot.
* Peripheral device for one central vs. 4 peripheral communication
* The central and peripheral settings are the same.

------------------------< Setting >-------------------------
/* Communication cycle: 15ms to 30ms */
#define MIN_CONN_INTERVAL MSEC_TO_UNITS(15, UNIT_1_25_MS) /**< Minimum acceptable connection interval (15 ms) */
#define MAX_CONN_INTERVAL MSEC_TO_UNITS(30, UNIT_1_25_MS) /**< Maximum acceptable connection interval (30 ms) */
/* Data length: 247byte */
#define NRF_SDH_BLE_GATT_MAX_MTU_SIZE 247

------------------------< program >-------------------------
do
{
  uint16_t length = (uint16_t)index;
  err_code = ble_nus_data_send(&m_nus, data_array, &length, m_conn_handle);
  if ((err_code != NRF_ERROR_INVALID_STATE) &&
      (err_code != NRF_ERROR_RESOURCES) &&
      (err_code != NRF_ERROR_NOT_FOUND))
  {
      APP_ERROR_CHECK(err_code);   <---   (Error location)
  }
} while (err_code == NRF_ERROR_RESOURCES);
------------------------------------------------------------

Thanking you in advance

Parents
  • 0

    Hello,

    You say that ble_nus_data_send() returns BLE_GATTS_VAR_ATTR_LEN_MAX only when you send a lot of data? Does that mean that it initially return NRF_SUCCES, and then after a while, it returns BLE_GATTS_VAR_ATTR_LEN_MAX? Or does it return BLE_GATTS_VAR_ATTR_LEN_MAX immediately (on the first attempt)?

    What does the following event in your ble_evt_handler() look like?

            case BLE_GATTS_EVT_SYS_ATTR_MISSING:
            // No system attributes have been stored.
            err_code = sd_ble_gatts_sys_attr_set(m_conn_handle, NULL, 0, 0);
            APP_ERROR_CHECK(err_code);
            break;

  • 0 in reply to Edvin

    1) Returns BLE_ERROR_GATTS_SYS_ATTR_MISSING when a large amount of data is sent. NRF_SUCCES is returned at first, and BLE_ERROR_GATTS_SYS_ATTR_MISSING is returned after a while.
    ”BLE_ERROR_GATTS_SYS_ATTR_MISSING is not returned from the beginning.
    2) The structure of the BLE_GATTS_EVT_SYS_ATTR_MISSING event of ble_evt_handler () is the same.
    The BLE_GATTS_EVT_SYS_ATTR_MISSING event of ble_evt_handler () does not occur.

  • 0 in reply to yokokawa

    Hello,

    I suggest that you define DEBUG in your preprocessor defines. This way it will print a bit more info whenever you receive the "Fatal error" in the log. Let me know if you are not sure how to do this. I also need to know what compiler/IDE you use, then.

    "app_uart_put failed for index 0x00XX" means that app_uart_put failed. If you define DEBUG in your preprocessor defines, it should also tell you what app_uart_put returned, which may help pin point the issue.

    "Connection handle invalid" means that you are trying to send data to a connection handle that isn't valid. Are you connected to multiple devices?

    I don't know from where you call this, and with what conn_handle?

    I suspect that if you try to reply to something, then you should be aware of that the BLE_NUS_C_EVT_NUS_TX_EVT doesn't contain the correct conn_handle. (the ble_nus_c service isn't designed for multiple connections). 

    It is a simple fix. Add:

    ble_nus_c_evt.conn_handle = p_ble_evt->evt.gattc_evt.conn_handle;

    before:

    p_ble_nus_c->evt_handler(p_ble_nus_c, &ble_nus_c_evt);

    So:

    1: add DEBUG to your preprocessor defines

    2: From where do you call ble_nus_c_string_send()? And with what conn_handle?

  • 0 in reply to Edvin

    I understand the following causes.

    ---------------------------------------------------
    <warning> ble_nus_c: Connection handle invalid.
    <warning> ble_nus_c: Connection handle invalid.
    <warning> ble_nus_c: Connection handle invalid.
    ---------------------------------------------------

    When changing from [Release] to [Debug] to debug the UART, an error about missing file occurred.
Is the setting different between [Release] and [Debug]?
     

    ble_app_multilink_uart_centra.zip
  • 0 in reply to yokokawa

    Ok. So you are using Segger embedded studio. Changing from release to debug is not equivalent to defining DEBUG in the preprocessor defines. "Release" and "Debug" from that dropdown are two different sets of project settings, and it looks like the debug set isn't set up to deal with UART. Change it back to "Release", so that you have a working set of project settings. 

    Then what I want you to do is to right click your project, and click options:

    Then select "Common" in the top left, go to "Preprocessor" -> double click "Preprocessor Definitions" -> Add "DEBUG" to the top of your defines:

    Then monitor your log. What does it say?

  • 0 in reply to Edvin

    The setting was changed according to the instructions.
    The result after the build did not change.

  • 0 in reply to yokokawa

    So you are not able to revert to being able to build your project? Have you removed the path to app_fifo.h from your project settings? Or what did you change to trigger this error? 

Reply Children
Related