Wireshark 2.4.3 cannot detect PCA10031 COM port interface

RE: Wireshark 2.4.3 cannot detect PCA10031 COM port interface

dcollier8 — Thu, 25 Jan 2018 16:21:26 GMT

I could not even see the interface toolbar or the sniffer in it. Per suggestion from Mango, this was because I did not execute nrf_sniffer.bat correctly. So I solved this as follows, and the problem is solved:

Copy nrf_sniffer.bat and nrf_sniffer.py, and the folder SnifferAPI to this folder: C:\Program Files\Wireshark\extcap

Then I reran this command from cmd.exe window:

C:\Program Files\Wireshark\extcap>nrf_sniffer.bat --extcap-interfaces extcap {version=2.0.0}{display=nRF Sniffer}{help=www.nordicsemi.com/.../P roducts/Bluetooth-low-energy/nRF-Sniffer#Downloads} control {number=0}{type=selector}{display=Device}{tooltip=Device list} control {number=1}{type=string}{display=Passkey / OOB key}{tooltip=6 digit tempo rary key or 16 byte Out-of-band (OOB) key in hexadecimal starting with '0x', big endian format. If the entered key is shorter than 16 bytes, it will be zero-pad ded in front'}{validation=\b^(([0-9]{6})|(0x[0-9a-fA-F]{1,32}))$\b} control {number=2}{type=string}{display=Adv Hop}{default=37,38,39}{tooltip=Adver tising channel hop sequence. Change the order in which the siffer switches adver tising channels. Valid channels are 37, 38 and 39 separated by comma.}{validatio n=^\s*((37|38|39)\s*,\s*){0,2}(37|38|39){1}\s*$}{required=true} control {number=3}{type=button}{role=help}{display=Help}{tooltip=Access user gui de (launches browser)} control {number=4}{type=button}{role=restore}{display=Defaults}{tooltip=Resets t he user interface and clears the log file} control {number=5}{type=button}{role=logger}{display=Log}{tooltip=Log per interf ace} value {control=0}{value= }{display=All advertising devices}{default=true}

The problem was then solved, and I can see the interface toolbar with the sniffer shown, which I then selected. However, the interface was then not added to the interfaces list to select for capture, what else needs to be done ?

I am using Wireshark latest 2.4.4 version. Windows7 32 bit. Device Manager shows Com port: Jlink CDC UART Port (Com19). Having other USB connections or unplugging them did not make any difference. All other software versions installed from the sniffer user guide are matched correctly, although I installed pyserial using install command: "python setup.py install", since I could not get the pip command to be installed or work (HELP: anyone know how to install pip ?

pyserial installation log, (does this look successful ?):

C:\1code\pyserial-master>pip install pyserial 'pip' is not recognized as an internal or external command, operable program or batch file.

C:\1code\pyserial-master>python setup.py install running install install_dir c:\Python27\Lib\site-packages
running bdist_egg running egg_info creating pyserial.egg-info writing pyserial.egg-info\PKG-INFO writing top-level names to pyserial.egg-info\top_level.txt writing dependency_links to pyserial.egg-info\dependency_links.txt writing manifest file 'pyserial.egg-info\SOURCES.txt' reading manifest file 'pyserial.egg-info\SOURCES.txt' reading manifest template 'MANIFEST.in' writing manifest file 'pyserial.egg-info\SOURCES.txt' installing library code to build\bdist.win32\egg running install_lib running build_py creating build creating build\lib creating build\lib\serial copying serial\rfc2217.py -> build\lib\serial copying serial\rs485.py -> build\lib\serial copying serial\serialcli.py -> build\lib\serial copying serial\serialjava.py -> build\lib\serial copying serial\serialposix.py -> build\lib\serial copying serial\serialutil.py -> build\lib\serial copying serial\serialwin32.py -> build\lib\serial copying serial\win32.py -> build\lib\serial copying serial_init.py -> build\lib\serial creating build\lib\serial\tools copying serial\tools\hexlify_codec.py -> build\lib\serial\tools copying serial\tools\list_ports.py -> build\lib\serial\tools copying serial\tools\list_ports_common.py -> build\lib\serial\tools copying serial\tools\list_ports_linux.py -> build\lib\serial\tools copying serial\tools\list_ports_osx.py -> build\lib\serial\tools copying serial\tools\list_ports_posix.py -> build\lib\serial\tools copying serial\tools\list_ports_windows.py -> build\lib\serial\tools copying serial\tools\miniterm.py -> build\lib\serial\tools copying serial\tools_init.py -> build\lib\serial\tools creating build\lib\serial\urlhandler copying serial\urlhandler\protocol_alt.py -> build\lib\serial\urlhandler copying serial\urlhandler\protocol_hwgrep.py -> build\lib\serial\urlhandler copying serial\urlhandler\protocol_loop.py -> build\lib\serial\urlhandler copying serial\urlhandler\protocol_rfc2217.py -> build\lib\serial\urlhandler copying serial\urlhandler\protocol_socket.py -> build\lib\serial\urlhandler copying serial\urlhandler\protocol_spy.py -> build\lib\serial\urlhandler copying serial\urlhandler_init.py -> build\lib\serial\urlhandler creating build\lib\serial\threaded copying serial\threaded_init.py -> build\lib\serial\threaded creating build\bdist.win32 creating build\bdist.win32\egg creating build\bdist.win32\egg\serial copying build\lib\serial\rfc2217.py -> build\bdist.win32\egg\serial copying build\lib\serial\rs485.py -> build\bdist.win32\egg\serial copying build\lib\serial\serialcli.py -> build\bdist.win32\egg\serial copying build\lib\serial\serialjava.py -> build\bdist.win32\egg\serial copying build\lib\serial\serialposix.py -> build\bdist.win32\egg\serial copying build\lib\serial\serialutil.py -> build\bdist.win32\egg\serial copying build\lib\serial\serialwin32.py -> build\bdist.win32\egg\serial creating build\bdist.win32\egg\serial\threaded copying build\lib\serial\threaded_init_.py -> build\bdist.win32\egg\serial\th readed creating build\bdist.win32\egg\serial\tools copying build\lib\serial\tools\hexlify_codec.py -> build\bdist.win32\egg\serial
tools copying build\lib\serial\tools\list_ports.py -> build\bdist.win32\egg\serial\too ls copying build\lib\serial\tools\list_ports_common.py -> build\bdist.win32\egg\ser ial\tools copying build\lib\serial\tools\list_ports_linux.py -> build\bdist.win32\egg\seri al\tools copying build\lib\serial\tools\list_ports_osx.py -> build\bdist.win32\egg\serial \tools copying build\lib\serial\tools\list_ports_posix.py -> build\bdist.win32\egg\seri al\tools copying build\lib\serial\tools\list_ports_windows.py -> build\bdist.win32\egg\se rial\tools copying build\lib\serial\tools\miniterm.py -> build\bdist.win32\egg\serial\tools

copying build\lib\serial\tools_init_.py -> build\bdist.win32\egg\serial\tools

creating build\bdist.win32\egg\serial\urlhandler copying build\lib\serial\urlhandler\protocol_alt.py -> build\bdist.win32\egg\ser ial\urlhandler copying build\lib\serial\urlhandler\protocol_hwgrep.py -> build\bdist.win32\egg
serial\urlhandler copying build\lib\serial\urlhandler\protocol_loop.py -> build\bdist.win32\egg\se rial\urlhandler copying build\lib\serial\urlhandler\protocol_rfc2217.py -> build\bdist.win32\egg \serial\urlhandler copying build\lib\serial\urlhandler\protocol_socket.py -> build\bdist.win32\egg
serial\urlhandler copying build\lib\serial\urlhandler\protocol_spy.py -> build\bdist.win32\egg\ser ial\urlhandler copying build\lib\serial\urlhandler_init.py -> build\bdist.win32\egg\serial
urlhandler copying build\lib\serial\win32.py -> build\bdist.win32\egg\serial copying build\lib\serial_init.py -> build\bdist.win32\egg\serial byte-compiling build\bdist.win32\egg\serial\rfc2217.py to rfc2217.pyc byte-compiling build\bdist.win32\egg\serial\rs485.py to rs485.pyc byte-compiling build\bdist.win32\egg\serial\serialcli.py to serialcli.pyc byte-compiling build\bdist.win32\egg\serial\serialjava.py to serialjava.pyc byte-compiling build\bdist.win32\egg\serial\serialposix.py to serialposix.pyc byte-compiling build\bdist.win32\egg\serial\serialutil.py to serialutil.pyc byte-compiling build\bdist.win32\egg\serial\serialwin32.py to serialwin32.pyc byte-compiling build\bdist.win32\egg\serial\threaded_init_.py to init.pyc

byte-compiling build\bdist.win32\egg\serial\tools\hexlify_codec.py to hexlify_co dec.pyc byte-compiling build\bdist.win32\egg\serial\tools\list_ports.py to list_ports.py c byte-compiling build\bdist.win32\egg\serial\tools\list_ports_common.py to list_p orts_common.pyc byte-compiling build\bdist.win32\egg\serial\tools\list_ports_linux.py to list_po rts_linux.pyc byte-compiling build\bdist.win32\egg\serial\tools\list_ports_osx.py to list_port s_osx.pyc byte-compiling build\bdist.win32\egg\serial\tools\list_ports_posix.py to list_po rts_posix.pyc byte-compiling build\bdist.win32\egg\serial\tools\list_ports_windows.py to list_ ports_windows.pyc byte-compiling build\bdist.win32\egg\serial\tools\miniterm.py to miniterm.pyc byte-compiling build\bdist.win32\egg\serial\tools_init.py to init.pyc byte-compiling build\bdist.win32\egg\serial\urlhandler\protocol_alt.py to protoc ol_alt.pyc byte-compiling build\bdist.win32\egg\serial\urlhandler\protocol_hwgrep.py to pro tocol_hwgrep.pyc byte-compiling build\bdist.win32\egg\serial\urlhandler\protocol_loop.py to proto col_loop.pyc byte-compiling build\bdist.win32\egg\serial\urlhandler\protocol_rfc2217.py to pr otocol_rfc2217.pyc byte-compiling build\bdist.win32\egg\serial\urlhandler\protocol_socket.py to pro tocol_socket.pyc byte-compiling build\bdist.win32\egg\serial\urlhandler\protocol_spy.py to protoc ol_spy.pyc byte-compiling build\bdist.win32\egg\serial\urlhandler_init.py to init.p yc byte-compiling build\bdist.win32\egg\serial\win32.py to win32.pyc byte-compiling build\bdist.win32\egg\serial_init_.py to init.pyc creating build\bdist.win32\egg\EGG-INFO installing scripts to build\bdist.win32\egg\EGG-INFO\scripts running install_scripts running build_scripts creating build\scripts-2.7 copying and adjusting serial\tools\miniterm.py -> build\scripts-2.7 creating build\bdist.win32\egg\EGG-INFO\scripts copying build\scripts-2.7\miniterm.py -> build\bdist.win32\egg\EGG-INFO\scripts copying pyserial.egg-info\PKG-INFO -> build\bdist.win32\egg\EGG-INFO copying pyserial.egg-info\SOURCES.txt -> build\bdist.win32\egg\EGG-INFO copying pyserial.egg-info\dependency_links.txt -> build\bdist.win32\egg\EGG-INFO

copying pyserial.egg-info\top_level.txt -> build\bdist.win32\egg\EGG-INFO zip_safe flag not set; analyzing archive contents... creating dist creating 'dist\pyserial-3.4-py2.7.egg' and adding 'build\bdist.win32\egg' to it removing 'build\bdist.win32\egg' (and everything under it) Processing pyserial-3.4-py2.7.egg creating c:\python27\lib\site-packages\pyserial-3.4-py2.7.egg Extracting pyserial-3.4-py2.7.egg to c:\python27\lib\site-packages Adding pyserial 3.4 to easy-install.pth file error: c:\python27\lib\site-packages\easy-install.pth: Permission denied

C:\1code\pyserial-master>python setup.py install running install install_dir c:\Python27\Lib\site-packages
running bdist_egg running egg_info writing pyserial.egg-info\PKG-INFO writing top-level names to pyserial.egg-info\top_level.txt writing dependency_links to pyserial.egg-info\dependency_links.txt reading manifest file 'pyserial.egg-info\SOURCES.txt' reading manifest template 'MANIFEST.in' writing manifest file 'pyserial.egg-info\SOURCES.txt' installing library code to build\bdist.win32\egg running install_lib running build_py creating build\bdist.win32\egg creating build\bdist.win32\egg\serial copying build\lib\serial\rfc2217.py -> build\bdist.win32\egg\serial copying build\lib\serial\rs485.py -> build\bdist.win32\egg\serial copying build\lib\serial\serialcli.py -> build\bdist.win32\egg\serial copying build\lib\serial\serialjava.py -> build\bdist.win32\egg\serial copying build\lib\serial\serialposix.py -> build\bdist.win32\egg\serial copying build\lib\serial\serialutil.py -> build\bdist.win32\egg\serial copying build\lib\serial\serialwin32.py -> build\bdist.win32\egg\serial creating build\bdist.win32\egg\serial\threaded copying build\lib\serial\threaded_init_.py -> build\bdist.win32\egg\serial\th readed creating build\bdist.win32\egg\serial\tools copying build\lib\serial\tools\hexlify_codec.py -> build\bdist.win32\egg\serial
tools copying build\lib\serial\tools\list_ports.py -> build\bdist.win32\egg\serial\too ls copying build\lib\serial\tools\list_ports_common.py -> build\bdist.win32\egg\ser ial\tools copying build\lib\serial\tools\list_ports_linux.py -> build\bdist.win32\egg\seri al\tools copying build\lib\serial\tools\list_ports_osx.py -> build\bdist.win32\egg\serial \tools copying build\lib\serial\tools\list_ports_posix.py -> build\bdist.win32\egg\seri al\tools copying build\lib\serial\tools\list_ports_windows.py -> build\bdist.win32\egg\se rial\tools copying build\lib\serial\tools\miniterm.py -> build\bdist.win32\egg\serial\tools

copying build\lib\serial\tools_init_.py -> build\bdist.win32\egg\serial\tools

byte-compiling build\bdist.win32\egg\serial\tools\hexlify_codec.py to hexlify_co dec.pyc byte-compiling build\bdist.win32\egg\serial\tools\list_ports.py to list_ports.py c byte-compiling build\bdist.win32\egg\serial\tools\list_ports_common.py to list_p orts_common.pyc byte-compiling build\bdist.win32\egg\serial\tools\list_ports_linux.py to list_po rts_linux.pyc byte-compiling build\bdist.win32\egg\serial\tools\list_ports_osx.py to list_port s_osx.pyc byte-compiling build\bdist.win32\egg\serial\tools\list_ports_posix.py to list_po rts_posix.pyc byte-compiling build\bdist.win32\egg\serial\tools\list_ports_windows.py to list_ ports_windows.pyc byte-compiling build\bdist.win32\egg\serial\tools\miniterm.py to miniterm.pyc byte-compiling build\bdist.win32\egg\serial\tools_init.py to init.pyc byte-compiling build\bdist.win32\egg\serial\urlhandler\protocol_alt.py to protoc ol_alt.pyc byte-compiling build\bdist.win32\egg\serial\urlhandler\protocol_hwgrep.py to pro tocol_hwgrep.pyc byte-compiling build\bdist.win32\egg\serial\urlhandler\protocol_loop.py to proto col_loop.pyc byte-compiling build\bdist.win32\egg\serial\urlhandler\protocol_rfc2217.py to pr otocol_rfc2217.pyc byte-compiling build\bdist.win32\egg\serial\urlhandler\protocol_socket.py to pro tocol_socket.pyc byte-compiling build\bdist.win32\egg\serial\urlhandler\protocol_spy.py to protoc ol_spy.pyc byte-compiling build\bdist.win32\egg\serial\urlhandler_init.py to init.p yc byte-compiling build\bdist.win32\egg\serial\win32.py to win32.pyc byte-compiling build\bdist.win32\egg\serial_init_.py to init.pyc creating build\bdist.win32\egg\EGG-INFO installing scripts to build\bdist.win32\egg\EGG-INFO\scripts running install_scripts running build_scripts creating build\bdist.win32\egg\EGG-INFO\scripts copying build\scripts-2.7\miniterm.py -> build\bdist.win32\egg\EGG-INFO\scripts copying pyserial.egg-info\PKG-INFO -> build\bdist.win32\egg\EGG-INFO copying pyserial.egg-info\SOURCES.txt -> build\bdist.win32\egg\EGG-INFO copying pyserial.egg-info\dependency_links.txt -> build\bdist.win32\egg\EGG-INFO

copying pyserial.egg-info\top_level.txt -> build\bdist.win32\egg\EGG-INFO zip_safe flag not set; analyzing archive contents... creating 'dist\pyserial-3.4-py2.7.egg' and adding 'build\bdist.win32\egg' to it removing 'build\bdist.win32\egg' (and everything under it) Processing pyserial-3.4-py2.7.egg removing 'c:\python27\lib\site-packages\pyserial-3.4-py2.7.egg' (and everything under it) creating c:\python27\lib\site-packages\pyserial-3.4-py2.7.egg Extracting pyserial-3.4-py2.7.egg to c:\python27\lib\site-packages Adding pyserial 3.4 to easy-install.pth file Installing miniterm.py script to c:\Python27\Scripts

Installed c:\python27\lib\site-packages\pyserial-3.4-py2.7.egg Processing dependencies for pyserial==3.4 Finished processing dependencies for pyserial==3.4

I found how to install pip here: pip.pypa.io/.../

result log: C:\1code\pyserial-master>python get-pip.py install c:\Python27\lib\site-packages\setuptools\command\install_scripts.py:3: UserWarni ng: Module pip was already imported from c:\users\dcollier\appdata\local\temp\tm pzltby6\pip.zip\pip_init.py, but c:\python27\lib\site-packages is being adde d to sys.path from pkg_resources import Distribution, PathMetadata, ensure_directory Collecting install c:\users\dcollier\appdata\local\temp\tmpzltby6\pip.zip\pip_vendor\requests\pack ages\urllib3\util\ssl.py:318: SNIMissingWarning: An HTTPS request has been made , but the SNI (Subject Name Indication) extension to TLS is not available on thi s platform. This may cause the server to present an incorrect TLS certificate, w hich can cause validation failures. You can upgrade to a newer version of Python to solve this. For more information, see urllib3.readthedocs.io/.../late st/security.html#snimissingwarning. c:\users\dcollier\appdata\local\temp\tmpzltby6\pip.zip\pip_vendor\requests\pack ages\urllib3\util\ssl_.py:122: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. You can upgrade to a newer version of Python to solve this. For more information, see urllib3.readthedocs.io/ en/latest/security.html#insecureplatformwarning. Could not find a version that satisfies the requirement install (from versions : ) No matching distribution found for install c:\users\dcollier\appdata\local\temp\tmpzltby6\pip.zip\pip_vendor\requests\pack ages\urllib3\util\ssl_.py:122: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. You can upgrade to a newer version of Python to solve this. For more information, see urllib3.readthedocs.io/ en/latest/security.html#insecureplatformwarning. You are using pip version 0.8.2, however version 9.0.1 is available. You should consider upgrading via the 'python -m pip install --upgrade pip' comm and.

still cannot run pip:

C:\1code\pyserial-master>pip install pyserial 'pip' is not recognized as an internal or external command, operable program or batch file.

Question: how to run "pip" commands ? Answer: run from scripts subfolder under the python folder, eg. C:\Python27\Scripts

I finally solved why the sniffer Com19 interface was not listed in the interfaces !

It was because the sniffer was not erased and programmed correctly !

here is how I followed the sniffer guide page 5 figure2, note used quotes around the hex file location for programming the sniffer:

C:\Program Files\SEGGER\JLink_V616c>JLink.exe SEGGER J-Link Commander V6.16c (Compiled Jun 16 2017 18:15:26) DLL version V6.16c, compiled Jun 16 2017 18:14:49

Connecting to J-Link via USB...O.K. Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jun 9 2017 14:57:23 Hardware version: V1.00 S/N: 680894940 VTref = 3.300V

Type "connect" to establish a target connection, '?' for help J-Link>erase Target connection not established yet but required for command. Please specify device / core. : NRF52832_XXAA Type '?' for selection dialog Device>NRF51422_XXAA Please specify target interface: J) JTAG (Default) S) SWD TIF>s Specify target interface speed [kHz]. : 4000 kHz Speed>1000 Device "NRF51422_XXAA" selected.

