• State Suggested Answer
  • Replies 32 replies
  • Answers 1 answer
  • Subscribers 73 subscribers
  • Views 2351 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 328994
Options

52840 Dongle，ble sniffer set coded phy failed

zadme

Hello, when testing the BLE sniffer with an nRF52840 dongle (utilizing the most recent official sniffer firmware), I configured Wireshark to capture the coded PHY. After initiating the sniffing process for several seconds and capturing roughly tens of broadcast packets, Wireshark ceases to update data. Upon conducting lower-level debugging, I discovered that the sniffer exclusively outputs counts rather than continuing to output broadcast packets. Could this be attributed to a misconfiguration or are there alternative explanations?

Parents Reply Children
  • 0 in reply to zadme
    zadme said:
    In my requirements, the device sends out a broadcast that has been encoded phy.

    Can you please give some more details on how this is done? Is it using coded phy as an extended advertisement, in addition to regular 1MBPS PHY advertisements? Or are you only advertising on coded phy?

    BR,
    Edvin

  • 0 in reply to Edvin

    My Bluetooth advertising transmission device has two types of advertisements, 1M phy and coded phy. I use pca10059 (nrf52840 dongle) as a sniffer, and 1M phy can continue to sniff normally. However, once the coded phy is selected as shown in the screenshot above, the sniffer will stop refreshing data after sniffing thousands of advertising packets. The firmware I burned for pca10059 is sniffer_nrf52840dk_nrf52840_4.1.1.hex (which is also my other question, why dongle burned sniffer_nrf52840dongle_nrf52840_4.1.1.hex, The firmware does not work on the contrary, which means that Wireshark cannot scan this ble sniffer

  • 0 in reply to zadme

    I will have to test this tomorrow. Could you possibly send the FW for the advertiser that you are using? Just in case this doesn't reproduce if it doesn't see any actual coded phy advertising packets. 

    zadme said:
    The firmware I burned for pca10059 is sniffer_nrf52840dk_nrf52840_4.1.1.hex (which is also my other question, why dongle burned sniffer_nrf52840dongle_nrf52840_4.1.1.hex, The firmware does not work on the contrary, which means that Wireshark cannot scan this ble sniffer

    Are you using the Nordic nRF52840 dongle, or a 3rd party device? I know you stated pca10059, but I am asking just to be certain. 

    And I have been using the sniffer_nrf52840dongle_nrf52840_4.1.1.hex without any issues (but I have not tested the coded phy option before). 

    The dongle FW should work on both the dongle and DK, as long as you use the peripheral USB port on the DK, but the DK FW shouldn't work on the dongle, unless they changed it to use the USB peripheral on there as well in the latest version. I will need to check that in the office tomorrow. 

    Best regards,

    Edvin

  • 0 in reply to Edvin

    1.  Yes, I am using Nordic's official USB dongle PCA10059

    2. I downloaded the ble sniffer firmware from this website（ nsscprodmedia.blob.core.windows.net/.../nrf_sniffer_for_bluetooth_le_4.1.1.zip ）I used the SWD burning interface to burn PCA10059 hex/sniffer_nrf52840dk_nrf52840_4.1.1.hex， When pca10059 is plugged into the USB interface of the computer, the device manager can recognize the USB serial device (USB CDC device). At this time, opening Wireshark can recognize nRF Sniffer For Bluetooth LE COMxx, and double clicking can sniff the advertisement (1M PHY) sent by my broadcasting device;
    Next, as shown in the screenshot above, I select Scan Coded PHY. After double clicking, I can only smell thousands of ad packets, including ads from my other broadcasting device (Coded PHY). Wireshark will no longer refresh the data

  • 0 in reply to Edvin

    hello, Edvin, are there any new progress

    thinks

Related