nRF BLE Sniffer Crashing

[Chris smith]

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.

[Hung Bui]

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

[endnode]

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

[Hung Bui]

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 ?

[endnode]

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

[Hung Bui]

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)