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

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?


Parents Reply Children
  • I've done the following:
    - Identified the serial port with this partial ls from \dev

    cu.Bluetooth-Incoming-Port	ttyv0
    cu.LGHBS760-CSRGAIA		ttyv1
    cu.MALS				ttyv2
    cu.SOC				ttyv3
    cu.usbmodem1451061		ttyv4
    cu.usbmodem1461			ttyv5
    disk0				ttyv6
    disk0s1				ttyv7

        It is the "cu.usbmodem1461" entry that appear/disappears with plugging/unplugging the dongle

    I typed the following into Terminal:      
            screen cu.usbmodem1461 46800

    ...resulting in:

    No typed keystrokes show, and it responds only to the Ctrl-a-Ctrl-k command to quit.

  • The baud rate I suggested was 460800 (not 46800 as I see in your screen shot). 
    Please connect to the port at 460800 and see if you are getting characters on the "screen".


  • Thanks for your patience.

    I get the same result as above with

    "screen cu.usbmodem1461 460800"


  • That is a problem, can you try with other terminal programs like minicom and open the port at 460800. You need to see something on the UART. Turn on the hardware flow control if possible.


    1. Can you verify that the board is indeed working by flashing some example program like ble_app_uart and running those examples.

    2, Can you also try with a different board 

    3. Specify the board PCA10040 and the PCA10031 version numbers ?

    4. Please stay on jlink 6.16c on the jlink emulator for all the experiments and actions.

    Edit: Additional Action:

    I checked if the jlink 6.16c for OS X and Windows are bundling the identical version of the jlink emulator firmware they are NOT. If you have a windows PC can you install jlink 6.16c and use the exec invalidatefw to set the jlink emulator firmware to what was bundled with jlink 6.16c for windows. Then use the board with OS X. Let me know if this is possible for you.

    Edit : ping

  • 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)