• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 55 replies
  • Answers 1 answer
  • Subscribers 73 subscribers
  • Views 29551 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 203434
Options
Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Sniffer on OSX - revisited

David Elvig

It looks like the last discussion of Sniffer on Devzone was 2-3 yrs ago.

I’ve ordered the nRF Dongle and will download the Windows-based nRF Sniffer app.

i can run this with WireShark on a Windows VM on my Mac, though I would like a Mac OSX option.

- Any news on that front?

- Any way the Bluetooth hardware built into the MacBook could serve a Mac Sniffer app?

thanks!

Parents
  • 0

    Still looking for a solution here.  I think a few others are having the same trouble.

    , what is the next steps?

  • 0 in reply to David Elvig

    Can you summarize your versions so I can look at it.

    OS Version:
    Wireshark version:
    Python version:
    Pyserial version:

    Segger jlink version on PC:
    Segger jlink version or build date on the jlink emulator on nRF5x-DK:

    nRF Sniffer version:

    PCA board number: 

    =

    Python 32 bit or 64 bit:

    Use: 

    import ctypes
    ctypes.sizeof(ctypes.c_void_p)

    8 -> 64 bit
    4 -> 32 bit

  • 0 in reply to David Edwin

    I've done all but the minicom step.  I ran the Windows j-Link Configurator and it shows this screen

    as in the sniffer 2.0 documentation

    I ran j-Link Commander and with exec invalidatefw I get this

    I said "no" since I think we're trying to stay on older builds... That said, I'm typing commands that I don't fully understand (I don't understand all of the layers involved)

    I expect my hardware is working (both the dongle (PCA10031) and the Dev Kit (PCA10040)).  I can use the dongle without trouble using nRFConnect on the Mac, and the DK works well with example SDK apps, and my own MIDI BLE app.

    I've stayed on the 6.16c version throughout (on Mac and Win)

    I did not easily find how to install minicom on the Mac.

    I did flash the Dev Kit board using the nRF52832_XXAA parameter to "erase"

    No difference in Wireshark visibility.

    Is there a chance of a screen-share where you could look over my shoulder, @David Edwin?

    I expect it's a missed step on my part... I have two hardware options to try, and access to all of the various permutations of j-link, segger and Wireshark.

    I'm available any time around the clock to make that happen (and have WebEx available for screen-sharing)

  • 0 in reply to David Edwin

    I've manage to get hold off an old macbook pro in order to mimic the settings David Edwin suggested.

    OS X 10.11.6
    Wireshark : 2.4.1 (also tried 2.4.2 and the latest 2.4.6)
    python 2.7.14 (installed with brew, could not find a way to install 2.7.10 using brew.)
    pyserial 3.2.1
    nRF Sniffer v2 Beta 1

    PCA10040

    Segger jlink 6.16c

    Still the interface does not pop up in Wireshark. This is starting to be a bit frustrating now.

  • 0 in reply to David Edwin

    I tried this with a Windows machine as well. Worked on the first try. So there's something strange with the OSX version.

    OS Version:            Windows 10 Pro 64 bit
    Wireshark version: 2.4.2
    Python version:      2.7.14
    Pyserial version:    3.4

    Segger jlink version on PC:    6.16c
    Segger jlink version or build date on the jlink emulator on nRF5x-DK:               ??????

    PCA board number:    
    - PCA10040 (Dev Kit)

  • 0 in reply to David Elvig

    We need to see some characters on the screen when connecting to the board from OS X.

    "screen <port> 460800"  

    If that does not happen then

    Action 1:
    we need to do this in addition (we will attempt to disable the mass storage device to see if this improves the situation. 

    Action 2:

    We attempt to see the characters when connecting to the board on windows. In addition can you connect to the board in Windows using termite or other terminal application at 460800 to verify that the port is accessible and that characters are coming out of it.

  • 0 in reply to David Edwin

    I have run the MSDDisable command (and alternatively MSDEnable) on both OSX and Windows 7, getting "Probe Configured Successfully" in all cases.

    I do see that the USB drive representing the dongle goes away after the MSDDisable and reappears with MSDEnable.

    After running MSDDisable, I get the same non-response from the terminal apps:

    On OSX using "screen cu.usbmodem1461 460800" I get a screen window with no characters as before

    On Windows using puTTY, connecting to "COM18"- the JLink USB serial port at 460800, I get a similar result... a blank terminal window with no response to typing and no characters displayed (and no apparent way to exit the terminal session)

Reply
  • 0 in reply to David Edwin

    I have run the MSDDisable command (and alternatively MSDEnable) on both OSX and Windows 7, getting "Probe Configured Successfully" in all cases.

    I do see that the USB drive representing the dongle goes away after the MSDDisable and reappears with MSDEnable.

    After running MSDDisable, I get the same non-response from the terminal apps:

    On OSX using "screen cu.usbmodem1461 460800" I get a screen window with no characters as before

    On Windows using puTTY, connecting to "COM18"- the JLink USB serial port at 460800, I get a similar result... a blank terminal window with no response to typing and no characters displayed (and no apparent way to exit the terminal session)

Children
Related