Failing to Pair with "Bluetooth Low Energy" Desktop (V3.0.0)

[Torsten Robitzki]

Good Morning and a Happy New Year,

I try to test an application, using the nRF Connect for Desktop (on a Mac). While trying to pair with an application that supports LESC with "Display Yes/No" IO capabilities, I see that my application and nRF Connect exchange Pairing Request and Pairing Response, but that nRF Connect does not start the public key exchange. Instead I see some error messages in the logs of nRF Connect:

    `Error when calling replySecParams: Error: Error occured when replying sec params. Errorcode: Unknown value (0x8005)`

As pairing works with other clients (but is not as comfortable as nRF Connect), I consider this to be a bug in nRF Connect. In case, you are interested in investigating this, I will try to provide everything to reproduce this issue (see attached files).

best regards,

Torsten

2022-01-07T07_02_32.114Z-log.txt

Fullscreen nrfconnect-system-report-2022-01-07T07-31-51.507Z.txt Download

# nRFConnect System Report - 2022-01-07T07-31-51.507Z

- System:     Apple Inc. MacBookPro13,3
- BIOS:       Apple Inc. 447.60.3.0.0
- CPU:        1 x Intel® Core™ i7-6700HQ 2.6 GHz 8 cores (4 physical)
- Memory:     2.1 GB free of 16 GB total
- Filesystem: /dev/disk1s5s1 (APFS) 931.5 GB 9.1% used

- OS:         macOS (11.6.2) darwin x64

- Versions
    - kernel: 20.6.0
    - git: 2.24.3
    - node: 14.16.0
    - python: 2.7.16
    - python3: 3.8.2

- Connected devices:
    - /dev/tty.usbmodem0006830046021: 000683004602 PCA10056
    - /dev/tty.usbmodem0006836461851: 000683646185 PCA10056
    - /dev/tty.usbmodem0006832609581: 000683260958 PCA10056

- Current device:
    - name:          undefined
    - serialNumber:  000683004602
    - cores:         undefined
    - website:       undefined

gpio.hexble_pair.pcapng

[Amanda Hsieh]

Hi, 

Do you see any error on device log? Please provide the device log and sniffer log which captures before connection. 

Are you developing with nRF5 SDK or NCS? Which version? 

What is the DK to run the image?

Could you test with Heart Rate Application? Do you see the same issue?

Regards,
Amanda

[Torsten Robitzki]

Hi Amanda,

please see the already attached `2022-01-07T07_02_32.114Z-log.txt`I guess that's what you name a device log. The sniffer log is in the already attached `ble_pair.pcapng` (can be opened, using Wireshark).

I'm using a third party BLE library for nRF52. But, as I wrote, I suspect the issue to be in the nRF Connect Desktop application, not in the firmware. (Because of the missing Public Key Exchange [which has to be initiated by the Controller, not the Peripheral] and because the provided binary [gpio.hex] works against other generic GATT clients)

If you provide me a binary, I would be happy to test your binary against nRF Connect Desktop.

best regards,

Torsten

[Amanda Hsieh]

Hi, 

Are you using DK or custom board? Do you have DK to test with 17.1_ble_app_hrs_pca10040_s132.hex for nRF52832DK;  17.1_ble_app_hrs_pca10056_s140.hex for nRF52840DK?

I cannot reproduce with those image on DKs pairing with the nRF Connect for Desktop/BLE app. Is it possible to test on your side? 

Is it possible to capture sniffer log before the application connect to the nRF Connect for Desktop/BLE app? I need the sniffer log starting before the device connects to app. Thanks.  

-Amanda

[Torsten Robitzki]

Hello Amanda,

I'm so sorry. It turned out, that I've (again) stumbled over the Mac / Segger MSD problem (https://wiki.segger.com/J-Link_OB#Problem_description). After disabling MSD on the eval board connected to the nRF Connect for Desktop, everything works as expected.

Thank you very much for your Time.

Best regards,

Torsten