"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

[Edvin]

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;

[yokokawa]

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.

[Edvin]

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?

[yokokawa]

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

[Edvin]

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? 

[yokokawa]

Once you set the settings again, you were able to build. The following screen shows the result of the problem.

[Edvin]

Ok. good. So app_uart_put() returns 4 (NRF_ERROR_NO_MEM).

Is it app_fifo_put() inside app_uart_put() that returns NRF_ERROR_NO_MEM? I need you to check this. Try to set a breakpoint here and see if that triggers.

What is the size of your UART buffers? In the ble_app_uart_c example, it is called UART_RX_BUF_SIZE and UART_TX_BUF_SIZE, but it may be called something else in your application. It should be the second and third parameter in APP_UART_FIFO_INIT(). 

Best regards,

Edvin

[yokokawa]

Stopped at "return NRF_ERROR_NO_MEM" of "app_fifo_put ()".
The buffer size is 256.

--------------------------------------------------------------------------------------

#define UART_TX_BUF_SIZE 256 /**< UART TX buffer size. */
#define UART_RX_BUF_SIZE 256 /**< UART RX buffer size. */

--------------------------------------------------------------------------------------

[Edvin]

Ok. So that means that your buffer is full. 

Do you see anything printed on your uart from this chip? Is flow control enabled on the UART? 

Have you changed anything in the UART or FIFO library? 

What is your UART connected to?

[yokokawa]

1) Not printing with UART.
2) Flow control is enabled.
3) The FIFO library has not changed.
4) The UART is converted to USB (using the evaluation board) and connected to the PC.

[Edvin]

Can you try to disable the flow control? It is not always the computers interpret the flow control correctly when it goes through the segger chip on the DK.

Are you using the nRF52832 DK? You have not changed the UART pin configurations, right? They are still RX P0.08 and TX P0.06?

BR,

Edvin

[yokokawa]

1) EBSHSN (Evaluation board) is used.
2) Flow control can be disabled.
3) The UART pin is not changed.
---------------------------------------------------------------------------------
#define RX_PIN_NUMBER 8
#define TX_PIN_NUMBER 6
#define CTS_PIN_NUMBER 7
#define RTS_PIN_NUMBER 5
---------------------------------------------------------------------------------
* Flow control is enabled in “main.c”, but flow control is not set in the “pca10040.h” board setting.

* Even when flow control is prohibited, the same error occurred.

*If flow control was disabled, an overrun error occurred during reception.