This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

BLE_APP_UART GATT Error 0x85

Hello ,

We are using the following.

Module: Bm833 (nRF52833) from Fanstel

Softdevice: S140 7.0.0

SDK: nRF5SDK17009d13099

Sample code: ble_app_uart

 We have added the buttonless DFU service in the ble_app_uart example and it is working fine.

We have around 20 30 modules and all are working except 2 or 3 which continuously resets and we are not able to connect it through the nRFconnect mobile app. 

When we try to connect them the application shows the Gatt Error 0x85. We went through various blogs for a similar issue but not able to find the solution.

The parameters we use are as below.

#define APP_ADV_INTERVAL 64 /**< The advertising interval (in units of 0.625 ms. This value corresponds to 40 ms). */

#define APP_ADV_DURATION 18000 /**< The advertising duration (180 seconds) in units of 10 milliseconds. */

#define MIN_CONN_INTERVAL MSEC_TO_UNITS(20, UNIT_1_25_MS) /**< Minimum acceptable connection interval (20 ms), Connection interval uses 1.25 ms units. */
#define MAX_CONN_INTERVAL MSEC_TO_UNITS(60, UNIT_1_25_MS) /**< Maximum acceptable connection interval (75 ms), Connection interval uses 1.25 ms units. */
#define SLAVE_LATENCY 0 /**< Slave latency. */
#define CONN_SUP_TIMEOUT MSEC_TO_UNITS(4000, UNIT_10_MS) /**< Connection supervisory timeout (4 seconds), Supervision Timeout uses 10 ms units. */
#define FIRST_CONN_PARAMS_UPDATE_DELAY APP_TIMER_TICKS(5000) /**< Time from initiating event (connect or start of notification) to first time sd_ble_gap_conn_param_update is called (5 seconds). */
#define NEXT_CONN_PARAMS_UPDATE_DELAY APP_TIMER_TICKS(30000) /**< Time between each call to sd_ble_gap_conn_param_update after the first call (30 seconds). */
#define MAX_CONN_PARAMS_UPDATE_COUNT 3 /**< Number of attempts before giving up the connection parameter negotiation. */

We tried to erase and reprogram the one board. It fixed the issue but it is not feasible to any kind of actual product.

Is there any particular page that we need to erase? 

Can anyone help us on fixing this?

Parents
  • Hi,

    Are the failing devices fresh devices, or have they been sued for development? Since you are able to recover from the error by performing an erase all and programming the device again, I suspect you have some old settings or something in flash. Maybe you could read the flash content from one of the failing devices and compare it to the flash content of one of the working devices and pay extra attention to the bootloader and mbr settings page.

Reply
  • Hi,

    Are the failing devices fresh devices, or have they been sued for development? Since you are able to recover from the error by performing an erase all and programming the device again, I suspect you have some old settings or something in flash. Maybe you could read the flash content from one of the failing devices and compare it to the flash content of one of the working devices and pay extra attention to the bootloader and mbr settings page.

Children
No Data
Related