• State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 25 subscribers
  • Views 306 views
  • Users 0 members are here
Attachments (7) Download All
Nordic Case Info
  • Case ID: 282258
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

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

user4223

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

Parents
  • 0

    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

  • 0 in reply to user77782

    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

  • 0 in reply to user4223

    Hi, 

    Are you using DK or custom board? Do you have DK to test with for nRF52832DK;   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

  • 0 in reply to user77782

    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

Reply Children
No Data
Related
Terms of service