NRF52840 NRF Connect desktop pairing / bonding issue

RE: NRF52840 NRF Connect desktop pairing / bonding issue

swisst — Fri, 04 Jun 2021 11:20:10 GMT

Thanks a lot

RE: NRF52840 NRF Connect desktop pairing / bonding issue

Einar Thorsrud — Fri, 28 May 2021 13:29:02 GMT

Hi,

The issue here is the IO Capabilities you configure. You set "Display, no keyboard" in the nRF Connect BLE app, which is the same as the glucose application. When both peers support only display, no MITM is possible. You need to set "Keyboard and display" on nRF Connect. Then the combined IO capabilities will allow passkey display on the nRF device and passkey entry on nRF Connect.

RE: NRF52840 NRF Connect desktop pairing / bonding issue

swisst — Thu, 27 May 2021 13:51:44 GMT

Hi,

thank you for quick reply and sorry for delay

For now lets focus on pca10056 board only - custom application relies on it so if I get result with glucose application I'll success with custom app

I've downloaded clear glucose example ( diifs were only in line endings ) and rebuild it - same result as above

The only changes I have in SDK are about verbosity with NRF_LOF_INFO in peer manager

devzone.nordicsemi.com/.../peer_5F00_manager_5F00_handler.diff

Screenshot from NRF Connect but did try all option variants

RE: NRF52840 NRF Connect desktop pairing / bonding issue

Einar Thorsrud — Wed, 26 May 2021 12:47:00 GMT

Hi,

Can you confirm that you reproduce this with an unmodified GLS example from SDK 17.0.2 as well as your custom app? If so, we need to look at your configuration in nRF Connect BLE. If you click on the gear icon, is "Auto reply security requests" checked or not? What is the configuration in "Security Parameters..."? When you initiate bonding, what parameters do you select? Screenshots would be good so that I can see that I match the exact same configuration on my side.

If this is not reproducible with the unmodified GLS app, then we need to look at your custom app and see if we see something there.

RE: NRF52840 NRF Connect desktop pairing / bonding issue

swisst — Tue, 25 May 2021 13:01:55 GMT

Sorry for delayed reply

NRF Connect is recent one v3.6.1

devzone.nordicsemi.com/.../NRF_5F00_Connect_5F00_log_5F00_autoresponse.log

RE: NRF52840 NRF Connect desktop pairing / bonding issue

Einar Thorsrud — Thu, 20 May 2021 16:38:44 GMT

Hi,

I am not able to reproduce this. Using the unmodified GLS example from SDK 17.0.2 and nRF Connect 3.6.1 with BLE app 2.5.1 I connect and immediately pair with MITM.

nRF side log:

<info> app_timer: RTC: initialized.
<info> app: advdata size: 31
<info> app: srdata size: 0
<info> app: Glucose example started.
<info> app: Fast advertising
<info> app: Connected
<info> app: Passkey: 671717
<info> app: BLE_GAP_EVT_LESC_DHKEY_REQUEST
<info> nrf_ble_lesc: Calling sd_ble_gap_lesc_dhkey_reply on conn_handle: 0
<info> peer_manager_handler: Connection secured: role: Peripheral, conn_handle: 0, procedure: Pairing
<info> app: Link secured. Role: 1. conn_handle: 0, Procedure: 2
<info> app: BLE_GAP_EVT_AUTH_STATUS: status=0x0 bond=0x0 lv4: 1 kdist_own:0x0 kdist_peer:0x0

nRF Connect log:

devzone.nordicsemi.com/.../2021_2D00_05_2D00_20T16_5F00_28_5F00_50.764Z_2D00_log.txt

Which version of the nRF Connect BLE app are you using? Could there be other factors here? Can you upload the log from nRF Connect?

RE: NRF52840 NRF Connect desktop pairing / bonding issue

swisst — Thu, 20 May 2021 11:56:34 GMT

Tested with gls example without any modifications - result is the same as described above

NRF connect for desktop + NRF52840-DK ( pca10056 ) - see attached log

devzone.nordicsemi.com/.../gls_5F00_example_5F00_log.log