This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Using nrfsniffer to debug connection loss

I am trying to use nrfsniffer to debug connection related issues.

We have a ble connection between central and peripheral and we are sending status updates to the peripheral fro the central at a rate of about 1 per second.

We have issues with the conenction and connection is regularly dropped and rebuilt. I can run this test walking arounf out side for say an hour and I regularly see the central indicating connection loss and connection being rebuilt.

If I try and trace this with wireshark and nrf52 dk I see all the packets from the first period of connection; but on the subsequent reconnections I only see the connection req/ind from the central; I do not see the complete trace of packets between the central and peripheral.

I am using wireshark 3.4.4 and nrf_sniffer_for_bluetooth_le_3.1.0_7cc811f.

We are seeing large gaps in the status update received by the peripheral and we suspect this is in actuality long periods of BLE not having a valid connection; hence we wish to see complete traces over these connect/disconnect cycles to try and debug the problems.


Or is snrfsniffer and wireshark just really not up to debugging  such problems?


Parents Reply
  • I programmed two nRF52840-DK (pca10056) for devices under test:

    \nRF5_SDK_17.0.2_d674dde\examples\ble_central\ble_app_blinky_c\hex

    \nRF5_SDK_17.0.2_d674dde\examples\ble_peripheral\ble_app_blinky\hex

    For nRF sniffer I used an nRF52-DK (pca10040), and I programmed it with the sniffer_nrf52dk_nrf52832_7cc811f.hex.

    I then started Wireshark and choose the Nordic Blinky device from the drop down box, I were able to successfully follow several connections with the nRF sniffer (I just turned off/on the peripheral since I didn't walk to the microwave):

    The blue section above is the second connection.

    Some information about my setup:

    Best regards,
    Kenneth

Children
Related