52840 Dongle，ble sniffer set coded phy failed

RE: 52840 Dongle，ble sniffer set coded phy failed

Hieu — Sun, 19 Jan 2025 10:23:03 GMT

matt.nickels are you referring to how rare/common LE Coded PHY advertising is?

RE: 52840 Dongle，ble sniffer set coded phy failed

matt.nickels — Fri, 17 Jan 2025 21:51:33 GMT

Just want to note that the statement that it is rare might be domain based. In UAS Remote ID world I disagree with that statement.

RE: 52840 Dongle，ble sniffer set coded phy failed

David300m — Fri, 13 Sep 2024 15:32:14 GMT

I have not. If time permits, I plan to update Wireshark on both of my dev platforms, Win11 and Linux. After thinking about it, I believe the problem is the duck-tape (plugin) between the nordic sniffer and Wireshark. Just a guess at this point.

I was investigating slowing the PHY for better range, but the iOS app developer claims they cannot setup the app to perform other than 1Mbps so I have some research to do if I really need this feature.

Have a great weekend.

David

RE: 52840 Dongle，ble sniffer set coded phy failed

zadme — Fri, 13 Sep 2024 12:12:43 GMT

Hello,

have you fixed this problem, or what's the latest progress,

thanks

RE: 52840 Dongle，ble sniffer set coded phy failed

David300m — Thu, 11 Jul 2024 21:38:00 GMT

I agree Hieu,

The symptoms experienced were exactly the same as what Zadme reported, with "exception" to the Rust exception. When time permits, I will check the Wireshark domain for support.

Thanks again. David

RE: 52840 Dongle，ble sniffer set coded phy failed

Hieu — Thu, 11 Jul 2024 21:00:35 GMT

Hi David,

OK. Those Rust exceptions sound like a different issue, so should you need the tool in the future, please feel free to open a new DevZone thread about it.

Hieu

RE: 52840 Dongle，ble sniffer set coded phy failed

David300m — Thu, 11 Jul 2024 18:37:42 GMT

Hi Hieu,

I tried the path that Joakim suggested and I still get the same issue. I noticed that wireshark produces some exceptions with reference to Rust. At this point I will work without wireshark.

Thank you for your response.

David

RE: 52840 Dongle，ble sniffer set coded phy failed

Hieu — Thu, 11 Jul 2024 12:19:31 GMT

Hi David,

[quote user="David300m"]

My setup: Sniffer rel 4.1.1 and wireshark 4.3.0 on Linux

For my application this is not a show stopper but a nice to have for development and verification. Hopefully this can be fixed in the future but I understand there are priorities on tools like these.

[/quote]

Do you have issue sniffing Coded PHY packets? Have you tried installing the sniffer following the link in Joakim's reply?

[quote user="David300m"]For clarification, you noted that advertising on LE Coded PHY is rare. Can you please elaborate? I would think that this would be useful for many applications that need to reach far for a connection.[/quote]

This is likely referring to Joakim's personal observation. On DevZone, I could also observe that most questions on Advertising are about regular legacy advertising.

It is true that it would be useful for many applications that want to have range.

Hieu

RE: 52840 Dongle，ble sniffer set coded phy failed

David300m — Sat, 06 Jul 2024 15:22:33 GMT

My setup: Sniffer rel 4.1.1 and wireshark 4.3.0 on Linux

For my application this is not a show stopper but a nice to have for development and verification. Hopefully this can be fixed in the future but I understand there are priorities on tools like these.

For clarification, you noted that advertising on LE Coded PHY is rare. Can you please elaborate? I would think that this would be useful for many applications that need to reach far for a connection.

In my application, it could improve the functionality given the expected dynamic use-cases. For now, we plan to advertise w a 1M PHY and monitor the PER and adjust the PHY to improve the connection.

Much appreciated for your response.

David

RE: 52840 Dongle，ble sniffer set coded phy failed

Joakim Andersson — Sat, 06 Jul 2024 09:43:10 GMT

