Orin USB problems

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
,
1

I am using orin Developer Kit and have two devices (SparkFun ZED-F9P-RtK2) that need to use usb TTY port (Serial Port-TTyACM), which I find when I use USB-A to The USB-C cable was used to connect orin to the device, which could not be connected again after first connecting and closing and had to be re-plugged and unplugged, but when I used the Type-c to Type-c cable it worked perfectly.

Then I thought there were two USB-C ports on orin, and I wanted to use both devices at the same time, but I found that Orin could not connect both devices at the same time. Only one ttyACM device was identified in /dev/tty*, which was from above DC Jack Usb-c, the opposite USB-C completely fails, and USB-C port even appears when I plug in the device in a different order Port did not output power supply, I thought it was my device problem, so I tried to connect my phone to Orin, the phone and Ubuntu kept popping out connection and disconnection messages very quickly, so I think it should not be my device problem, because I tested the same conditions on other computers are very normal.

However, when I tried to connect two USB-C cables before orin started up, I could connect both devices at the same time and the transmission was fine, but when I removed the cable and plugged it back in, it was back to where it was before.

3

Hi,
Please share the steps for reproducing the issue. We don’t have your devices but we can try with our devices like USB pendrive or camera.

4

I’m sorry because there are not many types of devices that I can use type-c, but I tried other devices that are easier to get, such as type-c phone devices, usb to TTL using usb-a will also appear similar Happening

  1. Connect two type-c devices to the two type-c connectors on the orin when using the dc jack for power supply
    result: Only the type-c device above the dc jack takes effect

  2. Connect a usb device using tty (uart serial) to USB-A and use software such as cutecom to open and view the serial port, then close the serial port and open it again
    result: cutecom cannot receive any new data, sometimes it will return to normal after closing and reopening

5

I will suggest that for each case, such as the two cases in your latest reply, that you monitor “dmesg --follow” prior to starting. Then, write down what logs show up when you plug in or unplug a cable, and note the type of device, port (such as “front type-A”, “USB-C above barrel jack”, so on), and any details for those log lines.

6
  1. use type-c to type-c cable connect one type-c devices to the type-c connector above barrel jack on the orin when using the dc jack for power supply
    result:
[  181.314404] usb 1-2: new low-speed USB device number 6 using tegra-xusb
[  181.446440] usb 1-2: device descriptor read/64, error -71
[  181.686432] usb 1-2: device descriptor read/64, error -71
[  181.922851] usb 1-2: new low-speed USB device number 7 using tegra-xusb
[  182.050442] usb 1-2: device descriptor read/64, error -71
[  182.286439] usb 1-2: device descriptor read/64, error -71
[  182.394511] usb usb1-port2: attempt power cycle
[  182.806398] usb 1-2: new full-speed USB device number 8 using tegra-xusb
[  182.831009] usb 1-2: New USB device found, idVendor=1546, idProduct=01a9, bcdDevice= 1.00
[  182.831018] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  182.831023] usb 1-2: Product: u-blox GNSS receiver
[  182.831027] usb 1-2: Manufacturer: u-blox AG - www.u-blox.com
[  182.884474] cdc_acm 1-2:1.0: ttyACM0: USB ACM device
[  182.885431] usbcore: registered new interface driver cdc_acm
[  182.885436] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters

and connect any other type-c device to front type-c connecter on the orin,then dmesg did’t show any newline

2.Connect a usb device using USB-A to USB-C cable to the front USB-A on orin

[  935.333796] usb 1-4.4: new full-speed USB device number 9 using tegra-xusb
[  935.449124] usb 1-4.4: New USB device found, idVendor=1546, idProduct=01a9, bcdDevice= 1.00
[  935.449135] usb 1-4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  935.449139] usb 1-4.4: Product: u-blox GNSS receiver
[  935.449142] usb 1-4.4: Manufacturer: u-blox AG - www.u-blox.com
[  935.452491] cdc_acm 1-4.4:1.0: ttyACM0: USB ACM device

open the cutecom to monitor the data coming from usb device(ttyACM0),dmesg did’t show any newline,then stop monitor from cutecom,after that start monitor again,data didn’t coming out any more,and dmesg still did’t show any newline utill i re-plug the device:

[ 1474.503648] usb 1-4.4: USB disconnect, device number 9
[ 1478.309486] usb 1-4.4: new full-speed USB device number 10 using tegra-xusb
[ 1478.389522] usb 1-4.4: device descriptor read/64, error -32
[ 1478.577504] usb 1-4.4: device descriptor read/64, error -32
[ 1478.769453] usb 1-4.4: new full-speed USB device number 11 using tegra-xusb
[ 1478.849528] usb 1-4.4: device descriptor read/64, error -32
[ 1479.037512] usb 1-4.4: device descriptor read/64, error -32
[ 1479.145956] usb 1-4-port4: attempt power cycle
[ 1480.977442] usb 1-4.4: new full-speed USB device number 12 using tegra-xusb
[ 1481.010257] usb 1-4.4: New USB device found, idVendor=1546, idProduct=01a9, bcdDevice= 1.00
[ 1481.010303] usb 1-4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1481.010324] usb 1-4.4: Product: u-blox GNSS receiver
[ 1481.010328] usb 1-4.4: Manufacturer: u-blox AG - www.u-blox.com
[ 1481.012814] cdc_acm 1-4.4:1.0: ttyACM0: USB ACM device