Connecting to target via SWD Found SW-DP with ID 0x0BB11477 Scanning APs, stopping at first AHB-AP found. AP[0] IDR: 0x04770021 (AHB-AP) AHB-AP ROM: 0xF0000000 (Base addr. of first ROM table) CPUID reg: 0x410CC200. Implementer code: 0x41 (ARM) Found Cortex-M0 r0p0, Little endian. FPUnit: 4 code (BP) slots and 0 literal slots CoreSight components: ROMTbl[0] @ F0000000 ROMTbl[0][0]: E00FF000, CID: B105100D, PID: 000BB471 ROM Table ROMTbl[1] @ E00FF000 ROMTbl[1][0]: E000E000, CID: B105E00D, PID: 000BB008 SCS ROMTbl[1][1]: E0001000, CID: B105E00D, PID: 000BB00A DWT ROMTbl[1][2]: E0002000, CID: B105E00D, PID: 000BB00B FPB ROMTbl[0][1]: F0002000, CID: B105900D, PID: 000BB9A3 ??? Cortex-M0 identified. Erasing device (nRF51422_xxAA)... J-Link: Flash download: Total time needed: 5.428s (Prepare: 0.045s, Compare: 0.0 00s, Erase: 5.376s, Program: 0.000s, Verify: 0.000s, Restore: 0.006s) Erasing done. J-Link>loadfile "C:\Program Files\Wireshark\extcap\nrf_sniffer_2.0.0-beta-1_5129 6aa\hex\sniffer_pca10028_51296aa.hex" Downloading file [C:\Program Files\Wireshark\extcap\nrf_sniffer_2.0.0-beta-1_512 96aa\hex\sniffer_pca10028_51296aa.hex]... J-Link: Flash download: Flash programming performed for 1 range (14336 bytes) J-Link: Flash download: Total time needed: 0.390s (Prepare: 0.078s, Compare: 0.0 07s, Erase: 0.000s, Program: 0.259s, Verify: 0.000s, Restore: 0.045s) O.K. J-Link>r Reset delay: 0 ms Reset type NORMAL: Resets core & peripherals via SYSRESETREQ & VECTRESET bit. Setting AIRCR.SYSRESETREQ J-Link>g J-Link>

