GATT CONN TERMINATE LOCAL HOST occurs when bonding with Android

RE: GATT CONN TERMINATE LOCAL HOST occurs when bonding with Android

Simonr — Mon, 17 Jan 2022 07:55:47 GMT

Not as far as I can tell in terms of enabling bonding at least. I assume you have added functions like ble_stack_init, scan_init, and so on.

Best regards,

Simon

RE: GATT CONN TERMINATE LOCAL HOST occurs when bonding with Android

sdi_kei — Sat, 15 Jan 2022 08:13:03 GMT

Hello.

I have included the peer manager and pm_evt_handler () in my project with the code settings below. Is there anything else I need?

#define SEC_PARAM_BOND            1                                /**< Perform bonding. */
#define SEC_PARAM_MITM            0                                /**< Man In The Middle protection not required. */
#define SEC_PARAM_LESC            1                                /**< LE Secure Connections not enabled. */
#define SEC_PARAM_KEYPRESS        0                                /**< Keypress notifications not enabled. */
#define SEC_PARAM_IO_CAPABILITIES BLE_GAP_IO_CAPS_NONE             /**< No I/O capabilities. */
#define SEC_PARAM_OOB             0                                /**< Out Of Band data not available. */
#define SEC_PARAM_MIN_KEY_SIZE    7                                /**< Minimum encryption key size. */
#define SEC_PARAM_MAX_KEY_SIZE    16                               /**< Maximum encryption key size. */

static void peer_manager_init(void)
{
    ble_gap_sec_params_t sec_param;
    ret_code_t err_code;

    err_code = pm_init();
    APP_ERROR_CHECK(err_code);

    memset(&sec_param, 0, sizeof(ble_gap_sec_params_t));

    sec_param.bond           = SEC_PARAM_BOND;
    sec_param.mitm           = SEC_PARAM_MITM;
    sec_param.lesc           = SEC_PARAM_LESC;
    sec_param.keypress       = SEC_PARAM_KEYPRESS;
    sec_param.io_caps        = SEC_PARAM_IO_CAPABILITIES;
    sec_param.oob            = SEC_PARAM_OOB;
    sec_param.min_key_size   = SEC_PARAM_MIN_KEY_SIZE;
    sec_param.max_key_size   = SEC_PARAM_MAX_KEY_SIZE;
    sec_param.kdist_own.enc  = 1;
    sec_param.kdist_own.id   = 1;
    sec_param.kdist_peer.enc = 1;
    sec_param.kdist_peer.id  = 1;

    err_code = pm_sec_params_set(&sec_param);
    APP_ERROR_CHECK(err_code);

    err_code = pm_register(pm_evt_handler);
    APP_ERROR_CHECK(err_code);

    return;
}

static void pm_evt_handler(pm_evt_t const * p_evt)
{
    pm_conn_sec_config_t conn_sec_config;

    pm_handler_on_pm_evt(p_evt);
    pm_handler_flash_clean(p_evt);

    switch (p_evt->evt_id) {
        case PM_EVT_BONDED_PEER_CONNECTED:
            break;

        case PM_EVT_CONN_SEC_START:
            break;

        case PM_EVT_CONN_SEC_SUCCEEDED:
            break;

        case PM_EVT_CONN_SEC_FAILED:
            break;

        case PM_EVT_CONN_SEC_CONFIG_REQ:
            // Even true didn't make sense.
            conn_sec_config.allow_repairing = false;
            pm_conn_sec_config_reply(p_evt->conn_handle, &conn_sec_config);
            break;

        case PM_EVT_CONN_SEC_PARAMS_REQ:
            break;

        case PM_EVT_STORAGE_FULL:
            break;

        case PM_EVT_ERROR_UNEXPECTED:
            break;

        case PM_EVT_PEER_DATA_UPDATE_SUCCEEDED:
            break;

        case PM_EVT_PEER_DATA_UPDATE_FAILED:
            break;

        case PM_EVT_PEER_DELETE_SUCCEEDED:
            break;

        case PM_EVT_PEER_DELETE_FAILED:
            break;
            
        case PM_EVT_PEERS_DELETE_SUCCEEDED:
            break;

        case PM_EVT_PEERS_DELETE_FAILED:
            break;

        case PM_EVT_LOCAL_DB_CACHE_APPLIED:
            break;

        case PM_EVT_LOCAL_DB_CACHE_APPLY_FAILED:
            break;

        case PM_EVT_SERVICE_CHANGED_IND_SENT:
            break;

        case PM_EVT_SERVICE_CHANGED_IND_CONFIRMED:
            break;

        case PM_EVT_SLAVE_SECURITY_REQ:
            break;

        case PM_EVT_FLASH_GARBAGE_COLLECTED:
            break;

        case PM_EVT_FLASH_GARBAGE_COLLECTION_FAILED:
            break;

        default:
            break;
    }

    return;
}

