FTDI USB Serial Device - where is ttyUSB0?


Cross-post from Sierra Wireless forum:

[quote]When I plug in my FTDI USB Serial cable, I see:

[ 690.149702] usb 1-1.3.2: new full-speed USB device number 7 using msm_hsic_host
[ 690.206805] ftdi_sio 1-1.3.2:1.0: FTDI USB Serial Device converter detected
[ 690.219624] usb 1-1.3.2: Detected FT232RL
[ 690.222615] usb 1-1.3.2: Number of endpoints 2
[ 690.227071] usb 1-1.3.2: Endpoint 1 MaxPacketSize 64
[ 690.232748] usb 1-1.3.2: Endpoint 2 MaxPacketSize 64
[ 690.236929] usb 1-1.3.2: Setting MaxPacketSize 64
[ 690.248588] usb 1-1.3.2: FTDI USB Serial Device converter now attached to ttyUSB0

But there is no /dev/ttyUSB0

root@swi-mdm9x15:~# ls /dev/ttyUSB0
ls: /dev/ttyUSB0: No such file or directory
root@swi-mdm9x15:~# ls /dev/ttyUSB*
ls: /dev/ttyUSB*: No such file or directory

So how do I use it ??


MangOH: USB-serial device doesn't create /dev/ttyUSB1

What hadware version are you using? Note that USB0 is run by Arduino to WP connection.


It is a unit from the Innovation Summit last year. How do I check the version?

The same happens whether I plug the FTDI cable into the USB Host socket on the main board, or the one on the IoT connector.


The same unit as here:


I would recommend moving to DV3 board as we dont support very early hardware. The Innovation Summit hardware was early hardware.

The USB issue could be due to the fact that USB0 is used in firmware to talk to Arduino in DV3 and onwards. PCB that show rev 7 and up will be supported by us.


But, surely, if ttyUSB0 was being used for the Arduino connection, then plugging in the cable would show up as ttyUSBx where x != 0 ??

If it’s correctly recognised that the device has been plugged in, what would prevent it from being assigned a proper /dev/ttyUSBx identity?

If seems to be a Linux issue rather than a hardware issue?


I got a new mangOH - yes, it does work with the FTDI cable, creates a /dev/ttyUSBx and I can send & receive stuff to the port from the command line.


closed #8