Setting up the nrfSniffer

[Den]

Hi,

I am following the nRF_Sniffer_UG_v2.2.pdf to setup the nrfSniffer. Wireshark does not show me my board among the interfaces. I had a look at the troubleshooting part. In part 6.1 the given tests are;

1. Run nrf_sniffer.bat --extcap-interfaces to list the interface.

2. If this exits with a python error, verify that python.exe can be run from the command line c:>python.exe --version, where the Python version is the same as Section 1.2 “Required software” on page 2.

My setup passes the second test. I see the version as 2.7.16. However it fails the first test; the outcome is nrf_sniffer.bat is not recognized as an internal or external command . I think the step I am missing is (correct me if I am wrong);

"For Windows - Verify that the path used for python in the nrf_sniffer.bat file correctly points to the required version as stated in “Required software“ on page 2."

Can someone please explain what this means?

Also is requirements.txt in pyserial-master supposed to be empty?

Thanks. 

[AndreasF]

Hi.

"For Windows - Verify that the path used for python in the nrf_sniffer.bat file correctly points to the required version as stated in “Required software“ on page 2."

 It means that you have to verify that it is Python 2.7.xx that is running the nrf_sniffer.bat file:

@echo off
python "%~dp0nrf_sniffer.py"  %*

(The content of the file above).

Have you checked this?

Also is requirements.txt in pyserial-master supposed to be empty?

 Looks empty on GitHub, you can install it with pip to be sure;

python -m pip install pyserial

Best regards,

Andreas

[Den]

Hi Andreas,

Thanks for your assistance.

I can confirm the the content of the nrf_sniffer.bat file's content is as you showed. 

Yes, I have checked the stuff under 6.1

I am not sure if pyserial has been installed correctly. How can I make sure of that. I am not experienced in using the cmd terminal. So I will be happy if you can please direct me as required. I have tried to installed pyserial as you said and the output is;

C:\Users\Denin\Desktop\pyserial-master>python -m pip install pyserial
Collecting pyserial
  Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x0000000004DDDC18>: Failed to establish a new connection: [Errno 11002] getaddrinfo failed',)': /simple/pyserial/
  Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x0000000004DDDD68>: Failed to establish a new connection: [Errno 11002] getaddrinfo failed',)': /simple/pyserial/
  Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x0000000004DDDF28>: Failed to establish a new connection: [Errno 11002] getaddrinfo failed',)': /simple/pyserial/
  Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x0000000004E53128>: Failed to establish a new connection: [Errno 11002] getaddrinfo failed',)': /simple/pyserial/
  Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x0000000004E532E8>: Failed to establish a new connection: [Errno 11002] getaddrinfo failed',)': /simple/pyserial/
  Could not find a version that satisfies the requirement pyserial (from versions: )
No matching distribution found for pyserial

Regards,

Denin

[AndreasF]

Hi.

Which version of Wireshark do you have?

Best regards,

Andreas

[Den]

Hello Andreas,

The Wireshark version is 3.0.3.  

I have been playing around with things to fix it. I want to give you more input; as said Wireshark starts to capture advertising packets and stops capturing after some random time. If I reset the board, it goes on capturing. Please see the picture below. The red arrows are where I reset the board. This makes me think that it is the board that stops sending packets to Wireshark since it timeouts and goes on giving timeout warning until I reset the board. I am using a custom board which hosts nRF52832 based ISP1507. I have been using it without any compatibility problems. 

Another thing is that when it captures, it only captures advertising packets. I have tried what it says in part 5.3 however it did not help.

Best regards,

Denin

[AndreasF]

Hi.

Can you try this firmware instead: nrf_sniffer_2.0.0_c87e17d.zip

It's the latest sniffer and it will be released soon.

Best regards,

Andreas

[Den]

Hi again Andreas,

I have changed the content of extcap folder according to the new firmware you have sent. After some time again it seems that the board stops sending packets. If I reset the board it sends for some more time until it stops again. The log looks the same. 

There isn't anything that I need to change other than extcap folder right?

One more observation; if I turn the board on and wait long enough, when I open the Wireshark it does not see the board. Obviously some time after the board is turned on, it stops communicating with computer. 

Have you had this error before?

Best regards,

Denin

[AndreasF]

Hi.

I've not had this error before.

Can you try to downgrade the j-link to this version?

segger_jlink.zip

Best regards,

Andreas

[Den]

Hi,

Both host and emulator firmware are now dated 2017 June 13 10:37. I deleted the previous jlink version. 

Unfortunately the behavior is the same, it stops after a while. 

I have also tried the sethwfc force command but I think its not accepted in this version. 

Is there anything else I can try?

Best regards,

Denin

[AndreasF]

Hi.

Unfortunately, I have no other suggestions to add.

I have talked to the developer and he is aware of the issues your facing and working on fixing those issues for the next release.

I hope this is of some comfort.

Best regards,

Andreas

[Den]

Hi Andreas,

I am sorry to hear this.

If we have tried every possible way and if the developer is aware of these, does this mean that I can be assured of that the problem is not caused by my set up? So buying a nRF52840 DK to use as sniffer instead of my custom board would not help?

Best regards,

Denin

[AndreasF]

Hi.

I cannot exclude the fact that your custom setup might affect the issue. It could be possible that the sniffer is more stable on one of our DK's or Dongles.

Is the email you're registered with on DevZone you're primary email?

I could arrange a Dongle for you. I will send you an email.

Best regards,

Andreas

[Den]

Thanks for your kind support Andreas. I will update this post when I give it try with nRF52480 DK.