Hi, DevZone, thanks for help : )
I'm try to porting DK Board's Ble Bonding function to Target Board.
TARGET : nRF52840
SD: s140_nRF52_v7.0.1
SDK: nRF5_v16.0.0
1st_question <- this is my first question links
2nd_question <- this is my second question links
The First cause was a mutex error that occurred while using RTOS, and
The second cause has not yet been clearly identified, but it seems that we have found a possible cause,
so we request an update and new help.
i'm looking this site also, check procedure JustWork method
in this procedure, sd_ble_gap_lesc_dhkey_reply(p_dhkey) works well,
(DK board debug log) (my board debug log)
<info> app: BLE_GAP_EVT_LESC_DHKEY_REQUEST <info> nrf_ble_lesc: && compute_and_give_dhkey <info> nrf_ble_lesc: Calling sd_ble_gap_lesc_dhkey_reply on conn_handle: 0
handler_ble_evt BLE_GAP_EVT_LESC_DHKEY_REQUEST && compute_and_give_dhkey Calling sd_ble_gap_lesc_dhkey_reply on conn_handle: 0
and after that procedure,
(DK board debug log) - DK board call same as procedure (my board debug log)
<info> peer_manager_smd: @@ BLE_GAP_EVT_CONN_SEC_UPDATE in <info> peer_manager_smd: && conn_sec_update_process <info> peer_manager_smd: && pairing <info> peer_manager_smd: @@ smd_ble_evt_handler out ... ... .. <info> peer_manager_smd: @@ BLE_GAP_EVT_AUTH_STATUS in <info> peer_manager_smd: && auth_status_process <info> peer_manager_smd: && auth_status_failure_process <info> peer_manager_smd: && pairing_success_evt_send <info> peer_manager_smd: && evt_send <info> peer_manager_handler: Connection secured: role: Peripheral, conn_handle: 0, procedure: Bonding
handler_ble_evt BLE_GAP_EVT_LESC_DHKEY_REQUEST && compute_and_give_dhkey Calling sd_ble_gap_lesc_dhkey_reply on conn_handle: 0 BLE event: 0x19. @@ ble_conn_state.c ble_evt_handler in @@ ble_conn_state.c BLE_GAP_EVT_AUTH_STATUS in @@ ble_conn_state.c ble_evt_handler out @@ im_ble_evt_handler in @@ evt_id != BLE_GAP_EVT_CONNECTED @@ sm_ble_evt_handler in @@ smd_ble_evt_handler in @@ BLE_GAP_EVT_AUTH_STATUS in && auth_status_process && auth_status_failure_process && link_secure_failure && sec_procedure && pairing && encryption_failure && bonding && conn_sec_failure && evt_send
board skip check BLE_GAP_EVT_CONN_SEC_UPDATE procedure.
I wonder where the function that sets the event flag to "BLE_GAP_EVT_CONN_SEC_UPDATE" is called.
Are there any possible causes of the problem?
and please let me know if there is another simple way to check "SMP_Pairing_DHKey_Check" in the previous process other than sniffing.
Thanks,
Best Regards
#Ble #Ble_Bonding #Bonding