nRF BLE Sniffer Crashing

RE: nRF BLE Sniffer Crashing

priya — Thu, 01 Jun 2017 19:54:06 GMT

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

RE: nRF BLE Sniffer Crashing

drtune — Sat, 24 Dec 2016 20:17:22 GMT

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,

RE: nRF BLE Sniffer Crashing

endnode — Tue, 01 Mar 2016 16:53:40 GMT

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

RE: nRF BLE Sniffer Crashing

Hung Bui — Tue, 01 Mar 2016 15:47:17 GMT

The sniffer console doesn't use Segger's dll however it does interface with the Segger chip on the board. The issue may also be with the Segger chip that it couldn't handle large amount of data flooding through UART. When you update to new Jlink driver, it will also update the firmware on the Segger chip on board, that I hope would help solving the issue. Could you try to test with the latest one which is v5.10p and let the Segger chip be updated (do some flash operation such as reprogram the sniffer firmware, a popup asking for firmware update will appear)

RE: nRF BLE Sniffer Crashing

endnode — Tue, 01 Mar 2016 15:12:23 GMT

You are right, this wasn't answer in terms of how to solve the question but rather how to reproduce it (which you asked for). I'm having 4 SEGGER J-Link packages installed in my software (V5.10d being the latest of them), is Sniffer executable pointing to some specific DLLs? Where should they be located? Thanks

RE: nRF BLE Sniffer Crashing

Hung Bui — Tue, 01 Mar 2016 15:01:02 GMT

Hi Jan,

Next time please post as question comment or create a new question, this is not an answer for the original question.

I tried to test with your firmware of fast advertising in the other case, but I still can use the sniffer to follow the advertising and connection with the device. Could you try again with the latest Segger Jlink driver ?

RE: nRF BLE Sniffer Crashing

endnode — Sun, 21 Feb 2016 14:40:10 GMT

Hi @hungbui,

I've experienced similar crashes of nRF BLE Sniffer app (latest release v1.0.1) on nRF51-DK (PCA10028 V1.1.0) once following fast advertising peripheral (host PC is running Win7 64bit). I've already experienced similar (buffer overflow/exception) problem in Android MCP app (see this thread). Sniffer PC app starts as it should, lists visible peripherals but once I select the fast one it crashes within 1s (I even cannot start the Wireshark how fast it is;). App closes without any further visible warning/error message to the end user. Do you have any logging/debugging in the Sniffer app which would help? I suspect that issue reported by Chris above is similar (sniffer app - or COM port link? - are exhausted by the flood of messages and crashes at some point).

Could you try to reproduce with the firmware I've provided to Alexander in mentioned question?

Many thanks Jan

RE: nRF BLE Sniffer Crashing

Hung Bui — Wed, 07 Oct 2015 12:18:37 GMT

Hi Chris, We haven't experienced this before. Could you try on another computer ?