Wireshark doesn't see nrf51 dongle sniffer

[Han Vertegaal]

The nRF sniffer is not listed in the Wireshark interface list.

Software versions: Windows 10 Pro 64 bit, Python 3.8, Wireshark 3.2.3, nRF Connect 3.3.3, Sniffer 3.0.0.

I programmed the dongle with hex image: sniffer_pca10031_129d2b3.hex. The toolbar shows up in Wireshark, but not the sniffer interface:

I tried the nrf_sniffer_ble.bat --extcap-interfaces command, and that seems to work fine.

Is there anything else I can try?

[Han Vertegaal]

In the mean time I installed nRF Connect BLE, and saw that it couldn't open the COM port on which the dongle operates. Because other software also has problems opening COM ports over USB, I conclude it is not so much an nRF software problem as a problem with my PC. So I re-installed everything on another PC and now it works fine, Wireshark and everything. Problem solved.

However, I can still program the dongle using nRF Connect, and I assume it uses the same USB attached COM port. What is the difference between nRF Connect Programmer and nRF Connect BLE? One of them works fine, while the other does not.

[Amanda Hsieh]

Hi, 

If you can program the nRF51 dongle with nRF Connect Programmer, you suppose to could use  nRF51 dongle with nRF Connect BLE.

Did you also press the reset button on nRF51 dongle before connecting with nRF Connect BLE  as using nRF Connect Programmer? 

If it still cannot work after pressing the reset button then connecting, could you provide the log of nRF Connect BLE?

 

-Amanda H.

[Han Vertegaal]

I tried resetting the dongle, but that brings no change.

The BLE tool log is as follows:

2020-05-18T10:16:55.684Z INFO Application data folder: C:\Users\han\AppData\Roaming\nrfconnect\pc-nrfconnect-ble
2020-05-18T10:16:55.757Z DEBUG App pc-nrfconnect-ble v2.3.2 official
2020-05-18T10:16:55.757Z DEBUG App path: C:\Users\han\.nrfconnect-apps\node_modules\pc-nrfconnect-ble
2020-05-18T10:16:55.757Z DEBUG nRFConnect 3.3.3 is supported by the app (^3.2.0)
2020-05-18T10:16:55.757Z DEBUG nRFConnect path: C:\Users\han\AppData\Local\Programs\nrfconnect\resources\app.asar
2020-05-18T10:16:55.757Z DEBUG HomeDir: C:\Users\han
2020-05-18T10:16:55.757Z DEBUG TmpDir: C:\Users\han\AppData\Local\Temp
2020-05-18T10:17:04.417Z INFO Validating connectivity firmware for device with serial number 000680450780...
2020-05-18T10:17:04.863Z ERROR Error while setting up device 000680450780: Opening COM3: Access denied
2020-05-18T10:17:04.866Z INFO Device closed.

The programmer log id as follows:

2020-05-18T10:19:57.973Z INFO Application data folder: C:\Users\han\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer
2020-05-18T10:19:58.053Z DEBUG App pc-nrfconnect-programmer v1.4.2 official
2020-05-18T10:19:58.054Z DEBUG App path: C:\Users\han\.nrfconnect-apps\node_modules\pc-nrfconnect-programmer
2020-05-18T10:19:58.054Z DEBUG nRFConnect 3.3.3 is supported by the app (^3.3.0)
2020-05-18T10:19:58.054Z DEBUG nRFConnect path: C:\Users\han\AppData\Local\Programs\nrfconnect\resources\app.asar
2020-05-18T10:19:58.054Z DEBUG HomeDir: C:\Users\han
2020-05-18T10:19:58.054Z DEBUG TmpDir: C:\Users\han\AppData\Local\Temp
2020-05-18T10:19:58.068Z INFO Using nrfjprog library 10.8.0, pc-nrfjprog-js 1.7.2
2020-05-18T10:20:01.836Z INFO Using nrfjprog to communicate with target
2020-05-18T10:20:02.228Z INFO Using J-Link Software version 6.62
2020-05-18T10:20:02.817Z INFO Segger serial:  680450780
2020-05-18T10:20:02.817Z INFO Segger speed:  2000  kHz
2020-05-18T10:20:02.817Z INFO Segger version:  J-Link OB-SAM3U128-V2-NordicSemi compiled Mar 17 2020 14:43:00
2020-05-18T10:20:02.818Z INFO Core probed: 680450780.
2020-05-18T10:20:02.818Z INFO Core RAM: 32KiB.
2020-05-18T10:20:02.818Z INFO Core ROM: 256KiB in pages of 1KiB.
2020-05-18T10:20:02.938Z INFO Model: NRF51xxx_xxAC_REV3.
2020-05-18T10:20:03.288Z INFO Core0: Reading device non-volatile memory. This may take a few seconds.
2020-05-18T10:20:03.310Z INFO Core0: UICR has been read. Click read button to read full non-volatile memory.