then toggled interface toolbar sniffer enable, interface appeared !

RE: Wireshark 2.4.3 cannot detect PCA10031 COM port interface

MANGO — Fri, 19 Jan 2018 01:22:56 GMT

Hello, tjp3. I haven't configured something specific to see the COMx port interface.

Can you check whether you are using the below versions?

Wireshark 2.4.2 or above
J-Link 6.16c (you need to up/downgrade if the version is different)
Python 2.7.x
Pyserial

Lastly, unzip \nrf_sniffer.bat and other files in C:\Program Files\Wireshark\extcap\ before running the nrf_sniffer.bat --extcap-interfaces, please.

Although you have configured this and face the problem, can you create a new question thread, please?

-Regards, MANGO

RE: Wireshark 2.4.3 cannot detect PCA10031 COM port interface

tjp3 — Thu, 18 Jan 2018 13:11:46 GMT

Hi I am facing similar problem. Can you explain what correct configuration have you done for rf_sniffer.bat --extcap-interfaces?

RE: Wireshark 2.4.3 cannot detect PCA10031 COM port interface

MANGO — Wed, 17 Jan 2018 14:03:49 GMT

Hi, David. Yes, now Wireshark 2 detects COMx ports after nrf_sniffer.bat --extcap-interfaces with correct configurations.