Follow up . It appears that the new extcap does not handle LE Coded PHY Packets. So use the old way to install the Python based extcap to get it working: https://infocenter.nordicsemi.com/topic/ug_sniffer_ble/UG/sniffer_ble/installing_sniffer_plugin.html

Note that advertising on LE Coded PHY is extremely rare and unless you have put up your own advertiser you probably want see anything.

I got it working on newest sniffer release, 4.1.1, using wireshark 4.2.2

RE: 52840 Dongle，ble sniffer set coded phy failed

David300m — Fri, 05 Jul 2024 16:23:35 GMT

Hi there, did you get this issue resolved?

Thanks,

David

RE: 52840 Dongle，ble sniffer set coded phy failed

Edvin — Fri, 05 Jul 2024 10:14:25 GMT

I was able to reproduce it without the "only ..." options being checked. Both on the Dongle and the DK.

RE: 52840 Dongle，ble sniffer set coded phy failed

Joakim Andersson — Fri, 05 Jul 2024 09:23:28 GMT

zadme You have selected "only legacy advertising packets" and "Scan and follow devices on LE Coded PHY". The intersection of these two options should be no packets. You need to unselect "only legacy advertising packets".

I suggest you uncheck both of the "Only .. " options.

Edvin Yes, the DK firmware does support USB. Just change your USB cable to the nRF USB after flashing the board.

RE: 52840 Dongle，ble sniffer set coded phy failed

Edvin — Tue, 02 Jul 2024 13:39:43 GMT

Hello,

I can't see to get it working with the nRF52840 DK either. So unfortunately, I don't see any way of sniffing Coded PHY packets at this point in time.

Best regards,

Edvin

RE: 52840 Dongle，ble sniffer set coded phy failed

zadme — Tue, 02 Jul 2024 12:58:15 GMT

Thank you for your support. When will this software bug be solved

Best regards

RE: 52840 Dongle，ble sniffer set coded phy failed

Edvin — Fri, 28 Jun 2024 19:45:34 GMT

Hello,

Yes. I have reproduced it. And it seems like a bug. I have reported it to the developers of this tool. I didn't notice it before. In fact, I wasn't even aware you could sniff Coded Phy packets (Well, it doesn't work now, so basically, you can't).

[quote user="zadme"]I add that when the sniffing is normal, the LD1 of dongle flickers irregularly. When wireshark stops refreshing, the LD1 no longer flickers[/quote]

I see that too. I believe it ususally toggles one time for every packet it picks up, so it suggests that the issue is in the nRF FW, and not with wireshark.

Let me see what the developers say.

Best regards,

Edvin

RE: 52840 Dongle，ble sniffer set coded phy failed

zadme — Fri, 28 Jun 2024 05:08:55 GMT

Hello, excuse me, the project is urgent, please help test the coded phy, thank you

RE: 52840 Dongle，ble sniffer set coded phy failed

zadme — Thu, 27 Jun 2024 12:23:24 GMT

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

RE: 52840 Dongle，ble sniffer set coded phy failed

zadme — Thu, 27 Jun 2024 11:59:58 GMT

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

RE: 52840 Dongle，ble sniffer set coded phy failed

zadme — Thu, 27 Jun 2024 11:20:50 GMT

Received your suggestion, thank you for answering

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

thanks

RE: 52840 Dongle，ble sniffer set coded phy failed

PaKa — Thu, 27 Jun 2024 10:32:05 GMT

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.

RE: 52840 Dongle，ble sniffer set coded phy failed

zadme — Thu, 27 Jun 2024 10:26:12 GMT

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

RE: 52840 Dongle，ble sniffer set coded phy failed

Edvin — Wed, 26 Jun 2024 22:02:54 GMT

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:

[quote user="zadme"]I used the SWD burning interface to burn PCA10059[/quote]

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

BR,
Edvin

RE: 52840 Dongle，ble sniffer set coded phy failed

zadme — Wed, 26 Jun 2024 12:38:45 GMT

hello, Edvin, are there any new progress

thinks

RE: 52840 Dongle，ble sniffer set coded phy failed

zadme — Tue, 25 Jun 2024 14:26:37 GMT

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