AGX Orin USB Issue Custom Carrier Jetpack 6

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

Hello, I’ve been developing the AGX Orin 64GB using a custom carrier board and have run into issues getting USB working.

When running lsusb nothing appears. I’ve tried many different USB devices and I have used this carrier board with Jetpack 5.1.2 and had no issues with USB. There appears to be some changes in the device tree that could have something to do with this.

Notes:
I have only tested USB3 (USB2_3 on schematics, pins G10 and G11).

I do not have EEPROM on my carrier board so I made the following modification to tegra234-mb2-bct-common.dtsi so the Orin doesn’t go into a busy spin.

- cvb_eeprom_read_size = <0x100>
+ cvb_eeprom_read_size = <0x0>

I also do not have the GB phy so I made the following modification to p3701.conf.common

-ODMDATA="gbe-uphy-config-22,hsstp-lane-map-3,nvhs-uphy-config-0,hsio-uphy-config-0,gbe0-enable-10g";
+ODMDATA="gbe-uphy-config-0,hsstp-lane-map-3,nvhs-uphy-config-0,hsio-uphy-config-0";

I do not think these changes are related to the problem because when I plug the module into the old carrier board USB seems to work fine.

Here is the output of “dmesg | grep usb” when plugged into my custom carrier board:

[    0.172340] usbcore: registered new interface driver usbfs
[    0.172365] usbcore: registered new interface driver hub
[    0.172384] usbcore: registered new device driver usb
[    0.303628] usbcore: registered new interface driver usb-storage
[    4.013403] usbcore: registered new interface driver usbhid
[    4.013408] usbhid: USB HID core driver
[    4.080501] usbcore: registered new interface driver snd-usb-audio

Here is the output when plugged into the official carrier board:

[    0.172443] usbcore: registered new interface driver usbfs
[    0.172470] usbcore: registered new interface driver hub
[    0.172489] usbcore: registered new device driver usb
[    0.302756] usbcore: registered new interface driver usb-storage
[    4.084527] usbcore: registered new interface driver usbhid
[    4.084533] usbhid: USB HID core driver
[    4.151215] usbcore: registered new interface driver snd-usb-audio
[   15.226116] tegra-xusb 3610000.usb: Adding to iommu group 55
[   15.251851] tegra-xusb 3610000.usb: Firmware timestamp: 2023-02-10 03:48:10 UTC
[   15.251867] tegra-xusb 3610000.usb: xHCI Host Controller
[   15.251892] tegra-xusb 3610000.usb: new USB bus registered, assigned bus number 1
[   15.252647] tegra-xusb 3610000.usb: hcc params 0x0180ff05 hci version 0x120 quirks 0x0000000000010810
[   15.252681] tegra-xusb 3610000.usb: irq 125, io mem 0x03610000
[   15.252848] tegra-xusb 3610000.usb: xHCI Host Controller
[   15.252852] tegra-xusb 3610000.usb: new USB bus registered, assigned bus number 2
[   15.252857] tegra-xusb 3610000.usb: Host supports USB 3.1 Enhanced SuperSpeed
[   15.270759] tegra-xudc 3550000.usb: Adding to iommu group 56
........ keeps going

There must be some with the Tegra xHCI controller preventing these interfaces from working.

I would appreciate any help!

3

What you are sharing is not the key point to check.

The key point here is what usb design you are using on your custom board.

Did you modify any device tree change in kernel to make the usb work on rel-35?
And did you make similar thing on rel-36?

4

My custom board does not use the RTS5420 USB hub controller like in the reference schematics. Instead that USB is connected directly to a USB C receptacle.

I did not need to make any device tree modifications to make the USB work on L4T 35.4.1.

5

Then your usb setting on rel-35 was also wrong. It is common situation that user may think “my usb device works, so my software is definitely correct”. But it does not… it is just luck. When it goes to rel-36, it comes to dead result.

You should share your schematic and what usb C controller you are using so that we can guide you to modify device tree…

6

I’m not using any USB C PD or hub controller, but here is the schematic.

image (1)
image (1)1585×636 60 KB

7

What is the usb2 pin in use on your type C?

8

Are you talking about the blue “USB1” and “USB2” symbols? Those are just harnesses that go to different schematic sheets, right now they are not actually connected to anything. Sorry I’m a little confused about your question.

Either way I was able to modify the device tree and get the USB working. My custom carrier does not have the CYPD4226 so the driver was failing to probe.

10

Are you talking about you have no further question to ask here?

11

or you are talking about there is only usb2 pin connection to your type C port and your type C port does not support USBSS?

13

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