-Regards, MANGO

RE: Wireshark 2.4.3 cannot detect PCA10031 COM port interface

David Edwin — Wed, 17 Jan 2018 13:48:55 GMT

@MANGO is this fixed for you ?

RE: Wireshark 2.4.3 cannot detect PCA10031 COM port interface

Petter Myhre — Tue, 16 Jan 2018 15:09:13 GMT

Please add a new question, and link to this one if relevant.

RE: Wireshark 2.4.3 cannot detect PCA10031 COM port interface

2rp — Tue, 16 Jan 2018 14:41:46 GMT

Cannot get this to work properly with nRF52 DK running the sniffer_pca10040_51296aa.hex included with nRF Sniffer version 2 (beta) on 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?

RE: Wireshark 2.4.3 cannot detect PCA10031 COM port interface

MANGO — Wed, 10 Jan 2018 16:18:39 GMT

Sorry to hear that, Bjarke. I sometimes cannot see COM ports from Wireshark, too.

I observed that if your PCA10040 sniffs packets, LED2 will blink rapidly.

This is my assumption; if you execute Wireshark 2 while PCA10040 is capturing packets, most of the time, Wireshark fails to find the COM port.

This might sound funny, but can you turn all your Bluetooth devices so that your PCA10040 cannot capture packets?

