nRF Sniffer version 2 (beta) not working with nRF52 DK

[2rp]

Cannot get nRF Sniffer version 2 (beta) to work properly with nRF52 DK running the sniffer_pca10040_51296aa.hex:

• Windows 7 64-bit
• nRF Sniffer 2.0.0-1.beta
• Wireshark 2.4.3
• Python 2.7.14
• pyserial 3.4
• nRFgo Studio 1.21.2
• Segger J-Link 6.16c

The Sniffer interface is available in Wireshark but only sometimes the nRF Sniffer COM6 (in my case) shows up but no traffic is ever captured.

For example, I plug in the nRF52 DK and is enumerated as JLink CDC UART Port (COM6) in Device Manager. First time running C:\Program Files\Wireshark\extcap\nrf_sniffer.bat --extcap-interfaces shows “interface {value=COM6}{display=nRF Sniffer COM6}” as expected. But the interface disappears when running the command again right after. On the nRF52 DK LED2 is flashing when my peripheral is advertising so I assume the application is running ok. I have downgraded the hardware from J-Link 6.20b to 6.16c without any improvements.

This explains why the interface is not always showing up in the Sniffer in Wireshark but what is causing this?

[Joel]

I'm having the same issue with a nearly identical environment (using Wireshshark 2.4.4 currently)

[shibshab]

I think there are known issues with the Segger UART and pyserial in general. Try opening a serial terminal (e.g. putty) to the board and see if data is being streamed. I think this is described in the user guide for the sniffer. Another thing to try is to run the "exec invalidatefw" command again to reflash the segger.

[David Edwin]

Please do not use nRFgo studio or run it when the sniffer is running, it interferes with the COM ports. Just use the jlink to flash the fw, since you installed nrfgo studio you have got a different jlink version also installed so double check that you are at 6.16c on the jlink emu on the DK.

[2rp]

nRFgo Studio was only used for erasing the nRF52 DK, nothing else, and is not running otherwise. Segger J-Link 6.16c was installed because a more recent version was installed with nRFgo Studio; the firmware was downgraded as described in troubleshooting section in the user guide, and I have checked (again) the firmware: C:\program files (x86)\segger\jlink_v616c\jlinkconfig.exe reports identical host and emulator firmware dates.

[Jakub J.]

I ran across similar problem. I was using Windows 10 and Wireshark v2.4.4. Sniffer connection was highly unstable, sometimes I wasn't able to connect, sometimes no traffic recorded. Moreover it didn't list any available BT device for the connection.

Tried Wireshark v2.4.2 - works like a charm.  I guess even though the user guide states in Required Software section "Wireshark v2.4.2 or later available from" it has to be version 2.4.2, not newer.