Nvidia Xavier nx not detect FTDI adapter

I try to interface UM7 imu sensor with Nvidia jetson xavier NX trough USB. I used this FTDI USB adapter. But xavier nx not detect ftdi adapter. I connect it to jetson nano and my laptop, it’s work fine. Also I installed the driver from this site. Still not work.

When i run $ lsusb in Xavier NX

Bus 002 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
Bus 002 Device 002: ID 2109:0817 VIA Labs, Inc. 
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
Bus 001 Device 006: ID 1bcf:08b8 Sunplus Innovation Technology Inc. 
Bus 001 Device 005: ID 0461:4e04 Primax Electronics, Ltd 
Bus 001 Device 004: ID 2109:2812 VIA Labs, Inc. VL812 Hub
Bus 001 Device 002: ID 2109:2817 VIA Labs, Inc. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

When i run $ lsusb in my Jetson nano

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:57f3 Realtek Semiconductor Corp.
Bus 001 Device 002: ID 04ca:3015 Lite-On Technology Corp.
**Bus 001 Device 005: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC**
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

If you monitor “dmesg --follow”, then what extra log lines appear as a result of plugging in the USB device?

When I plugged the device while running “dmesg --follow ” this,
Output:

[ 2630.101267] usb 1-2.1: new low-speed USB device number 4 using tegra-xusb
[ 2630.102015] usb 1-2.1: Device not responding to setup address.
[ 2630.309905] usb 1-2.1: Device not responding to setup address.
[ 2630.517237] usb 1-2.1: device not accepting address 4, error -71
[ 2630.645196] usb 1-2.1: new low-speed USB device number 5 using tegra-xusb
[ 2630.646017] usb 1-2.1: Device not responding to setup address.
[ 2630.854023] usb 1-2.1: Device not responding to setup address.
[ 2631.061179] usb 1-2.1: device not accepting address 5, error -71
[ 2631.061510] usb 1-2-port1: attempt power cycle
[ 2632.972935] usb 1-2: usb_suspend_both: status 0

I used:

  • Jetson Xavier NX
  • Ubuntu 18.04
  • JETPACK VERSION 4.6.2
  • L4T VERSION 32.2.1

That sounds like a signal quality issue (it wouldn’t be a driver or software issue). As a test you might use it with and without an external HUB. Sometimes the HUB-to-device has better quality, as well as HUB-to-Jetson; conversely, direct connect from device to Jetson would have different signal characteristics. Even on otherwise 100% functioning systems R.F. is complicated and will change with minor changes in setup, so it is worth testing this. If not, then someone from NVIDIA might be able to suggest more on USB. I can tell you though that the above is not a software problem, and the device should function on a Jetson.

Thanks for the info. Can you tell me why this command does not run in xavier. dmesg | grep -i FTDI

when I run this in my host machine without any device plugged in, the output looks like this.

[ 1689.726044] usb 1-1: Manufacturer: FTDI
[ 1689.794739] usbcore: registered new interface driver ftdi_sio
[ 1689.794811] usbserial: USB Serial support registered for FTDI USB Serial Device
[ 1689.795085] ftdi_sio 1-1:1.0: FTDI USB Serial Device converter detected
[ 1689.796022] usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB0
[ 1697.574711] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[ 1697.574755] ftdi_sio 1-1:1.0: device disconnected

When I run dmesg | grep -i FTDI in xavier, nothing happens. What I missed?

USB is a “plug-n-play” communications pipe. This means it can query the end device, and the end device responds with what it is. USB then publishes the specs, and any driver which can handle the device will take ownership. If the USB signal itself is failing, then it means the query may not succeed, and thus no driver knows what the device is. In the case of a USB device plugin which does not have a driver, then you would see the FTDI mentioned from the query stage, possibly then with a note of the driver which loads. If the query itself fails, then there can be no mention of FTDI because the device never responds (at least not in a way which reaches the driver).

This is suspicious of signal quality issues:

[ 2630.646017] usb 1-2.1: Device not responding to setup address.
[ 2630.854023] usb 1-2.1: Device not responding to setup address.
[ 2631.061179] usb 1-2.1: device not accepting address 5, error -71

(note that power delivery issues can also cause such an error)