Now connect your PCA10040 to your computer. If your PCA10040 is not capturing packets, LED2 will not blink.

After checking this, turn on Wireshark 2 and you might see COM x port.

This is quite cumbersome, but give it a try, please.

By the way, I posted a question that summarizes a problem similar to yours.

If you keep an eye on it, maybe it will help you, too.

-BR

RE: Wireshark 2.4.3 cannot detect PCA10031 COM port interface

Bjarke — Wed, 10 Jan 2018 14:56:27 GMT

Hi Mango,

I do have the interface toolbar, but not the interface COM port...it is just blank. BR

RE: Wireshark 2.4.3 cannot detect PCA10031 COM port interface

Petter Myhre — Wed, 10 Jan 2018 14:21:33 GMT

I will relay to the developers. Thank you for the feedback.

RE: Wireshark 2.4.3 cannot detect PCA10031 COM port interface

MANGO — Wed, 10 Jan 2018 12:33:55 GMT

Hi, Petter. Well, that line created a concern for me.

Since other plugins like USBPcapCMD existed inside that file, I thought I had to create an extra directory.

There could be other plugins that use the same file name like the SnifferAPI and I didn't want those to be mixed.

That's why I unzipped as C:\Program Files\Wireshark\extcap\nrf_sniffer_2.0.0-beta-1_51296aa\extcap\nrf_sniffer.bat.