Best regards.

RE: GATT CONN TERMINATE LOCAL HOST occurs when bonding with Android

Simonr — Fri, 07 Jan 2022 13:19:26 GMT

Have you included the pm_evt_handler() function and peer manager library files in your project in order to include and add bonding to your project? Just setting the SEC_PARAM_BOND to 1 won't be sufficient in a project that hasn't implemented the peer manager at all.

Best regards,

Simon

RE: GATT CONN TERMINATE LOCAL HOST occurs when bonding with Android

sdi_kei — Fri, 07 Jan 2022 11:26:05 GMT

Hello.

sorry for being late.
I compared the project where my bonding fails with ble_app_hrs_c, but I still don't understand why it fails.

Do you have any advertisements?

Best regards.

RE: GATT CONN TERMINATE LOCAL HOST occurs when bonding with Android

Simonr — Tue, 21 Dec 2021 13:21:55 GMT

What kind of error do you see when trying to bond with your Android peripheral. Can you show me a screenshot of how you've set up the Android advertiser?

Please also note that, by default the ble_app_uart_c example project does not support bonding, so it makes sense that you won't be able to bond an Android device to it. If you try using the ble_app_hrs_c example where SEC_PARAM_BOND is set to 1, and bonding is implemented, that should work better.

Best regards,

Simon

RE: GATT CONN TERMINATE LOCAL HOST occurs when bonding with Android

sdi_kei — Tue, 21 Dec 2021 03:10:01 GMT

Hello.

Does that mean I have to register NUS GATT?
It is possible to connect with Android, and I think it is a matter of bonding at that time. So I think GATT has nothing to do with it.

If I need GATT, I have to add it to nRF Connect, but I don't know the data structure. Is there any material that describes the configuration?

Best regards.

RE: GATT CONN TERMINATE LOCAL HOST occurs when bonding with Android

Simonr — Mon, 13 Dec 2021 08:13:28 GMT

Did you add the Nordic UART service as part of your advertiser on Android, as the application scans peripheral devices and connects to a device that advertises with the NUS UUID in its advertisement report. After connecting, the application enables notifications on the device that delivers the Nordic UART Service.

Best regards,

Simon

RE: GATT CONN TERMINATE LOCAL HOST occurs when bonding with Android

sdi_kei — Fri, 10 Dec 2021 00:43:40 GMT

Hello.

I tried to see if it can be bonded with ble_app_uart_c on Android.
As a result, bonding was not possible.

I pressed Bond from nRF Connect because Android didn't show the pairing request, but it didn't bond.
Advertising Data was set to UUID only, and Configure GATT server was set to "Sample configuration".

Best regards.

RE: GATT CONN TERMINATE LOCAL HOST occurs when bonding with Android

Simonr — Wed, 08 Dec 2021 10:32:59 GMT

Before we go to a code review and make this ticket private. Have you tried using I.E. the default ble_app_uart_c example project to connect to, and does that result in this local host termination as well?

Since you're using the Android as a peripheral, how have you set up the advertiser in the nRFConnect app? What advertising data have you added and what services have you added in the Configure GATT server of nRFConnect. It's also worth tweaking the connection parameters and connection supervision timeout in your central applicaton.

Best regards,

Simon

RE: GATT CONN TERMINATE LOCAL HOST occurs when bonding with Android

sdi_kei — Wed, 08 Dec 2021 01:26:27 GMT

Hello.

Isn't GATT CONN TERMINATE LOCAL HOST from Android?
The device used for connection is XPERIA SO-03J, and the application used is nRF Connect.
The sample sources I referred to are "ble_app_blinky_c" and "ble_app_uart_c" of ble_central.
Should I share the code I'm using? In that case, would you please make it a private ticket?

It's difficult to change because we work with people other than me in software development.

Best regards.

RE: GATT CONN TERMINATE LOCAL HOST occurs when bonding with Android

Simonr — Tue, 07 Dec 2021 13:29:01 GMT

Does this GATT CONN TERMINATE LOCAL HOST error come from the Android? What Android device is this you're trying to connect to, and are you using an Android app for BLE scanning and connecting (like nRFConnect) or are you using the standard settings/Bluetooth menu?

What example project have you based your nRF52832 application on here? Are you able to connect and bond with the Android device if you try using a default SDK example project? Please also note that If you are using v17.0.0 for development, it is strongly recommended to switch to v17.0.2. As it is a bug fix release to v17.0.0 which had some bug fixes properly handling errata.

Best regards,

Simon