This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF BLE Sniffer Crashing

nRF BLE sniffer is crashing within the first few minutes of use. Attached is the log of one sniffer session from the start to when it crashes.

Here is my log.txt from starting the application to when it crashed.

Has anyone experienced this or knows how to fix it? Thanks in advanced.


Software used:

  • nRF BLE Sniffer win version 1.0.1_1111

  • Wireshark Version 1.12.7

  • Windows 7

Hardware used:

  • N51422 usb.
  • Hi, upgrading from v5.10i to v5.10p (including J-Link OB FW on actual DK) solved the problem! Many thanks for support. Cheers Jan

  • Hi, Having used the sniffer for a while my guess is that the capture uplink to the PC is too slow, I see symptoms of dropped packets and crashes but only with a lot of traffic.

    I didn't stick a scope on it yet but I suspect the NRF UART in the scan firmware is was compiled only to use a 110kbps uart; no doubt the segger SAM7 debug cpu which provides the UART<->USB bridge is fine with much higher than that; e.g. 1mbps should be no problem.

    Can someone at Nordic rebuild the NRFDK sniffer firmware to run 1mbps (or if it's open source, where I can do it?)

    It's a really good tool by the way; until we get a practical SDR setup that can simultaneously analyze+sniff the whole 80mhz 2.4ghz range at once (..soon I think :-) ) the NRF sniffer is my fave.

    Update: Looking at the Adafruit python client for the nordic fw it appears to run at ~400kbps, so maybe that's not the problem? I do seem to get the sniffer dropping packets on a busy connection (e.g. with a linux Central device pumping a lot of packets w/fast connection interval). If there was an easy fix to increase the bandwidth that'd be great.

    Thanks,

  • I am facing the same issue.Could you please tell me how to capture logs. Thank you

Related