Eventually, my guess was wrong. However, looks like other users might have thought like I did and asked similar questions / the guide's improvements.

Due to this reason, can the devteam elaborate on that instruction? Thanks for your time.

-Warm Regards, MANGO

RE: Wireshark 2.4.3 cannot detect PCA10031 COM port interface

Petter Myhre — Wed, 10 Jan 2018 11:10:40 GMT

Yes, it can be. This is still in beta.

The user guide says

Unzip the ZIP's extcap content to the Wireshark Extcap path found in "About Wireshark” (shown
here as C:\Program Files\Wireshark\extcap).

Isn't it pretty clear that the content of the extcap folder in the ZIP should be unzipeed to C:\Program Files\Wireshark\extcap

Don't you think?

RE: Wireshark 2.4.3 cannot detect PCA10031 COM port interface

MANGO — Wed, 10 Jan 2018 10:37:24 GMT

Thanks for your reply, Petter. Then can the user guide be revised later? Looks like other users posting questions that they cannot find the Interface Toolbars in Wireshark 2.

Maybe stating that this Interface Toolbars can be visible after nrf_sniffer.bat is executed successfully.

Lastly, do I have to place nrf_sniffer.bat, nrf_sniffer.py, and SnifferAPI at C:\Program Files\Wireshark\extcap\, not at C:\Program Files\Wireshark\extcap\nrf_sniffer_2.0.0-beta-1_51296aa\extcap?