3.when using the dc jack for power supply,connect any device to front USB-C connecter of orin,the dmesg didn’t show any message

7

  • Case 1, USB-C above power connector:
    I don’t know the specific errors shown, but there is likely some sort of error with signal. I do see the “attempt power cycle”, and am wondering if this is power related. Can you try the same “dmesg --follow” experiment with the item plugged into an externally powered HUB, and then the HUB into the USB-C above the power barrel connector?

  • When you mention:

…is this a separate case to one of the other USB-C which you are saying had no response in any log? If so, that’s important. Detecting connect of USB is fundamental. The only exception would be if you connect a device to a micro-OTG port which is designed only for device mode (a device must connect to a host mode port), but that is a special case.

  • Case 2, USB-A to USB-C cable and USB-A on the Jetson:
    This works normally and the device is correctly identified. This is actually the end of the USB role, and what you see regarding loading of cdc_acm driver is the hot plug system loading the driver. This should function and produce file “/dev/ttyACM0”.

Note that if you are using one of your serial UARTs, and not using the one integrated into the Orin, then that port is not set up for serial console. The one which is integrated is a device, and would show up on the remote host when monitoring “dmesg --follow” on the remote host, but not on the Jetson. Note that the cable from NVIDIA for the micro-OTG port is a micro type-B (an OTG port accepts type-A or type-B, but has an ID pin…only the type-B would be active for serial console because the Jetson itself is then a serial UART).

I’ve never actually tried to use the USB-C connector above the power jack for anything other than power. I’m not sure if this works as a USB-C host or not. Someone would have to clarify that…if this is just for power, then I wouldn’t expect a dmesg log when devices are plugged in to it, but I think it probably is a “normal” USB-C connector (not sure).

8

I will try it tomorrow.

What I mean is that when the TYPE-C on the DC connector is not used as the power source, the Type-C interface marked 10 in the Hardware Layout (I call it front TYPE-C) will not respond in the log no matter what device is inserted.
you mentioned that micro-OTG port, But that was not the case with me.

In my case ,because my device which i plug-in to Orin has the serial UART function, so i know it should be show as /dev/ttyACMx,and should be detect well as Case1 shown (even that case has some error but the device which connected and detected was work perfect)

I checked the Hardware Layout in user Guide.it says that the USB-C work in UFP and DFP mode,and front USB-C work in DFP only.

9

I think I will try a simple USB-C SDcard reader for the test, maybe will make things easier, I forgot I don’t have the USB-C hub which has the external power input,

10

I tried connect the USB-C SDcard reader to USB-C above the power barrel connector,and the log shows below:

[  227.442235] usb 1-2: new high-speed USB device number 6 using tegra-xusb
[  227.599889] usb 1-2: New USB device found, idVendor=05e3, idProduct=0749, bcdDevice=15.32
[  227.599899] usb 1-2: New USB device strings: Mfr=3, Product=4, SerialNumber=2
[  227.599903] usb 1-2: Product: USB3.0 Card Reader
[  227.599907] usb 1-2: Manufacturer: Generic
[  227.599910] usb 1-2: SerialNumber: 000000001532
[  227.601501] usb-storage 1-2:1.0: USB Mass Storage device detected
[  227.602569] scsi host0: usb-storage 1-2:1.0
[  228.615692] scsi 0:0:0:0: Direct-Access     Generic  STORAGE DEVICE   1532 PQ: 0 ANSI: 6
[  228.892267] sd 0:0:0:0: [sda] 62333952 512-byte logical blocks: (31.9 GB/29.7 GiB)
[  228.893165] sd 0:0:0:0: [sda] Write Protect is off
[  228.893309] sd 0:0:0:0: [sda] Mode Sense: 21 00 00 00
[  228.893915] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[  228.925260]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 sda14
[  228.928416] sd 0:0:0:0: [sda] Attached SCSI removable disk
[  229.665749] EXT4-fs (sda1): 9 orphan inodes deleted
[  229.665757] EXT4-fs (sda1): recovery complete
[  229.698064] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)

then i remove the SDcard reader ,and try connect to front USB-C ,the log shows below:

