Using nrfsniffer to debug connection loss

RE: Using nrfsniffer to debug connection loss

OwainIncus — Wed, 31 Mar 2021 13:12:04 GMT

I haave wireshark 3.4.4; loaded latest nrfutils as said and latest segger. Reprogrammed dongle.
The powering peripheral on/off test as you did appears to work OK.

I do not have microwave here in work; will retest tomorrow at home.

RE: Using nrfsniffer to debug connection loss

Kenneth — Thu, 25 Mar 2021 17:03:34 GMT

I programmed two nRF52840-DK (pca10056) for devices under test:

\nRF5_SDK_17.0.2_d674dde\examples\ble_central\ble_app_blinky_c\hex

\nRF5_SDK_17.0.2_d674dde\examples\ble_peripheral\ble_app_blinky\hex

For nRF sniffer I used an nRF52-DK (pca10040), and I programmed it with the sniffer_nrf52dk_nrf52832_7cc811f.hex.

I then started Wireshark and choose the Nordic Blinky device from the drop down box, I were able to successfully follow several connections with the nRF sniffer (I just turned off/on the peripheral since I didn't walk to the microwave):

The blue section above is the second connection.

Some information about my setup:

Best regards,
Kenneth

RE: Using nrfsniffer to debug connection loss

Kenneth — Tue, 23 Mar 2021 18:13:49 GMT

Sorry, haven't had time, it's on the to do list.

Kenneth

RE: Using nrfsniffer to debug connection loss

OwainIncus — Tue, 23 Mar 2021 15:12:15 GMT

Have you tried the microwave test?

RE: Using nrfsniffer to debug connection loss

Kenneth — Tue, 23 Mar 2021 13:32:53 GMT

The command line tools were a bit old, maybe give it an update:
https://www.nordicsemi.com/Software-and-tools/Development-Tools/nRF-Command-Line-Tools/Download

Also, just write a "nrfjprog -p" afterwards, I believe this will update the j-link firmware afterwards (this should at least have an effect for the pca10040, which is the one I am using also for nRF sniffer. I haven't done testing with the pca10059, though I believe support was recently added).

Kenneth

RE: Using nrfsniffer to debug connection loss

OwainIncus — Tue, 23 Mar 2021 09:34:15 GMT

Here details of the two cards/dongles used for these tests....

PCA10040 Sticker:: 1.2.1 2017.48 682534162 PCB: 400150 0256RUBR

PCA10059 Sticker: 1.0.0 2018.22 CC:33:61:0C:BC:84 PCB: 400250 0284RUBR

C:\Users\Owain>nrfjprog --version
nrfjprog version: 9.8.1
JLinkARM.dll version: 6.88a

C:\Users\Owain>

RE: Using nrfsniffer to debug connection loss

Kenneth — Mon, 22 Mar 2021 14:46:09 GMT

I will see if I can get some time to recreate this.

Can you just provide details about the pca10040 you are using for test here? E.g. version printed on the label.

Also type 'nrfjprog --version' in a command line window.

Thanks,
Kenneth

RE: Using nrfsniffer to debug connection loss

OwainIncus — Mon, 22 Mar 2021 09:38:03 GMT

Hi Kenneth,

I have just repeated the microwave test using a new nrf52840 dongle as the sniffer.
Successfully logged until the peripheral was put into the microwave; I see one led flashing green; another solid red.

On removing peripheral from the microwave the red led goes off and the green led is static; and wireshark is not seeing any more packets. I repeated and saw all leds off.devzone.nordicsemi.com/.../possibleSnifferBug.pcapng

I can see my central is connected to the peripheral and working properly.

I would add to this that starting/stopping wireshark does not appear to start the dongle now; static green led; in fact wirshark appears crashed. Restarting wireshark; dongle interface is NOT seen!!! Had to unplug/plug dongle in again to get it seen from wireshark.

This looks like sniffer FW bugs.

Could you please try and reproduce this one?

Regards,
Owain

RE: Using nrfsniffer to debug connection loss

Kenneth — Wed, 17 Mar 2021 10:10:29 GMT

[quote user="owain"]I have sniffer FW on a pca10040 dev card; and normally when its running I see a couple of leds flashing tx and rx? When it stops logging those leds stop as well; they only start flashing if I reset the dev card (sniffer).[/quote]

That may indicate some issues with the board, do you have a second pca10040 you can use for test? What is the marking on the pca10040 you are using? Can you try to connect the board to a different USB hub/port and possible replace the USB cable? Also update for instance segger j-link from:
https://www.nordicsemi.com/Software-and-tools/Development-Tools/nRF-Command-Line-Tools/Download

Kenneth

RE: Using nrfsniffer to debug connection loss

OwainIncus — Tue, 16 Mar 2021 15:24:47 GMT

I just ran another test putting the peripheral into a microwave; not turned on :-)

I see behaviour as in last trace; but as I bring the peripheral out of the microwave; my central reconencts OK, but the sniffer stops logging packets.

I have sniffer FW on a pca10040 dev card; and normally when its running I see a couple of leds flashing tx and rx? When it stops logging those leds stop as well; they only start flashing if I reset the dev card (sniffer).

Has sniffer crashed when my device successfully reconnects?

I blew hex onto sniffer by copying the hex to the segger mass storage device; I did not flash it via ICE. Is my problem with the sniffer itself?

Many thanks for analysis above; we are not using whitelists/blacklists. It looks like that test trace you see did catch my issue; sporadic disconnects for a substantial period before a successful reconnect. The big question is why is the peripheral

The confusing thing is the "crashed" sniffer; so I suspect in the trace I uploaded the last sampes seen are where the central successfully reconnected (and crashed the sniffer).

Although at end of trace those LL_VERSION_IND''s are showing bad sequence numbers.

RE: Using nrfsniffer to debug connection loss

Kenneth — Tue, 16 Mar 2021 14:01:30 GMT

What happens here is that the central send a connection request, but the connection request is not received by the peripheral. In such case the central will try for some attempts before giving up and try again. This is something that can happens from time to time due to noise, but if it always occurs (which seems to be the case). Then I suspect that the peripheral have not included the central in it's whitelist when advertising, and thereby don't allow the central to connect. None of the connections after 71727 is successful (you can see the SN and NESN don't increment). It doesn't look like any bonding is involved, so I don't expect you are using whitelist on the peripheral (at least you should not be)?

Kenneth

RE: Using nrfsniffer to debug connection loss

OwainIncus — Tue, 16 Mar 2021 13:15:33 GMT

Here the trace filedevzone.nordicsemi.com/.../12_2D00_03_2D00_21_2D00_1730_2D00_ladybayHookLoop.pcapng

#1755 initial connection made
#71263 Starts having connection issues / bad sequence numbers
#71718 peripheral starts advertising again
#71726 connects again; but does not decode/filters out peripheral packets>

Just see advertising/connection indicators till end of trace as sniffer had dropped filtered out packets.

RE: Using nrfsniffer to debug connection loss

Kenneth — Tue, 16 Mar 2021 12:31:37 GMT

This should work, I have done this many times and can sniff subsequent connections.

Maybe you are stopping and starting the sniffer between connections here? Can you share a log file that show what you describe?

Kenneth