• State Verified Answer
  • Locked Locked
  • Replies 20 replies
  • Subscribers 64 subscribers
  • Views 22965 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 129019
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

nRF Sniffer support for Wireshark v2.0.3

sidekick

Hi,

My setup:

  • Host: Windows 10, 64 bit
  • CPU: x86_64
  • Wireshark: v2.0.3 nRF
  • sniffer: v1.0.0
  • nRF Dongle: Segger, PCA100000, v2.2.0 (nRF51822QFAA based board)

Followed the Sniffer guide to successfully flash the dongle and start the sniffer application, however packet capturing is not working. Wireshark crashes and I see the message logged on the console that wireshark v2.0.3 is not supported. Is there a plan to add support for latest version of wireshark (v2.0.3) ?

  • 0 in reply to Julien

    @Eric I do not have a dongle now and may try only next week. You used latest automated build and not v2.2.0 this should be OK. Not sure NRF sniffer uses the PATH (I supposed it uses the registry base to get last installed version path). Do not use "w" to start Wireshark, do it manually (but I will confirm this point). You may have a try with v 1.10.x (as "recommended" by Nordic) to see if the sniffer is able to create the pipe. If this doesn't work too, the sniffer may be the problem

  • 0 in reply to Julien

    @Julien I did use the latest automated build. Before that the sniffer was opening wireshark 2.2 with the pipe on its own just fine but it lacked the analyzer so the frames were junk. Does NRF create the pipe immediately? I didn't see it in technet.microsoft.com/.../dd581625.aspx Maybe I can just cat the pipe to a file somehow.

  • 0 in reply to Julien

    @Eric No reason for the automated build not to work if 2.2.0 did. I installed Wireshark-win32-2.3.0-944-g90e30be.exe and it seems to work (pipe exists even if I haven't the dongle) You could try launching wireshark with commandLine C:\Program Files (x86)\Wireshark220custom\Wireshark.exe', '-Y', 'btle', '-k', '-i', '\\.\pipe\wireshark_nordic_ble do not use the -gtk version. You seem to be skilled, try to see log.txt file in with 's' option in NRF sniffer. For me it seems that the pipe is immediatly created at opening of NRFsniffer not on 'w' command. Also as I already said, NRFsniffer automatically uses the latets installed version. You may try to reinstall a 2.3.0 build (I usually install along the 2.2.0 version by changin the install path to C:\PF(x86)\Wireshark_myVersion\ )

  • 0 in reply to Julien

    @julien Any idea on where to start to get Wireshark 2.5 up? I need the BLE5 data. Can't get sniffer to load WS with "w". Tried command line, but pipes are removed and omitting that didn't help.

Related