[  581.657661] usb 1-1: new high-speed USB device number 7 using tegra-xusb
[  581.811266] usb 1-1: New USB device found, idVendor=05e3, idProduct=0749, bcdDevice=15.32
[  581.811277] usb 1-1: New USB device strings: Mfr=3, Product=4, SerialNumber=2
[  581.811282] usb 1-1: Product: USB3.0 Card Reader
[  581.811292] usb 1-1: Manufacturer: Generic
[  581.811295] usb 1-1: SerialNumber: 000000001532
[  581.812498] usb-storage 1-1:1.0: USB Mass Storage device detected
[  581.812885] scsi host0: usb-storage 1-1:1.0
[  582.831599] scsi 0:0:0:0: Direct-Access     Generic  STORAGE DEVICE   1532 PQ: 0 ANSI: 6
[  583.112839] sd 0:0:0:0: [sda] 62333952 512-byte logical blocks: (31.9 GB/29.7 GiB)
[  583.113668] sd 0:0:0:0: [sda] Write Protect is off
[  583.113814] sd 0:0:0:0: [sda] Mode Sense: 21 00 00 00
[  583.114415] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[  583.159348]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 sda14
[  583.163453] sd 0:0:0:0: [sda] Attached SCSI removable disk
[  583.770148] EXT4-fs (sda1): recovery complete
[  583.771275] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)

It weird because it never connect successfully when using dc barrel before, so I try to connect my USB-C device which couldn’t connect before, then It work,devices are connected with some error but it work normally , I still don’t know what happen to these…

[ 1235.467333] usb 1-1: new low-speed USB device number 26 using tegra-xusb
[ 1235.599406] usb 1-1: device descriptor read/64, error -71
[ 1235.839370] usb 1-1: device descriptor read/64, error -71
[ 1236.075302] usb 1-1: new low-speed USB device number 27 using tegra-xusb
[ 1236.203348] usb 1-1: device descriptor read/64, error -71
[ 1236.439322] usb 1-1: device descriptor read/64, error -71
[ 1236.547410] usb usb1-port1: attempt power cycle
[ 1236.967280] usb 1-1: new full-speed USB device number 28 using tegra-xusb
[ 1236.995691] usb 1-1: New USB device found, idVendor=1546, idProduct=01a9, bcdDevice= 1.00
[ 1236.995695] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1236.995696] usb 1-1: Product: u-blox GNSS receiver
[ 1236.995697] usb 1-1: Manufacturer: u-blox AG - www.u-blox.com
[ 1236.996984] cdc_acm 1-1:1.0: ttyACM0: USB ACM device
[ 1242.922924] usb 1-2: new low-speed USB device number 29 using tegra-xusb
[ 1243.054988] usb 1-2: device descriptor read/64, error -71
[ 1243.294939] usb 1-2: device descriptor read/64, error -71
[ 1243.530891] usb 1-2: new low-speed USB device number 30 using tegra-xusb
[ 1243.662946] usb 1-2: device descriptor read/64, error -71
[ 1243.898885] usb 1-2: device descriptor read/64, error -71
[ 1244.007045] usb usb1-port2: attempt power cycle
[ 1244.434831] usb 1-2: new full-speed USB device number 31 using tegra-xusb
[ 1244.463258] usb 1-2: New USB device found, idVendor=1546, idProduct=01a9, bcdDevice= 1.00
[ 1244.463268] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1244.463270] usb 1-2: Product: u-blox GNSS receiver
[ 1244.463272] usb 1-2: Manufacturer: u-blox AG - www.u-blox.com
[ 1244.464929] cdc_acm 1-2:1.0: ttyACM1: USB ACM device
11

I don’t know what those specific errors are. One theme is that this might be a power issue, but this was the most interesting web search hit:
https://urukrama.wordpress.com/2009/01/27/usb-drive-not-recognised-error-71/
(usbcore is part of the USB driver)

I don’t know if the above will help or not, but it is probably worth a try. On the other hand, I think this would require building the USB core as a module. An easier alternative is to supply this on kernel command line at boot. To do so, edit “/boot/extlinux/extlinux.conf”. Find the “APPEND” key/value parameter, and add this to the end of the line (space delimited):
usbcore.use_both_schemes=1
(this may already be the existing setting, but if it is, then this will do nothing)

12

Hi,
Would like to confirm what the issue is. Now the issue is specific to type-C port above DC jack. If you connect it to a SD card reader, it cannot be detected. Is it the current issue?

13

No, in most cases, the USB-C next to the GPIO is the problem, but in the previous case the SD card reader worked fine no matter which USB-C I was connected to and could be detected, and after that, all my devices worked fine no matter which USB-C I was connected to.

But USB-A still didn’t work, However, I’m not going to deal with USB-A right now.

USB-A doesn’t have any errors in dmesg --follow log, so I have no idea what’s going on.

14

I am very sorry to find that my previous reply was a huge mistake. I pointed out that the USB-C in question was marked as 4 ports in the manual, but I found that I made a mistake and the one in question was marked as 10 in the manual,I will fix it.

16

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.