• State Verified Answer
  • Replies 5 replies
  • Subscribers 87 subscribers
  • Views 808 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 261370
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

BLE Sniffer stops when a connection established

jawadk

Hi,

I used this user guide: https://infocenter.nordicsemi.com/pdf/nRF_Sniffer_UG_v2.2.pdf.

I am using the nRF52840 DK for the sniffer, and managed to connect it and see the advertising data for the peripheral (nRF52840) BLE.

When I power on the central board (another nRF52840) I stop receiving sniffer data from the peripheral board, and not sure if the connection is really established.

When I don't power on the sniffer the connection between the two nRF52840 boards done as expected.

Without the sniffer I don't face any problems, when I sniff the peripheral board with the central turned off it works and I got the sniffer data for the advertising data from the peripheral, but I still facing a problem when I turn on the central board.

Please help me to   fix this issue, I need to see the data passed between my peripheral and the central board.

Best Regards

JK

Parents
  • 0

    Hi

    That depends on how you do encryption in your application. If you use a passkey to do pairing, it should be printed to the terminal over the DKs COM port, and you can add it in the sniffer and central device to pair while the sniffer is "in".

    If you don't use a passkey, I guess you're pairing using OOB. If so, you will need the OOB key. To get it, you will need to output the OOB key from the application somehow, for instance by printing it to UART using NRF_LOG_INFO(). The OOB key is requested in the BLE_GAP_EVT_AUTH_KEY_REQUEST event, and you provide the key using the sd_ble_gap_auth_key_reply() function. So I would suggest printing it right after or before the sd_ble_gap_auth_key_reply() function is called in this case. Either should be fine.

    Best regards,

    Simon

Reply
  • 0

    Hi

    That depends on how you do encryption in your application. If you use a passkey to do pairing, it should be printed to the terminal over the DKs COM port, and you can add it in the sniffer and central device to pair while the sniffer is "in".

    If you don't use a passkey, I guess you're pairing using OOB. If so, you will need the OOB key. To get it, you will need to output the OOB key from the application somehow, for instance by printing it to UART using NRF_LOG_INFO(). The OOB key is requested in the BLE_GAP_EVT_AUTH_KEY_REQUEST event, and you provide the key using the sd_ble_gap_auth_key_reply() function. So I would suggest printing it right after or before the sd_ble_gap_auth_key_reply() function is called in this case. Either should be fine.

    Best regards,

    Simon

Children
No Data
Related
Terms of service