It looks like the last discussion of Sniffer on Devzone was 2-3 yrs ago.
I’ve ordered the nRF Dongle and will download the Windows-based nRF Sniffer app.
i can run this with WireShark on a Windows VM on my Mac, though I would like a Mac OSX option.
- Any news on that front?
- Any way the Bluetooth hardware built into the MacBook could serve a Mac Sniffer app?
Still looking for a solution here. I think a few others are having the same trouble.
Martin Lesund, what is the next steps?
Can you summarize your versions so I can look at it.
OS Version:Wireshark version:Python version:Pyserial version:
Segger jlink version on PC:Segger jlink version or build date on the jlink emulator on nRF5x-DK:nRF Sniffer version:
PCA board number:
Python 32 bit or 64 bit:
8 -> 64 bit4 -> 32 bit
Can you try the screen option on all the the DKs that you have, I see that a PCA10031 and a PCA10040 were mentioned.
OK. I'll try that tomorrow (Tuesday US Central time) with:- Python 2.7.14- pyserial (3.2.1)- SEGGER J-Link Commander V6.16c (Compiled Jun 16 2017 18:19:39) DLL version V6.16c, compiled Jun 16 2017 18:19:20- WireShark Mac OS Version 2.4.5
In separate sessions, I'll use each device (nRF dongle-PCA10031 and DK-PCA10040) and flash them using the appropriate parameters in JLINKEXE to "erase..." as in the Sniffer 2.1 User Guide.
Then in OSX Terminal, I'll run "screen <port> 460800" and report the results.
Have I got it?
OK, I've run the above with no luck on either board.
I'm wondering where to go next.
I've been through the steps many times.
Are others experiencing this problem?Is so, what is your environment?
I was having issues with Wireshark not showing the extcap interface in it's UI on Mac OS X 10.13.5, even though the files were in the correct location, inside the .app /Applications/Wireshark.app/Contents/MacOS/extcap/
While trying to debug the issue, i decided to run wireshark directly from my shell to see any possible output via /Applications/Wireshark.app/Contents/MacOS/Wireshark
Turns out, this was enough to get nrf_sniffer.py to load, so if you've been having trouble getting it to load, it might be worth running the executable directly from Terminal.app
I suspect it has something to do with environment variables that Wireshark inherits from the shell, but haven't debugged further.
EDIT: Turns out, the best way to fix this so regular app launches work was to change the shebang at the top of nrf_sniffer.py to point directly to your local python2 instance. For me, this was #!/usr/local/bin/python2
I've verified the fix by running through a use case from Mohammad Afeneh's Bluetooth LE eBook for using the sniffer with Wireshark. All looks good.
WireShark "sees" the nrf_sniffer on start-up, and the subsequent steps in Mohamad's tutorial, and in the nRF_Sniffer_User_Guide_v2.1.pdf work as expected.
Now I have the WireShark learning curve... and am thankful to get on to it.
Thanks to those that helped, particularly Richard and David Edwin in this thread!
The fix is a bit of a hack, it seems, and I'll look forward to staying in touch on how to standardize the setup - either by explicit documentation of this work-around in the nRF_Sniffer_User_Guide_v2.X.pdf, or in a update that allows "latest versions" default installation options for required software.