Let's clear things up. Thanks for your cooperation.

-Regards, MANGO

RE: Wireshark 2.4.3 cannot detect PCA10031 COM port interface

Petter Myhre — Wed, 10 Jan 2018 09:40:42 GMT

No prob :) It is not default no.

RE: Wireshark 2.4.3 cannot detect PCA10031 COM port interface

MANGO — Tue, 09 Jan 2018 16:39:46 GMT

Thanks for sharing your pictures, Petter. I have updated my question to show my side's configuration.

- Is it listed like this? RE: Nope.

In short, I placed the file at C:\Program Files\Wireshark\extcap\nrf_sniffer_2.0.0-beta-1_51296aa\extcap\nrf_sniffer.bat.

Whereas your picture says that the path is C:\Program Files\Wireshark\extcap\nrf_sniffer.bat, so I changed my file path, too.

As you see my uploaded pictures, did I had to place nrf_sniffer.bat, nrf_sniffer.py, and SnifferAPI at C:\Program Files\Wireshark\extcap\, not at C:\Program Files\Wireshark\extcap\nrf_sniffer_2.0.0-beta-1_51296aa\extcap?

The user guide confuses me where to place the files, so I wish you to clear this up.

Was the Interface Toolbars appear after I run nrf_sniffer.bat? So this is not a Wireshark default menu, is it?

-Regards, MANGO

RE: Wireshark 2.4.3 cannot detect PCA10031 COM port interface

MANGO — Tue, 09 Jan 2018 16:14:35 GMT

Hi, Bjarke.

Did you have any progress on this issue?

Kind of. I will add some pictures to my original question. Hope that helps.

Also, please check Petter Myhre's comments, too.

-Regards, MANGO

RE: Wireshark 2.4.3 cannot detect PCA10031 COM port interface

Bjarke — Tue, 09 Jan 2018 11:08:06 GMT

Hi,

