RE: Ble Bonding - error of unknown cause

Empe — Thu, 12 Aug 2021 02:13:28 GMT

Hello,

thanks for reply and sorry for late update.

[quote userid="4240" url="~/f/nordic-q-a/77969/ble-bonding---error-of-unknown-cause/322827#322827"]Have you tried to debug the app to see if the program maybe gets stuck in one of your threads?[/quote]

now, i'm solve stuck problem, i don't now true reason but maybe thread's size problem

links <- this is my new post

try to insert debug code and looks like find some error point

when your not busy, please check it once

thanks for help

best regards

RE: Ble Bonding - error of unknown cause

Vidar Berg — Mon, 02 Aug 2021 10:16:50 GMT

[quote user="Empe"]situation are same both get BLE event fleg : 0x19 "Authentication procedure completed with status"[/quote]

What's the status code? PM_EVT_CONN_SEC_SUCCEEDED indicate that the bonding procedure completed succesfully, so maybe it's something else that causes your program to hang. Have you tried to debug the app to see if the program maybe gets stuck in one of your threads?

Best regards,

Vidar

RE: Ble Bonding - error of unknown cause

Empe — Thu, 29 Jul 2021 06:39:41 GMT

Hello, Vidar

thanks for answer

[quote userid="4240" url="~/f/nordic-q-a/77969/ble-bonding---error-of-unknown-cause/322260#322260"]if you disable LESC support (i.e. set SEC_PARAM_LESC = 0)?[/quote]

yes, i try Enable and disable both result are same

here is full log (i was turn on Error, Warning, Info, Debug Message ) - using LESC 0

Generating ECC key pair
Erase bonds!
Event PM_EVT_PEERS_DELETE_SUCCEEDED
All peers deleted.

BLE event: 0x10.
Requesting to update ATT MTU to 247 bytes on connection 0x0.
Updating data length to 251 on connection 0x0.
Connected

BLE event: 0x1c.
BLE event: 0x3a.
ATT MTU updated to 247 bytes on connection 0x0 (response).
Data len is set to 0xF4(244)
ATT MTU exchange completed. central 0xf7 peripheral 0xf7
BLE event: 0x24.
Data length updated to 123 on connection 0x0.
max_rx_octets: 123
max_tx_octets: 123
max_rx_time: 1096
max_tx_time: 1096
ATT MTU exchange completed. central 0xf7 peripheral 0xf7
BLE event: 0x12.
BLE event: 0x23.
Peer on connection 0x0 requested a data length of 123 bytes.
Updating data length to 123 on connection 0x0.
BLE event: 0x24.
Data length updated to 123 on connection 0x0.
max_rx_octets: 123
max_tx_octets: 123
max_rx_time: 1096
max_tx_time: 1096
ATT MTU exchange completed. central 0xf7 peripheral 0xf7
BLE event: 0x12.
BLE event: 0x13.
Event PM_EVT_CONN_SEC_START
Connection security procedure started: role: Peripheral, conn_handle: 0, procedure: Bonding
Event PM_EVT_CONN_SEC_PARAMS_REQ
Security parameter request
BLE event: 0x12.
BLE event: 0x1a.
BLE event: 0x19.
Event PM_EVT_CONN_SEC_SUCCEEDED

here is full log ( also turn on Error, Warning, Info, Debug Message ) - using LESC 1

Generating ECC key pair
Erase bonds!
Event PM_EVT_PEERS_DELETE_SUCCEEDED
All peers deleted.
BLE event: 0x10.
Requesting to update ATT MTU to 247 bytes on connection 0x0.
Updating data length to 251 on connection 0x0.
Connected

BLE event: 0x1c.
BLE event: 0x3a.
ATT MTU updated to 247 bytes on connection 0x0 (response).
Data len is set to 0xF4(244)
ATT MTU exchange completed. central 0xf7 peripheral 0xf7
BLE event: 0x24.
Data length updated to 123 on connection 0x0.
max_rx_octets: 123
max_tx_octets: 123
max_rx_time: 1096
max_tx_time: 1096
ATT MTU exchange completed. central 0xf7 peripheral 0xf7
BLE event: 0x12.
BLE event: 0x23.
Peer on connection 0x0 requested a data length of 123 bytes.
Updating data length to 123 on connection 0x0.
BLE event: 0x24.
Data length updated to 123 on connection 0x0.
max_rx_octets: 123
max_tx_octets: 123
max_rx_time: 1096
max_tx_time: 1096
ATT MTU exchange completed. central 0xf7 peripheral 0xf7
BLE event: 0x12.
BLE event: 0x13.
Event PM_EVT_CONN_SEC_START
Connection security procedure started: role: Peripheral, conn_handle: 0, procedure: Bonding
Event PM_EVT_CONN_SEC_PARAMS_REQ
Security parameter request
BLE event: 0x18.
BLE_GAP_EVT_LESC_DHKEY_REQUEST
BLE_GAP_EVT_LESC_DHKEY_REQUEST
Calling sd_ble_gap_lesc_dhkey_reply on conn_handle: 0
BLE event: 0x12.
BLE event: 0x12.
BLE event: 0x1a.
BLE event: 0x19.

situation are same both get BLE event fleg : 0x19 "Authentication procedure completed with status"

and send PM_EVT_CONN_SEC_SUCCEEDED and stuck in somewhere

after that log, device go to reset mode via watch-dog

( when i block watch-dog, stuck in somewhere and no-respons)

[quote userid="4240" url="~/f/nordic-q-a/77969/ble-bonding---error-of-unknown-cause/322260#322260"]nrf_ble_lesc_request_handler() function[/quote]

this function is run on another thread,

it means using freeRTOS, useing several thread, initialize in main thread and lesc handler is working on ble thread

ble thread's job is only work update app's time and call lesc handler

++ test that run (initialize and lesc handler) as same thread, it's situation result is same

Thanks

Best Regards, Empe

RE: Ble Bonding - error of unknown cause

Vidar Berg — Wed, 28 Jul 2021 13:32:28 GMT

Hello,

Have you tried to see if bonding works ok if you disable LESC support (i.e. set SEC_PARAM_LESC = 0)? Also, are you calling the nrf_ble_lesc_request_handler() function periodically like in the ble_app_hrs example?

Thanks,

Vidar

Edit: Forgot that we do have an example with Freertos+LESC in our nRF5 Thread & Zigbee SDK. Maybe that example could serve as a reference: https://devzone.nordicsemi.com/f/nordic-q-a/74337/use-the-le-secure-connections-in-the-ble_thread_dyn_mtd_coap_cli-example