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

nRF Sniffer on linux host - uart connection

I'd tried some first steps using nRF Sniffer on a linux host.

Within sniffer_uart_protocol.xlsx I read something about the Uart packet format et cetera.

I'd programmed my PCA10000 V2.2.0 with the current sniffer version 0.9.7 while succesfully trying out nRF Sniffer on a Windows host machine.

When I plug the PCA10000 to my linux machine, I'd expected a new /dev/ttyUSBx but it isn't. Using lsusb, I just see a new usb device: Bus 002 Device 012: ID 1366:0105 SEGGER. And in /dev, I see a ttyACM3.

  • Did anybody know if the /dev/ttyACMx is related to the nRF Sniffer uart interface?
  • And what about the connection parameters?
    • Baudrate?
    • Rts / Cts hardware handshake?

I'd performed some tests with 38.400 bd and 115.200 bd. On my /dev/ttyACM3 I see lots of incoming data, but never the pattern 0xBE 0xEF as described in sniffer_uart_protocol.xlsx.

  • FormerMember
    0 FormerMember

    Joe, Thanks for looking into porting the sniffer software to Linux. When I first started using PCA10000, I was also surprised with ttyACM3 (sometimes it is ttyACM0 or 4, found out the hard way). Just replace ttyUSBx by ttyACMx in what ever code you are developing, should work.

    Regarding the connection parameters, the baud rate can be negotiated as per the protocol mentioned in the xlsx file. From the UART.py file we can see that the initial baud rate is 460800 bps. This is the maximum baud rate that my PCA10000 can run on, so I guess that need not be changed. PCA10000 needs RTS/CTS hardware handshake to work properly.

    Hope this helps!

Related