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?

thanks!

  • Davids-MacBook-Pro-2:extcap davidelvig$ ./nrf_sniffer.py --extcap-interfaces
    extcap {version=2.0.0}{display=nRF Sniffer}{help=http://www.nordicsemi.com/eng/Products/Bluetooth-low-energy/nRF-Sniffer#Downloads}
    control {number=0}{type=selector}{display=Device}{tooltip=Device list}
    control {number=1}{type=string}{display=Passkey / OOB key}{tooltip=6 digit temporary key or 16 byte Out-of-band (OOB) key in hexadecimal starting with '0x', big endian format. If the entered key is shorter than 16 bytes, it will be zero-padded in front'}{validation=\b^(([0-9]{6})|(0x[0-9a-fA-F]{1,32}))$\b}
    control {number=2}{type=string}{display=Adv Hop}{default=37,38,39}{tooltip=Advertising channel hop sequence. Change the order in which the siffer switches advertising channels. Valid channels are 37, 38 and 39 separated by comma.}{validation=^\s*((37|38|39)\s*,\s*){0,2}(37|38|39){1}\s*$}{required=true}
    control {number=3}{type=button}{role=help}{display=Help}{tooltip=Access user guide (launches browser)}
    control {number=4}{type=button}{role=restore}{display=Defaults}{tooltip=Resets the user interface and clears the log file}
    control {number=5}{type=button}{role=logger}{display=Log}{tooltip=Log per interface}
    value {control=0}{value= }{display=All advertising devices}{default=true}
    Davids-MacBook-Pro-2:extcap davidelvig$ 

  • did you actually give the right path to the UART, it is usually in /dev .

    Verify that by using the "screen <port> 460800", you should see some characters on the screen.

  • 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

  • Thanks for your patience.

    I get the same result as above with

    "screen cu.usbmodem1461 460800"

    Dave

Related