The carrier board we designed has two USB channels routed directly from the chip to the connector, namely USB0 and USB1, with only ESD protection added in between. Currently, USB0 is functioning normally, but USB1 is not working. Are there any enable configurations in the software that need to be checked?
*** Please note that this reply is generated by LLM automatically ***
Based on the provided context, I’ll try to help you troubleshoot the issue with USB1 not working on your custom carrier board.
Firstly, it’s great that you’ve confirmed USB0 is functioning normally, which suggests that the basic USB functionality is working on your board.
To troubleshoot USB1, let’s break down the possible causes:
- Hardware issues: Since you’ve mentioned that only ESD protection is added between the chip and the connector, it’s possible that there’s a hardware issue with the USB1 channel. Double-check the routing, connections, and component values to ensure they match the recommended values in the Jetson AGX Orin documentation.
- Software configuration: Yes, there are software configurations that need to be checked. The Jetson AGX Orin series uses a Linux-based operating system, and USB configuration is typically managed through the Linux kernel and device tree.
To investigate software configuration issues, you can try the following:
a. Check the device tree: Verify that the device tree (DT) configuration for USB1 is correct. You can check the DT files in the Linux kernel source tree or use tools like dtc to decompile the DT binary.
b. Kernel configuration: Ensure that the Linux kernel is configured to support USB1. Check the kernel configuration file (config) for options related to USB, such as CONFIG_USB_XHCI_HCD, CONFIG_USB_EHCI_HCD, or CONFIG_USB_OHCI_HCD.
c. USB driver: Verify that the USB driver is loaded and configured correctly for USB1. You can check the kernel logs (dmesg) for USB-related messages or use tools like lsusb to enumerate USB devices.
d. Pinmux configuration: The Jetson AGX Orin series uses a pinmux controller to configure the pin functions. Ensure that the pinmux configuration for USB1 is correct. You can check the pinmux configuration using tools like pinmux or gpio.
To help you further, I’d like to ask a few questions:
- Have you checked the kernel logs (
dmesg) for any USB-related error messages? - Have you verified the device tree configuration for USB1?
- Are there any differences in the hardware design or component values between USB0 and USB1?
Please provide more information about your setup, and I’ll do my best to help you troubleshoot the issue with USB1.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
Hi 877690771,
What’s the Jetpack version in use?
Please share the results of the following commands on your board.
$ cat /etc/nv_boot_control.conf
$ cat /etc/nv_tegra_release
Do you mean the issue is about C10(USB1_N), C11(USB1_P)?
cmd result:R35 (release), REVISION: 4.1, GCID: 33958178, BOARD: t186ref, EABI: aarch64, DATE: Tue Aug 1 19:57:35 UTC 2023
Yes, USB1 is not functioning properly. USB0 can recognize devices, but USB1 fails to do so.
Could you refer to Porting the Universal Serial Bus to port USB according to your design on custom carrier board?
r35.4.1 is a bit old release. Could you also verify with the latest Jetpack 5.1.5(r35.6.2) or Jetpack 6.1.2(r36.4.4)?
I believe this issue is unrelated to the JetPack version. We have another carrier board where both USB ports function normally, as you can see, the system has successfully detected both the mouse and keyboard.Both carrier boards are using the same Orin module (SoM)
The dmesg logs are provided below:
[ 0.423605] vbusB-cvb: supplied by vdd-5v-sys
[ 0.423722] vdd-usbc1-vbus: supplied by vdd-5v-sys
[ 0.423821] vdd-usbc2-vbus: supplied by vdd-5v-sys
[ 0.424400] usbcore: registered new interface driver usbfs
[ 0.424414] usbcore: registered new interface driver hub
[ 0.424437] usbcore: registered new device driver usb
[ 5.287820] usbcore: registered new interface driver r8152
[ 5.293153] usbcore: registered new interface driver asix
[ 5.298484] usbcore: registered new interface driver ax88179_178a
[ 5.304603] usbcore: registered new interface driver cdc_ether
[ 5.310560] usbcore: registered new interface driver net1080
[ 5.316157] usbcore: registered new interface driver cdc_subset
[ 5.322194] usbcore: registered new interface driver zaurus
[ 5.327887] usbcore: registered new interface driver cdc_ncm
[ 5.333566] usbcore: registered new interface driver qmi_wwan
[ 5.338995] usbcore: registered new interface driver aqc111
[ 5.344870] ohci_hcd: USB 1.1 ‘Open’ Host Controller (OHCI) Driver
[ 5.360727] tegra-xusb 3610000.xhci: Adding to iommu group 0
[ 5.366528] usbcore: registered new interface driver cdc_wdm
[ 5.371778] usbcore: registered new interface driver uas
[ 5.377066] usbcore: registered new interface driver usb-storage
[ 5.383030] usbcore: registered new interface driver option
[ 5.388695] usbserial: USB Serial support registered for GSM modem (1-port)
[ 5.395608] usbcore: registered new interface driver qcserial
[ 5.401289] usbserial: USB Serial support registered for Qualcomm USB modem
[ 5.419690] usbcore: registered new interface driver xpad
[ 6.797716] usbcore: registered new interface driver usbhid
[ 6.798251] usbhid: USB HID core driver
[ 6.988115] usbcore: registered new interface driver snd-usb-audio
[ 8.034022] tegra-xusb 3610000.xhci: Firmware timestamp: 2021-12-01 05:27:10 UTC, Version: 80.03 release
[ 8.034804] tegra-xusb 3610000.xhci: xHCI Host Controller
[ 8.035495] tegra-xusb 3610000.xhci: new USB bus registered, assigned bus number 1
[ 8.039784] tegra-xusb 3610000.xhci: hcc params 0x0180ff05 hci version 0x120 quirks 0x0000000000050810
[ 8.048416] tegra-xusb 3610000.xhci: irq 239, io mem 0x03610000
[ 8.054642] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[ 8.062654] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 8.069823] usb usb1: Product: xHCI Host Controller
[ 8.074823] usb usb1: Manufacturer: Linux 5.10.104-tegra xhci-hcd
[ 8.081112] usb usb1: SerialNumber: 3610000.xhci
[ 8.086189] hub 1-0:1.0: USB hub found
[ 8.093880] tegra-xusb 3610000.xhci: xHCI Host Controller
[ 8.099060] tegra-xusb 3610000.xhci: new USB bus registered, assigned bus number 2
[ 8.106672] tegra-xusb 3610000.xhci: Host supports USB 3.1 Enhanced SuperSpeed
[ 8.114083] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.10
[ 8.122245] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 8.129498] usb usb2: Product: xHCI Host Controller
[ 8.134485] usb usb2: Manufacturer: Linux 5.10.104-tegra xhci-hcd
[ 8.140695] usb usb2: SerialNumber: 3610000.xhci
[ 8.145852] hub 2-0:1.0: USB hub found
[ 10.662404] tegra-xusb 3610000.xhci: entering ELPG done
[ 12.886255] tegra-xusb 3610000.xhci: Firmware timestamp: 2021-12-01 05:27:10 UTC, Version: 80.03 release
[ 13.285443] usb 2-2: new SuperSpeed Gen 1 USB device number 2 using tegra-xusb
[ 13.309299] usb 2-2: New USB device found, idVendor=0451, idProduct=8240, bcdDevice= 1.10
[ 13.309869] usb 2-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 13.314312] hub 2-2:1.0: USB hub found
[ 13.432987] usb 1-4: new high-speed USB device number 2 using tegra-xusb
[ 13.585545] usb 1-4: New USB device found, idVendor=0451, idProduct=8242, bcdDevice= 1.00
[ 13.586100] usb 1-4: New USB device strings: Mfr=0, Product=0, SerialNumber=1
[ 13.586621] usb 1-4: SerialNumber: 83030841833B
[ 13.587938] hub 1-4:1.0: USB hub found
[ 13.885182] usb 1-4.3: new full-speed USB device number 3 using tegra-xusb
[ 13.886747] usb 1-4: clear tt 3 (8000) error -71
[ 13.887246] usb 1-4: USB disconnect, device number 2
[ 13.888199] usb 1-4-port3: attempt power cycle
[ 14.102111] usb 2-2: Disable of device-initiated U1 failed.
[ 14.103857] usb 2-2: Disable of device-initiated U2 failed.
[ 14.229691] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using tegra-xusb
[ 14.524988] usb 1-4: new high-speed USB device number 7 using tegra-xusb
[ 14.681544] usb 1-4: New USB device found, idVendor=0451, idProduct=8242, bcdDevice= 1.00
[ 14.682141] usb 1-4: New USB device strings: Mfr=0, Product=0, SerialNumber=1
[ 14.682716] usb 1-4: SerialNumber: 83030841833B
[ 14.684062] hub 1-4:1.0: USB hub found
[ 14.977114] usb 1-4.3: new full-speed USB device number 8 using tegra-xusb
[ 15.089169] usb 1-4.3: New USB device found, idVendor=046d, idProduct=c08e, bcdDevice=40.00
[ 15.089820] usb 1-4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 15.090422] usb 1-4.3: Product: MX518 Gaming Mouse
[ 15.090946] usb 1-4.3: Manufacturer: Logitech
[ 15.091452] usb 1-4.3: SerialNumber: 1963395D3836
[ 15.099196] input: Logitech MX518 Gaming Mouse as /devices/platform/3610000.xhci/usb1/1-4/1-4.3/1-4.3:1.0/0003:046D:C08E.0001/input/input1
[ 15.101007] hid-generic 0003:046D:C08E.0001: input,hidraw0: USB HID v1.11 Mouse [Logitech MX518 Gaming Mouse] on usb-3610000.xhci-4.3/input0
[ 15.106347] input: Logitech MX518 Gaming Mouse Keyboard as /devices/platform/3610000.xhci/usb1/1-4/1-4.3/1-4.3:1.1/0003:046D:C08E.0002/input/input2
[ 15.165215] input: Logitech MX518 Gaming Mouse Consumer Control as /devices/platform/3610000.xhci/usb1/1-4/1-4.3/1-4.3:1.1/0003:046D:C08E.0002/input/input3
[ 15.166775] input: Logitech MX518 Gaming Mouse System Control as /devices/platform/3610000.xhci/usb1/1-4/1-4.3/1-4.3:1.1/0003:046D:C08E.0002/input/input4
[ 15.168585] hid-generic 0003:046D:C08E.0002: input,hiddev96,hidraw1: USB HID v1.11 Keyboard [Logitech MX518 Gaming Mouse] on usb-3610000.xhci-4.3/input1
[ 15.249108] usb 1-4.4: new low-speed USB device number 9 using tegra-xusb
[ 15.361942] usb 1-4.4: New USB device found, idVendor=04f3, idProduct=0103, bcdDevice= 1.07
[ 15.362857] usb 1-4.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 15.369981] input: HID 04f3:0103 as /devices/platform/3610000.xhci/usb1/1-4/1-4.4/1-4.4:1.0/0003:04F3:0103.0003/input/input7
[ 15.370983] hid-generic 0003:04F3:0103.0003: input,hidraw2: USB HID v1.11 Keyboard [HID 04f3:0103] on usb-3610000.xhci-4.4/input0
[ 15.376705] input: HID 04f3:0103 Consumer Control as /devices/platform/3610000.xhci/usb1/1-4/1-4.4/1-4.4:1.1/0003:04F3:0103.0004/input/input8
[ 15.378454] input: HID 04f3:0103 System Control as /devices/platform/3610000.xhci/usb1/1-4/1-4.4/1-4.4:1.1/0003:04F3:0103.0004/input/input9
[ 15.380222] hid-generic 0003:04F3:0103.0004: input,hidraw3: USB HID v1.11 Device [HID 04f3:0103] on usb-3610000.xhci-4.4/input1
[ 16.784082] usb0: HOST MAC b2:9a:a4:ee:cb:82
[ 16.784086] usb0: MAC b2:9a:a4:ee:cb:83
[ 16.791986] l4tbr0: port 2(usb0) entered blocking state
[ 16.791996] l4tbr0: port 2(usb0) entered disabled state
[ 16.792091] device usb0 entered promiscuous mode
For the carrier board with one faulty USB port, the dmesg logs are as follows:
[ 0.423543] vbusB-cvb: supplied by vdd-5v-sys
[ 0.423660] vdd-usbc1-vbus: supplied by vdd-5v-sys
[ 0.423759] vdd-usbc2-vbus: supplied by vdd-5v-sys
[ 0.424346] usbcore: registered new interface driver usbfs
[ 0.424362] usbcore: registered new interface driver hub
[ 0.424377] usbcore: registered new device driver usb
[ 5.249014] usbcore: registered new interface driver r8152
[ 5.254337] usbcore: registered new interface driver asix
[ 5.259675] usbcore: registered new interface driver ax88179_178a
[ 5.265793] usbcore: registered new interface driver cdc_ether
[ 5.271745] usbcore: registered new interface driver net1080
[ 5.277344] usbcore: registered new interface driver cdc_subset
[ 5.283381] usbcore: registered new interface driver zaurus
[ 5.289075] usbcore: registered new interface driver cdc_ncm
[ 5.294758] usbcore: registered new interface driver qmi_wwan
[ 5.300184] usbcore: registered new interface driver aqc111
[ 5.306061] ohci_hcd: USB 1.1 ‘Open’ Host Controller (OHCI) Driver
[ 5.321917] tegra-xusb 3610000.xhci: Adding to iommu group 0
[ 5.327708] usbcore: registered new interface driver cdc_wdm
[ 5.332959] usbcore: registered new interface driver uas
[ 5.338254] usbcore: registered new interface driver usb-storage
[ 5.344220] usbcore: registered new interface driver option
[ 5.349880] usbserial: USB Serial support registered for GSM modem (1-port)
[ 5.356795] usbcore: registered new interface driver qcserial
[ 5.362478] usbserial: USB Serial support registered for Qualcomm USB modem
[ 5.380871] usbcore: registered new interface driver xpad
[ 6.766145] usbcore: registered new interface driver usbhid
[ 6.766305] usbhid: USB HID core driver
[ 6.954970] usbcore: registered new interface driver snd-usb-audio
[ 8.001827] tegra-xusb 3610000.xhci: Firmware timestamp: 2021-12-01 05:27:10 UTC, Version: 80.03 release
[ 8.002100] tegra-xusb 3610000.xhci: xHCI Host Controller
[ 8.002282] tegra-xusb 3610000.xhci: new USB bus registered, assigned bus number 1
[ 8.008119] tegra-xusb 3610000.xhci: hcc params 0x0180ff05 hci version 0x120 quirks 0x0000000000050810
[ 8.016725] tegra-xusb 3610000.xhci: irq 239, io mem 0x03610000
[ 8.022891] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[ 8.030962] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 8.038137] usb usb1: Product: xHCI Host Controller
[ 8.043116] usb usb1: Manufacturer: Linux 5.10.104-tegra xhci-hcd
[ 8.049418] usb usb1: SerialNumber: 3610000.xhci
[ 8.055150] hub 1-0:1.0: USB hub found
[ 8.062264] tegra-xusb 3610000.xhci: xHCI Host Controller
[ 8.067368] tegra-xusb 3610000.xhci: new USB bus registered, assigned bus number 2
[ 8.074978] tegra-xusb 3610000.xhci: Host supports USB 3.1 Enhanced SuperSpeed
[ 8.082421] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.10
[ 8.090554] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 8.097819] usb usb2: Product: xHCI Host Controller
[ 8.102795] usb usb2: Manufacturer: Linux 5.10.104-tegra xhci-hcd
[ 8.109003] usb usb2: SerialNumber: 3610000.xhci
[ 8.114244] hub 2-0:1.0: USB hub found
[ 8.319960] usb 1-2: new full-speed USB device number 2 using tegra-xusb
[ 8.474100] usb 1-2: New USB device found, idVendor=046d, idProduct=c08e, bcdDevice=40.00
[ 8.474343] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 8.474553] usb 1-2: Product: MX518 Gaming Mouse
[ 8.474691] usb 1-2: Manufacturer: Logitech
[ 8.474807] usb 1-2: SerialNumber: 1963395D3836
[ 8.480284] input: Logitech MX518 Gaming Mouse as /devices/platform/3610000.xhci/usb1/1-2/1-2:1.0/0003:046D:C08E.0001/input/input0
[ 8.481627] hid-generic 0003:046D:C08E.0001: input,hidraw0: USB HID v1.11 Mouse [Logitech MX518 Gaming Mouse] on usb-3610000.xhci-2/input0
[ 8.483911] input: Logitech MX518 Gaming Mouse Keyboard as /devices/platform/3610000.xhci/usb1/1-2/1-2:1.1/0003:046D:C08E.0002/input/input1
[ 8.544504] input: Logitech MX518 Gaming Mouse Consumer Control as /devices/platform/3610000.xhci/usb1/1-2/1-2:1.1/0003:046D:C08E.0002/input/input2
[ 8.545122] input: Logitech MX518 Gaming Mouse System Control as /devices/platform/3610000.xhci/usb1/1-2/1-2:1.1/0003:046D:C08E.0002/input/input3
[ 8.546044] hid-generic 0003:046D:C08E.0002: input,hiddev96,hidraw1: USB HID v1.11 Keyboard [Logitech MX518 Gaming Mouse] on usb-3610000.xhci-2/input1
[ 16.400025] usb0: HOST MAC b2:9a:a4:ee:cb:82
[ 16.400028] usb0: MAC b2:9a:a4:ee:cb:83
[ 16.407763] l4tbr0: port 2(usb0) entered blocking state
[ 16.407774] l4tbr0: port 2(usb0) entered disabled state
[ 16.407893] device usb0 entered promiscuous mode
Please check if the fault follows the carrier board. If carrier board, you will need to debug what could be causing this issue on that particular carrier board. Please check with the design guide and ensure you meet the requirements for USB2 routing. Check correct ESD protection is used and it is not affecting the signal integrity on these differential pairs.
1 Like
To enable the native USB interfaces directly connected to the Orin chip, what mandatory configurations must be defined in the device tree or software drivers?
Is this still an issue to support? Any result can be shared?
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.