Im working on a windows 11 Pro (OS Build 22000.1219) with a NRF52 development kit which has a NRF52832 chip set. The board is PCA10040 3.0.0. The device does not communicate with wireshark and I think its related to this issue https://devzone.nordicsemi.com/f/nordic-q-a/92334/unable-to-start-capture-on-nrf-sniffer/388027
I can use the development kit with the Bluetooth Low Energy App that comes with nrf connect. Ive followed the steps to install the sniffer firmware sniffer_nrf52dk_nrf52832_4.1.1.hex and validated that it bat file works when placed in the extcap folder in wireshark. Ive tried wireshark version 4.0.1, 3.6.9 and 3.6.7 but the same issue appears.
Ive traced back the error to how wireshark starts the python script. See below
15-Nov-2022 18:09:45 (+0000) INFO: --------------------------------------------------------
15-Nov-2022 18:09:45 (+0000) INFO: Software version: 4.1.1
15-Nov-2022 18:09:45 (+0000) INFO: Started PID 28452
15-Nov-2022 18:09:45 (+0000) INFO: Namespace(capture=False, extcap_interfaces=True, extcap_interface=None, extcap_dlts=False, extcap_config=False, extcap_capture_filter=None, fifo=None, extcap_control_in=None, extcap_control_out=None, extcap_version='4.0', device='', baudrate=None, only_advertising=False, only_legacy_advertising=False, scan_follow_rsp=False, scan_follow_aux=False, coded=False)
15-Nov-2022 18:09:45 (+0000) INFO: Opening serial port COM11
15-Nov-2022 18:09:45 (+0000) INFO: --------------------------------------------------------
15-Nov-2022 18:09:45 (+0000) INFO: Software version: 4.1.1
15-Nov-2022 18:09:45 (+0000) INFO: Started PID 23452
15-Nov-2022 18:09:45 (+0000) INFO: Namespace(capture=False, extcap_interfaces=True, extcap_interface=None, extcap_dlts=False, extcap_config=False, extcap_capture_filter=None, fifo=None, extcap_control_in=None, extcap_control_out=None, extcap_version='4.0', device='', baudrate=None, only_advertising=False, only_legacy_advertising=False, scan_follow_rsp=False, scan_follow_aux=False, coded=False)
15-Nov-2022 18:09:45 (+0000) INFO: Opening serial port COM11
15-Nov-2022 18:09:45 (+0000) ERROR: Error opening UART could not open port 'COM11': PermissionError(13, 'Access is denied.', None, 5)
Traceback (most recent call last):
File "C:\Users\xx\AppData\Roaming\Wireshark\extcap\SnifferAPI\Packet.py", line 74, in __init__
self.uart = UART.Uart(portnum, baudrate)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\xx\AppData\Roaming\Wireshark\extcap\SnifferAPI\UART.py", line 124, in __init__
self.ser = serial.Serial(
^^^^^^^^^^^^^^
File "C:\Users\xx\AppData\Local\Programs\Python\Python311\Lib\site-packages\serial\serialwin32.py", line 33, in __init__
super(Serial, self).__init__(*args, **kwargs)
File "C:\Users\xx\AppData\Local\Programs\Python\Python311\Lib\site-packages\serial\serialutil.py", line 244, in __init__
self.open()
File "C:\Users\xx\AppData\Local\Programs\Python\Python311\Lib\site-packages\serial\serialwin32.py", line 64, in open
raise SerialException("could not open port {!r}: {!r}".format(self.portstr, ctypes.WinError()))
serial.serialutil.SerialException: could not open port 'COM11': PermissionError(13, 'Access is denied.', None, 5)
15-Nov-2022 18:09:45 (+0000) INFO: Opening serial port None
15-Nov-2022 18:09:45 (+0000) INFO: Opening serial port COM11
This is the bat test response
./nrf_sniffer_ble.bat --extcap-interfaces
extcap {version=4.1.1}{display=nRF Sniffer for Bluetooth LE}{help=https://www.nordicsemi.com/Software-and-Tools/Development-Tools/nRF-Sniffer-for-Bluetooth-LE}
control {number=0}{type=selector}{display=Device}{tooltip=Device list}
control {number=1}{type=selector}{display=Key}{tooltip=}
control {number=2}{type=string}{display=Value}{tooltip=6 digit passkey or 16 or 32 bytes encryption key in hexadecimal starting with '0x', big endian format.If the entered key is shorter than 16 or 32 bytes, it will be zero-padded in front'}{validation=\b^(([0-9]{6})|(0x[0-9a-fA-F]{1,64})|([0-9A-Fa-f]{2}[:-]){5}([0-9A-Fa-f]{2}) (public|random))$\b}
control {number=3}{type=string}{display=Adv Hop}{default=37,38,39}{tooltip=Advertising channel hop sequence. Change the order in which the sniffer switches advertising channels. Valid channels are 37, 38 and 39 separated by comma.}{validation=^\s*((37|38|39)\s*,\s*){0,2}(37|38|39){1}\s*$}{required=true}
control {number=7}{type=button}{display=Clear}{tooltop=Clear or remove device from Device list}
control {number=4}{type=button}{role=help}{display=Help}{tooltip=Access user guide (launches browser)}
control {number=5}{type=button}{role=restore}{display=Defaults}{tooltip=Resets the user interface and clears the log file}
control {number=6}{type=button}{role=logger}{display=Log}{tooltip=Log per interface}
value {control=0}{value= }{display=All advertising devices}{default=true}
value {control=0}{value=[00,00,00,00,00,00,0]}{display=Follow IRK}
value {control=1}{value=0}{display=Legacy Passkey}{default=true}
value {control=1}{value=1}{display=Legacy OOB data}
value {control=1}{value=2}{display=Legacy LTK}
value {control=1}{value=3}{display=SC LTK}
value {control=1}{value=4}{display=SC Private Key}
value {control=1}{value=5}{display=IRK}
value {control=1}{value=6}{display=Add LE address}
value {control=1}{value=7}{display=Follow LE address}
Ive checked to see the com port can be opened outside wireshark using the same python and liibraries and it can be successfully read without erroring out like when when wireshark calls it.
Is there any fix for this? Ive also tried ubuntu, windows 10..
