GATT_CONN_TERMINATE_LOCAL_HOST after 28-30s

[Dani]

Good morning,

I have designed a prototype based on nRF52840 and an application based on S140 v.6.1.0.

We have already assembled several prototypes and all of them have been working fine for weeks: we have created our own Android app and we have tested it with several Smartphones.

One of this equipments is the one I'm using for development, together with a defined Smartphone.

Up to yesterday, everythink was working fine but now, when I'm connecting the Smartphone with my development prototype, it perfectly connects but it always disconnects after 28-30seconds.

I have also tested with nRF Connect app: the same happens and in log register the message GATT_CONN_TERMINATE_LOCAL_HOST appears after 28-30s.

From this point, I have done some testing:

- With my Smartphone:

- I have tried to connect to a different prototype and it is connecting fine without any disconnection

- I have forgotten my prototype in order to enter passkey again --> This has not solved the problem with my prototype

- I have switched off and on back again bluetooth --> Same problem

- I have erased bluetooth cache in my smartphone --> Same problem

- With my prototype (nRF52840 based):

-I have tested same prototype with another Smartphone, and it is perfectly working.

- I have fully erased it with JFlash and I have flashed it again (bootloader, sd, boot_setting,app). Even, I have done this with different versions that were previously working without problems.

My smartphone is a Xiaomi Mi6, and I have been using it during my development stage.

Do you know which can be the reason of such behaviour?

Best regards,

Dani

[Dani]

Hi Amanda,

I'm very interested in knowing what I have asked in my previous answers.

But apart of this, and going deeper into this behaviour, I have solved this disconnections, but I do not know the reason. In fact, I have noticed that I receive the BLE_GATTC_EVT_HVX event. Then, according to (https://devzone.nordicsemi.com/f/nordic-q-a/30804/nrf-connect-for-android-disconnects-with-error-22-gatt-conn-terminate-local-host/149921#149921) I call 'sd_ble_gattc_hv_confirm' when this event is given and know device works without disconnections.

Dani

[Amanda Hsieh]

Hi Dani, 

Good to hear you fix the issue. 

Dani said:

Could you recommend us best scenario, or the rules to follow?

Check if this helps you devzone.nordicsemi.com/.../ and this note. 

Dani said:

What I do not understand (looking at nRF Connect app in my smartphone) is why notifications are received every 1 second (I send them every 62.5ms).

The central decides the connection interval and it may not accept the intervals proposed by the peripheral.

-Amanda H.

[Dani]

Thank you very much...

Now, when writting a wrong passkey, my device is reseted.

Which can be the reason? I have already implemented event PM_EVT_CONN_SEC_FAILED:

static void pm_evt_handler(pm_evt_t const * p_evt)
{
ret_code_t err_code;

pm_conn_sec_config_t config;
pm_conn_sec_status_t conn_sec_status;

pm_handler_on_pm_evt(p_evt);
pm_handler_disconnect_on_sec_failure(p_evt);
pm_handler_flash_clean(p_evt);

switch (p_evt->evt_id)
{

case PM_EVT_CONN_SEC_SUCCEEDED:

// Check if the link is authenticated (meaning at least MITM).
err_code = pm_conn_sec_status_get(p_evt->conn_handle, &conn_sec_status);
APP_ERROR_CHECK(err_code);

break;

case PM_EVT_CONN_SEC_FAILED:
m_ble_general.ble_conn_handle = BLE_CONN_HANDLE_INVALID;
break;

case PM_EVT_PEERS_DELETE_SUCCEEDED:
advertising_start();
break;

case PM_EVT_CONN_SEC_CONFIG_REQ:
config.allow_repairing = true;
pm_conn_sec_config_reply(p_evt->conn_handle, &config);
break;

case PM_EVT_BONDED_PEER_CONNECTED:
pm_local_database_has_changed();

break;

default:
break;
}
}

Please, find attached sniffer trace for this moment.

What do I have to correct to avoid these resets?

Dani.

Android_pairing_with_wrong_key.pcapng

[Amanda Hsieh]

Hi Dani, 

This is a different issue from the origianl. Please create a new support case with the debug log.

-Amanda H.