I'm using MacOS Catalina 10.15.6 and nRF52840-DK (2019.9) for the Sniffer. My PCB is running BLE on nRF52840. The hex file used for the sniffer is sniffer_nrf52840dk_nrf52840_7cc811f.hex (from nrf_sniffer_for_bluetooth_le_3.1.0_7cc811f ).I've downgraded to Wireshark 3.0.7 per some comments from here and here.
When following the instruction from the InfoCenter I got stuck on Step 4, ie I didn't see the Interface. So, I did few other things like setting 'alias python=python3' per this comment. And, ran "/usr/bin/python3 -m pip install --user pyserial" per info from here. And I could finally see the nRF Sniffer Interface
But when I double click on it (while putting the nRF52840-DK sniffer right next to my PCB containing nRF52840 that's actively streaming), I don't see any packets. And, when I click Stop, it gives some error about "Interrupted system call", and then the Wireshark stops responding.
My questions are:1) Is it possible that I need to change some Wireshark settings to be able to sniff the BLE packets? I'm very sure my PCB is streaming packets because my PC Client sees them.2) Is it expected that you cannot stop the streaming? Or, am I doing some wrong setup somewhere perhaps?Thanks,Cecylia
Can you please check the install guide:
And particularly part 3 b) and c).
Does it return an error?
1) Is it possible that I need to change some Wireshark settings to be able to sniff the BLE packets? I'm very sure my PCB is streaming packets because my PC Client sees them.
Not sure. Try to follow the guide from the link and let me know if the behavior differs from the guide.
2) Is it expected that you cannot stop the streaming? Or, am I doing some wrong setup somewhere perhaps?
Here's the output. I have to use "./" before the .sh file name, but it looks OK to me.
You are using a normal nRF52840 DK as the sniffer DK, right?
If you don't plug your custom PCB running the BLE software, but only keep the sniffer DK connected to your computer (try powering it off and on after programming it with the sniffer_nrf52840dk_nrf52840_7cc811f.hex), and then open wireshark. What does it look like after you select the nRF Sniffer (from your first screenshot) but before you hit the "stop button"?
Even though your device is not advertising, you should see a bunch of BLE packets. At least in a typical home environment, if you have a couple of phones in the nearby, some TVs, computers and so on. If you have a phone nearby, you can try to scan using nRF Connect for Android/iOS. You should see that there are some BLE devices nearby, so the nRF Sniffer should be able to see these as well. The reason I ask you to test is just to see that the other device is not messing up the USB interface.
Perhaps you can try to power your custom device from another computer/power supply?
If you are using a USB Hub, try connecting the DK used for the nRF Sniffer directly to your computer (without the USB hub).
Edvin said:You are using a normal nRF52840 DK as the sniffer DK, right?
Edvin said:What does it look like after you select the nRF Sniffer (from your first screenshot) but before you hit the "stop button"?
It's totally empty. See screenshot below.
I'm connecting the nRF52840-DK directly to my MAC and I have nothing else connected to the MAC.I can use this DK on a PC and it works as expected, so I believe the DK has no issue. But I don't always have access to a PC, so I was hoping we can resolve it for MAC.
Can you please try to update the JLink driver from www.segger.com? What version are you currently on?