The USB side of that cable requires a driver for the particular serial UART chip. The reason for watching “dmesg --follow” while plugging in the cable is to see if hints are given as to driver status.
If you monitor “dmesg --follow”, and then plug in the device, what log do you see? Not all serial devices are named with a “/dev/ttyUSB#” format…some get udev to rename the device. In other cases a different USB serial UART chip might need an extra driver.
nvidia@tegra-a:~$ dmesg --follow
....
[ 36.610598] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control off
[ 36.610650] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 58.842440] mttcan c320000.mttcan can1: Bitrate set
[ 58.846164] mttcan_controller_config: ctrlmode 0
[ 58.846184] mttcan c320000.mttcan can1: Bitrate set
[ 58.857873] can: controller area network core (rev 20120528 abi 9)
[ 58.858114] NET: Registered protocol family 29
[ 58.864727] can: raw protocol (rev 20120528)
[ 64.066428] mttcan c310000.mttcan can0: Bitrate set
[ 64.086527] mttcan_controller_config: ctrlmode 10
[ 64.086547] mttcan c310000.mttcan can0: Bitrate set
[ 64.110613] mttcan c320000.mttcan can1: Bitrate set
[ 64.131075] mttcan_controller_config: ctrlmode 10
[ 64.131135] mttcan c320000.mttcan can1: Bitrate set
[ 64.164622] EXT4-fs (vblkdev3): mounted filesystem with ordered data mode. Opts: (null)
[ 158.380973] usb 1-1.1: new high-speed USB device number 7 using tegra-xusb
[ 158.486047] usb 1-1.1: New USB device found, idVendor=09d7, idProduct=0100
[ 158.486056] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 158.486060] usb 1-1.1: Product: NovAtel GPS Receiver
[ 158.486064] usb 1-1.1: Manufacturer: NovAtel Inc.
[ 158.486067] usb 1-1.1: SerialNumber: BMAW18060002P
nvidia@tegra-a:~$ lsusb
Bus 002 Device 002: ID 05e3:0612 Genesys Logic, Inc.
Bus 002 Device 003: ID 0781:558c SanDisk Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 1546:01a8 U-Blox AG
Bus 001 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
nvidia@tegra-a:~$
nvidia@tegra-a:~$
nvidia@tegra-a:~$ lsusb
Bus 002 Device 002: ID 05e3:0612 Genesys Logic, Inc.
Bus 002 Device 003: ID 0781:558c SanDisk Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 1546:01a8 U-Blox AG
Bus 001 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 007: ID 09d7:0100 Novatel Wireless NovAtel FlexPack GPS receiver
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
nvidia@tegra-a:~$
I do have remove the “99-usb-serial.rules” and restart, still not working…
I have also tried another DRIVE AGX Xavier, same result…
nvidia@tegra-a:~$ lsusb
Bus 002 Device 002: ID 05e3:0612 Genesys Logic, Inc.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 1546:01a8 U-Blox AG
Bus 001 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 003: ID 09d7:0100 Novatel Wireless NovAtel FlexPack GPS receiver
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
nvidia@tegra-a:~$ dmesg --follow
...
ports DPO and FUA
[ 170.832840] sda: sda1
[ 170.836841] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
[ 170.837111] sd 0:0:0:0: [sda] Attached SCSI disk
[ 207.053706] usb 1-1.1: USB disconnect, device number 3
[ 280.493665] usb 1-1.1: new high-speed USB device number 7 using tegra-xusb
[ 280.594746] usb 1-1.1: New USB device found, idVendor=09d7, idProduct=0100
[ 280.594753] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 280.594785] usb 1-1.1: Product: NovAtel GPS Receiver
[ 280.594788] usb 1-1.1: Manufacturer: NovAtel Inc.
[ 280.594791] usb 1-1.1: SerialNumber: BMAW18060002P
nvidia@tegra-a:~/Workspace/ngpsusbpackage$ sudo bash ngpsusb-install
...
DKMS: add completed.
Error! Your kernel headers for kernel 4.9.131-rt93-tegra cannot be found.
Please install the linux-headers-4.9.131-rt93-tegra package,
or use the --kernelsourcedir option to tell DKMS where it's located
Error! Your kernel headers for kernel 4.9.131-rt93-tegra cannot be found.
Please install the linux-headers-4.9.131-rt93-tegra package,
or use the --kernelsourcedir option to tell DKMS where it's located
dpkg: error processing package ngpsusbpackage (--install):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
ngpsusbpackage
And seems that hard to fetch linux-headers-4.9.131-rt93-tegra
It isn’t clear which log is specifically occurring on plug in of that device, but I suspect this is because the USB cable is hosting more than one device type. Is it correct that this is the only dmesg text which occurred as a result of connecting the cable?
[ 280.493665] usb 1-1.1: new high-speed USB device number 7 using tegra-xusb
[ 280.594746] usb 1-1.1: New USB device found, idVendor=09d7, idProduct=0100
[ 280.594753] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 280.594785] usb 1-1.1: Product: NovAtel GPS Receiver
[ 280.594788] usb 1-1.1: Manufacturer: NovAtel Inc.
[ 280.594791] usb 1-1.1: SerialNumber: BMAW18060002P
Some other devices showed up, but may not be part of this and I’d like to make sure I’m looking at the right device. For example, “sda1” is a disk partition…perhaps the device has a writable partition, but perhaps this is not from plugging in the device. There is also some “mttcan” text, and this would probably be a CAN bus (looks like a network device in “ifconfig” if it is configured).
The actual NovAtel device is a custom USB device needing a custom driver, and is not an ordinary serial UART. Underneath this customization there may indeed be an ordinary serial UART, but the plug-n-play information published by the device upon plugin is such that generic drivers cannot be used. If this is the serial device, then you’ll need the NovAtel driver to get the ttyUSB# to show up. USB has seen the device connect and has reported the specifications, but nothing took ownership (there is no driver, or else the customization of the information prevented the generic driver from recognizing it can handle the device).
I’m thinking there is more software you need to install for this, but keep in mind that desktop PC drivers won’t work on this architecture. If you go to the device’s support web site, then you’ll need the arm64/aarch64 drivers. If the CAN device is part of this, then you may also need user space software to talk to the CAN interface.
Fixed by installing usb-serial-simple.ko, which contains novatel_gps
nvidia@tegra-a:~$ sudo modprobe usbserial
nvidia@tegra-a:~$ sudo insmod usb-serial-simple.ko
nvidia@tegra-a:~$ dmesg
...
[ 9421.234635] usbcore: registered new interface driver usbserial
[ 9424.247233] usbcore: registered new interface driver usb_serial_simple
[ 9424.247273] usbserial: USB Serial support registered for carelink
[ 9424.247294] usbserial: USB Serial support registered for zio
[ 9424.247316] usbserial: USB Serial support registered for funsoft
[ 9424.247336] usbserial: USB Serial support registered for flashloader
[ 9424.247381] usbserial: USB Serial support registered for google
[ 9424.247427] usbserial: USB Serial support registered for libtransistor
[ 9424.247470] usbserial: USB Serial support registered for vivopay
[ 9424.247514] usbserial: USB Serial support registered for moto_modem
[ 9424.247552] usbserial: USB Serial support registered for motorola_tetra
[ 9424.247591] usbserial: USB Serial support registered for novatel_gps
[ 9424.247630] usbserial: USB Serial support registered for hp4x
[ 9424.247666] usbserial: USB Serial support registered for suunto
[ 9424.247702] usbserial: USB Serial support registered for siemens_mpi
Then NovAtel can successfully attached to /dev/ttyUSB0…2
[ 1361.124082] usb_serial_simple 1-1.1:1.0: device disconnected
[ 1364.157877] usb 1-1.1: new high-speed USB device number 8 using tegra-xusb
[ 1364.258824] usb 1-1.1: New USB device found, idVendor=09d7, idProduct=0100
[ 1364.258832] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1364.258835] usb 1-1.1: Product: NovAtel GPS Receiver
[ 1364.258837] usb 1-1.1: Manufacturer: NovAtel Inc.
[ 1364.258839] usb 1-1.1: SerialNumber: BMAW18060002P
[ 1364.260571] usb_serial_simple 1-1.1:1.0: novatel_gps converter detected
[ 1364.260797] usb 1-1.1: novatel_gps converter now attached to ttyUSB0
[ 1364.261169] usb 1-1.1: novatel_gps converter now attached to ttyUSB1
[ 1364.261388] usb 1-1.1: novatel_gps converter now attached to ttyUSB2
Fetch usb-serial-simple.ko by kernel cross-compilation, only need change following configuration, adding line 483
I have a device ,connect with RS232 to usb serial cable(067b:23c3 Prolific),but don’t find a ttyUSB device in AGX Xavier.
ai@ai-desktop:~$ lsusb
Bus 002 Device 006: ID 05e3:0626 Genesys Logic, Inc.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 008: ID 067b:23c3 Prolific Technology, Inc.
Bus 001 Device 007: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 006: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
