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?

[Edvin]

Hello,

the sniffer exclusively outputs counts rather than continuing to output broadcast packets.

What do you mean by this? What kind of counting are you seeing? 

What sort of packets are transmitted using CODED_PHY? Advertisements, or are you changing over to coded phy after entering a connection?

Best regards,

Edvin

[zadme]

i set this, scan coded phy

flow to thousands of packets and no longer refresh, this phenomenon occurs every time

[zadme]

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

[Edvin]

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

[zadme]

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

[zadme]

hello, Edvin, are there any new progress

thinks

[Edvin]

Hello,

Sorry for the delay.

I will test tomorrow. But just in case, can you please try to download the sniffer firmware from our source? 

https://www.nordicsemi.com/Products/Development-tools/nRF-Sniffer-for-Bluetooth-LE/Download?lang=en#infotabs

Then we know we are using the same FW.

Also, please try to use the .hex file intended for the dongle, not the DK. And finally, what do you mean by:

zadme said:

I used the SWD burning interface to burn PCA10059

What interface is this? Do you mean the nRF Connect for Desktop -> Programming app?

BR,
Edvin

[zadme]

Hello,

I confirmed that I downloaded the ble sniffer firmware from this link, using a third-party burning tool, and the interfaces are swdio and swdclk on the dongle

Best regards

[PaKa]

The image delivered from Nordic has a hard requirement that the original bootloader is in the Dongle. If you have used SWD interface then it's likely that the bootloader is gone, then the code won't run. Search the forum on how to get the bootloader re-instated, program the sniffer code through the USB interface as described in the user guide and test again.

[zadme]

Received your suggestion, thank you for answering

I will retest the sniffing of the coded phy after correctly burning it

thanks

[zadme]

I have correctly burned open_bootloader_usb_mbr_pca10059_debug.hex and sniffer_nrf52840dongle_nrf52840_4.1.1.hex. Now my usb dongle (pca10059) can be normally recognized by wireshark. Next, let's go back to the initial question. After checking wireshark coded phy option, wireshark will no longer output new packets after sniffing hundreds or thousands of ad packets

thanks

[zadme]

I add that when the sniffing is normal, the LD1 of dongle flickers irregularly. When wireshark stops refreshing, the LD1 no longer flickers