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

Device popup menu in Wireshark not working

I've got Wireshark running with nRF Sniffer, but it is not really working for me.

I'm using a PCA10040 board as the sniffer hardware.

I'm running on a Mac with MacOS 10.14.4.

I'm running Python 2.7.10 and I installed PySerial 2.7.

I downloaded nrfsniffer200beta312oct20181c2a221.zip.

I installed the hex file for PCA10040 onto the board.

I installed the nRF profile into Wireshark and installed the python scripts into the extcap folder.

Note that I first installed Wireshark 3.0.2 and then downgraded to 2.6.9, which did not affect my issue.

When I run Wireshark, I can select the nRF sniffer profile and I can select the interface to my sniffer board. I see all of the advertising data for all devices, but when I select a specific device from the Device popup menu, it does not affect the output. I still see all of the advertising data. If I select my device and connect to it from my iPad then I see the advertising stop for my device, but I continue to see the advertising packet for all of the other devices in my area. Also, I only see advertising data. It does not show any other packet types from my device.

Here is the log window contents after selecting my device.

INFO: Log started at Fri May 31 15:37:30 2019

INFO: args: ()

INFO: kwargs: {'callbacks': [('*', <bound method Sniffer.passOnNotification of <Sniffer(Thread-2, initial)>>)]}

INFO: board ID (random): 156

INFO: starting scan

INFO: starting scan

INFO: Sent key value to sniffer: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]

INFO: Sent key value to sniffer: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]

INFO: Sniffing device 13 - ""Sm""

INFO: Following "Sm" f7:73:bf:4a:a6:c3 random

It says it is following my device, but it is still following all devices.

Any help is appreciated.