[Amanda Hsieh]

Hi Han, 

Please try Vidar's suggestion in this post. 

-Amanda H.

[Han Vertegaal]

I erased the dongle using the programmer. Then started BLE, but I got the exact same log (error opening COM3). Next, I reprogrammed the device so I can user it as a sniffer again on my other PC. Reprogramming worked fine. Next, I started BLE again, and it prompted me that the dongle needed to be reprogrammed. Clicking Ok in the dialog resulted in the following log:

2020-05-18T11:43:49.575Z INFO Application data folder: C:\Users\han\AppData\Roaming\nrfconnect\pc-nrfconnect-ble
2020-05-18T11:43:49.648Z DEBUG App pc-nrfconnect-ble v2.3.2 official
2020-05-18T11:43:49.648Z DEBUG App path: C:\Users\han\.nrfconnect-apps\node_modules\pc-nrfconnect-ble
2020-05-18T11:43:49.648Z DEBUG nRFConnect 3.3.3 is supported by the app (^3.2.0)
2020-05-18T11:43:49.648Z DEBUG nRFConnect path: C:\Users\han\AppData\Local\Programs\nrfconnect\resources\app.asar
2020-05-18T11:43:49.648Z DEBUG HomeDir: C:\Users\han
2020-05-18T11:43:49.649Z DEBUG TmpDir: C:\Users\han\AppData\Local\Temp
2020-05-18T11:44:00.109Z INFO Validating connectivity firmware for device with serial number 000680450780...
2020-05-18T11:44:12.565Z INFO Connectivity firmware is valid.
2020-05-18T11:44:12.565Z INFO Getting information from J-Link debugger...
2020-05-18T11:44:13.251Z INFO Found device type: nRF51. J-Link firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Mar 17 2020 14:43:00.
2020-05-18T11:44:13.251Z INFO Connectivity firmware version: 4.1.1. SoftDevice API version: 2. Baud rate: 1000000.
2020-05-18T11:44:13.251Z INFO Opening adapter connected to COM3
2020-05-18T11:44:13.970Z ERROR Received status with code 5 IO_RESOURCES_UNAVAILABLE, message: 'Error setting up serial port COM3. open: Access is denied.: Access is denied.'
2020-05-18T11:44:13.971Z DEBUG State change: STATE_START -> STATE_FAILED
2020-05-18T11:44:16.996Z ERROR Error occured when opening port. Errorcode: Unknown value (0x8029)

Looking at the memory map using the programmer, it seem that the BLE app did indeed program a new image, but subsequently failed to connect.

Apparently, if the BLE app communicates through J-Link (as does the programmer) everything works, but when it accesses the COM3 port directly (?) it fails.

[Amanda Hsieh]

Hi Han, 

Could you try other USB ports and do the Vidar's suggestion again?

-Amanda H. 

[Han Vertegaal]

Sorry for the delay. I tried, but the problem remains.

Do you have an idea about the difference between the BLE app and the programmer where it comes to communicating with the device. Could it be that the programmer bypasses the COM port emulator and talks directly to the USB?