SDK_V10, S110_V8.0.0,
Just Works, getting error BLE_GAP_SEC_STATUS_CONFIRM_VALUE when bonding, attached file is Sniffer data. What is the problem?
SDK_V10, S110_V8.0.0,
Just Works, getting error BLE_GAP_SEC_STATUS_CONFIRM_VALUE when bonding, attached file is Sniffer data. What is the problem?
What does sd_ble_gap_sec_params_reply() return?
What does sd_ble_gap_sec_params_reply() return?
Because in file "device_manager_peripheral.c", before call "sd_ble_gap_sec_params_reply()", there are "keys_exchanged.keys_central.p_enc_key = NULL;" , so it will return error NRF_ERROR_INVALID_ADDR.
I will modify it to test more.
Hi, Martin:
I modify as below:
keys_exchanged.keys_central.p_enc_key = ¢ral_peer_enc_key; keys_exchanged.keys_central.p_id_key = &m_peer_table[m_connection_table[index].bonded_dev_id].peer_id; keys_exchanged.keys_central.p_sign_key = NULL; keys_exchanged.keys_periph.p_enc_key = &m_bond_table[index].peer_enc_key; keys_exchanged.keys_periph.p_id_key = NULL; keys_exchanged.keys_periph.p_sign_key = NULL; err_code = sd_ble_gap_sec_params_reply(p_ble_evt->evt.gap_evt.conn_handle, BLE_GAP_SEC_STATUS_SUCCESS, &m_application_table[0].sec_param, &keys_exchanged); if (err_code != NRF_SUCCESS) { DM_LOG("[DM]: Security parameter reply request failed, reason 0x%08X.\r\n", err_code); event_result = err_code; notify_app = false; }
But after bonding successfully several times, it still return Confirm Value Failed error. Please check the Sniffer data:
Hi, Martin:
Do you have any suggestion?
Hi Matt,
Sorry for the long delay.
Have you had any progress in your research? Any changes or anything you could update me on.
If you haven't I would recommend you to look at the Heart Rate Application in the SDK to see how Just Works with pairing/bonding works.
What is the peripheral and central in your testing?
Hi, Martin:
Please check the Sniffer data. "Pairing request, pairing response, pairing confirm" are right, but "sent pairing random" is responsed with "confirm value failed", what is the problem, and is it done in SoftDevice?