RE: nRF Sniffer 2.0 Not Following Device Into Connection

Josh M — Tue, 29 May 2018 17:26:37 GMT

Hello David,

I copied the files from the attachment into my Wireshark extcap folder and gave it a try. I'm still seeing the same behavior as documented in my initial post.

One strange thing I've noticed is that after I select the device I want to follow into connection in Wireshark, and then have the central connect, I keep seeing advertisements from the device on the sniffer. It's like the sniffer keeps sending cached / old messages to Wireshark on repeat. I'm highly confident that these aren't actual advertisements as our peripheral only supports one connection and doesn't advertise after it's connected. I know its connected from monitoring the debug logs of the peripheral and central via UART.

If I stop and restart Wireshark while the connection is still active I no longer see the advertisements on the sniffer, until I break the connection.

-Josh

RE: nRF Sniffer 2.0 Not Following Device Into Connection

David Edwin — Tue, 22 May 2018 13:04:51 GMT

My hypothesis points at the command being sent from the nRF Sniffer plugin in Wireshark is reaching the PCA board over UART. This type of UART issue usually points to a segger jlink issue.

Can you try the attachment in this case for a possible fix, which attempts to work around the segger jlink UART issue.