Parents
  • Hi.

    I have to look a bit more at this, can you provide me with some log files?

    Best regards,

    Andreas

  • If you meant a capture log, here's a screen shot showing advertising data. You can see the selected device "Sm" is my device, but the advertising packets are still all devices. I have one of my device packets selected, so you can see its data in the details pane. I never see any connect packets, which I guess is because the device selection just isn't working.

    Advertising data

  • Hi.

    I think that the python script could be the issue, I'm still waiting on response from the developer.

    Do you have any chance to run a virtual machine with Windows and try?

    Best regards,

    Andreas

  • Sorry this has taken so long, but I do have a Windows 7 VM on my iMac. I just spent the morning doing the installation and the behavior is exactly the same. I get advertising packets for all of the device in the area, but selecting a specific device from the Device list has no effect. It continues to display advertising packets from all of the devices and it does not follow a connection.

    If there is anything I can do to help debug this, please let me know.

  • Hi.

    Which J-Link version do you have?

    What version is your DK?

    Are you able to do a J-Link reset?

    It should also be noted that there are issues with odd numbers of Wireshark, that is x.y.<odd number> .

    Best regards,

    Andreas

  • Which J-Link version do you have?

    Are you able to do a J-Link reset?

    [iMaci9:/Applications/SEGGER/JLink_V634b] john% JLinkExe 

    SEGGER J-Link Commander V6.34b (Compiled Aug 13 2018 16:38:25)

    DLL version V6.34b, compiled Aug 13 2018 16:38:14

    Connecting to J-Link via USB...FAILED: Cannot connect to J-Link via USB.

    J-Link>connect

    J-Link connection not established yet but required for command.

    Connecting to J-Link via USB...O.K.

    Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jul 12 2018 11:44:41

    Hardware version: V1.00

    S/N: 682485235

    VTref=3.300V

    Please specify device / core. <Default>: NRF52

    Type '?' for selection dialog

    Device>nRF52832_XXAA

    Please specify target interface:

      J) JTAG (Default)

      S) SWD

      T) cJTAG

    TIF>s

    Specify target interface speed [kHz]. <Default>: 4000 kHz

    Speed>1000

    Device "NRF52832_XXAA" selected.

    Connecting to target via SWD

    Found SW-DP with ID 0x2BA01477

    Found SW-DP with ID 0x2BA01477

    Scanning AP map to find all available APs

    AP[2]: Stopped AP scan as end of AP map has been reached

    AP[0]: AHB-AP (IDR: 0x24770011)

    AP[1]: JTAG-AP (IDR: 0x02880000)

    Iterating through AP map to find AHB-AP to use

    AP[0]: Core found

    AP[0]: AHB-AP ROM base: 0xE00FF000

    CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)

    Found Cortex-M4 r0p1, Little endian.

    FPUnit: 6 code (BP) slots and 2 literal slots

    CoreSight components:

    ROMTbl[0] @ E00FF000

    ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7

    ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT

    ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB

    ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM

    ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU

    ROMTbl[0][5]: E0041000, CID: B105900D, PID: 000BB925 ETM

    Cortex-M4 identified.

    J-Link>loadfile /Applications/Wireshark.app/Contents/MacOS/extcap/nrfsniffer200beta312oct20181c2a221/hex/sniffer_pca10040_1c2a221.hex 

    Downloading file [/Applications/Wireshark.app/Contents/MacOS/extcap/nrfsniffer200beta312oct20181c2a221/hex/sniffer_pca10040_1c2a221.hex]...

    Comparing flash   [100%] Done.

    Verifying flash   [100%] Done.

    J-Link: Flash download: Bank 0 @ 0x00000000: Skipped. Contents already match

    O.K.

    J-Link>r

    Reset delay: 0 ms

    Reset type NORMAL: Resets core & peripherals via SYSRESETREQ & VECTRESET bit.

    Reset: Halt core after reset via DEMCR.VC_CORERESET.

    Reset: Reset device via AIRCR.SYSRESETREQ.

    What version is your DK?

    I'm confused. Do you mean my application? Does that matter? Does the sniffer only work with devices running Nordic chips or softdevices? This is the softdevice hex file I have installed on my board:

    s132_nrf52_3.0.0_softdevice.hex

    It should also be noted that there are issues with odd numbers of Wireshark, that is x.y.<odd number> .

    Maybe you could elaborate?

    From my OP, on my Mac:

    Note that I first installed Wireshark 3.0.2 and then downgraded to 2.6.9, which did not affect my issue.

    The Windows version I just installed this week is 3.0.2.

  • Hi again.

    jsheaney said:

    What version is your DK?

    I'm confused. Do you mean my application? Does that matter? Does the sniffer only work with devices running Nordic chips or softdevices? This is the softdevice hex file I have installed on my board:

    s132_nrf52_3.0.0_softdevice.hex

     I was thinking about the version number printed on the development kit (DK), looks like you have v1.0.0 from the logs above (Hardware version: V1.00).

    jsheaney said:

    It should also be noted that there are issues with odd numbers of Wireshark, that is x.y.<odd number> .

    Maybe you could elaborate?

    I was told by our developer that version of Wireshark that are odd number releases tend to have some stability issues.

    Can you try this version of the nRF Sniffer:

    nrf_sniffer_2.0.0_5june2019_c87e17d.zip

    Best regards,

    Andreas

Reply
  • Hi again.

    jsheaney said:

    What version is your DK?

    I'm confused. Do you mean my application? Does that matter? Does the sniffer only work with devices running Nordic chips or softdevices? This is the softdevice hex file I have installed on my board:

    s132_nrf52_3.0.0_softdevice.hex

     I was thinking about the version number printed on the development kit (DK), looks like you have v1.0.0 from the logs above (Hardware version: V1.00).

    jsheaney said:

    It should also be noted that there are issues with odd numbers of Wireshark, that is x.y.<odd number> .

    Maybe you could elaborate?

    I was told by our developer that version of Wireshark that are odd number releases tend to have some stability issues.

    Can you try this version of the nRF Sniffer:

    nrf_sniffer_2.0.0_5june2019_c87e17d.zip

    Best regards,

    Andreas

Children
No Data
Related