RE: OOB pairing central

Artur — Mon, 05 Oct 2015 21:02:24 GMT

I realized that function sd_ble_gap_auth_key_reply is never called on the central. Because when I call dm_security_setup_req this wariant is chosen:

if ((p_handle->device_id != DM_INVALID_ID) ||
        (m_connection_table[p_handle->connection_id].bonded_dev_id != DM_INVALID_ID))
    {
        p_handle->device_id = m_connection_table[p_handle->connection_id].bonded_dev_id;

        //Already bonded device, encrypt the link.
        err_code = sd_ble_gap_encrypt(m_connection_table[p_handle->connection_id].conn_handle,
            &m_bond_table[p_handle->connection_id].peer_enc_key.master_id,
            &m_bond_table[p_handle->connection_id].peer_enc_key.enc_info);
    }

I found the confirmation in degug log:

[DM]:[00]:[Block ID 0x0003F800]:Loading bond information at 20002e44, size 0x0000001C, offset 0x00000018.

I thought that when i reset device or load code to flash I remove it. But it does not work. How can I do it?

RE: OOB pairing central

Petter Myhre — Mon, 05 Oct 2015 11:00:52 GMT

Shouldn't you get the BLE_GAP_EVT_AUTH_KEY_REQUEST on the central side as well? And reply with sd_ble_gap_auth_key_reply()? See this MSC.