I have the exact same issue, and I am on PC10040. Did you have any progress on this issue?

BR bjarke

RE: Wireshark 2.4.3 cannot detect PCA10031 COM port interface

Petter Myhre — Mon, 08 Jan 2018 15:45:15 GMT

Is it listed like this?

Interface Toolbars:

RE: Wireshark 2.4.3 cannot detect PCA10031 COM port interface

MANGO — Sun, 07 Jan 2018 17:35:14 GMT

Hi, Petter.

Is nrf_sniffer.bat listed in Wireshark->Help->About Wireshark->Plugins ?

RE: It is listed in C:\Program Files\Wireshark\extcap\nrf_sniffer_2.0.0-beta-1_51296aa\extcap\nrf_sniffer.bat

This is the correct list, isn't it?

you should use NRF51422_XXAC

Thanks for pointing that out. However, my Wireshark still does not show the COMx interface after retrying the whole steps.

Since your side is working, did you clicked the Interface Toolbars from Wireshark?

From my side, and another thread says this, I cannot see that menu.

Referring my previously uploaded image, can you check that interface toolbar one more time, please?

-Best Regards, MANGO

RE: Wireshark 2.4.3 cannot detect PCA10031 COM port interface

Ignacio Lopez — Sat, 06 Jan 2018 21:41:32 GMT

Couple of notes to improve the user guide 2.0:

· It would be better to specify better which files are required to be copied to extcap

· It could not find where it is explained how to install the pyserial.

stackoverflow.com/.../installing-and-using-pyserial-in-python-3-4-windows-8-1

RE: Wireshark 2.4.3 cannot detect PCA10031 COM port interface

Petter Myhre — Tue, 02 Jan 2018 15:30:05 GMT

I just tested with PCA10031 and Wireshark 2.4.3, seems to be working fine. I just programmed the sniffer hex with nrfjprog, you can try that. I noticed that you were using NRF51422_XXAA while the user guide says you should use NRF51422_XXAC (I'm not sure if that should matter though).

Is nrf_sniffer.bat listed in Wireshark->Help->About Wireshark->Plugins ?

RE: Wireshark 2.4.3 cannot detect PCA10031 COM port interface

MANGO — Fri, 29 Dec 2017 16:24:40 GMT

Hi, David. I just downgraded the J-Link version to 6.16c. However, the result was same that nRF5 Sniffer COMx interface doesn't show up on my Wireshark 2.

As mentioned in my first question 0,

I couldn't find the Interface Toolbars. Would this be the problem? It would be a great help if you can elaborate why I don't have that Interface Toolbars menu.

In Wireshark 2.4.3 (Windows version), in contrast to the Troubleshooting guide, I cannot

“nRF Sniffer on xxxxx” doesn’t show up as one of the interfaces when I open Wireshark.

1. Click View in the Wireshark toolbar. 2. Select Interface Toolbars then click nRF Sniffer.

Also, looks like another user had the same problem, described here.

Can you help me with this interface toolbars? This doesn't show up when I Google it.

-Regards

RE: Wireshark 2.4.3 cannot detect PCA10031 COM port interface

MANGO — Fri, 29 Dec 2017 08:14:19 GMT

Thanks, David Edwin. Do I have to downgrade the Python version, too?

The manual says

C:>python --version

Python 2.7.x

As you see my first screenshot, I have installed Python 2.7.14 on my Windows 10 desktop.

Also, I have uploaded the screenshots after executing

python nrf_sniffer.py --extcap-interfaces

and

nrf_sniffer.bat --extcap-interfaces

Check the 3rd picture for the python execution and the first one for nrf_sniffer.bat output.

Are those messages show any problems?

I tried to downgrade the J-Link firmware, but I was postponing that due to personal reasons.

I will downgrade it now. In the meantime can you check the output messages? Are these messages expected ones?

-Best Regards

RE: Wireshark 2.4.3 cannot detect PCA10031 COM port interface

David Edwin — Wed, 27 Dec 2017 13:59:29 GMT

You need to use jlink 6.16c as listed in the required software section in the nRF Sniffer v2 user guide.
You need to verify all the steps in the user guide v2 in sections 1, 2, 3. Verify that you have the correct python version.
In addition since you are using a later version of segger jlink, you need to downgrade the jlink emulator firmware on the Nordicsemi DK board to 6.16c. Use the troubleshooting section in the user guide to do the downgrade of the jlink emulator firmware.