USB0 is not working as device mode on Orin NX custom carrier board(JP 5.1.2)

[592803276]

Dear nvidia team:

If our orin nx custom carrier board is not connected to any other USB devices, just connect to the TYPE-C flashing port, the computer cannot recognize our device after system startup.If you insert another USB device into another usb TYPE-A port at this time, such as a keyboard, mouse, flash drive, etc., the TYPE-C port will work normally. This problem does not exist on the JP5.1.1 ORIN NX, but only on the JP5.1.2, please help analyze and provide a solution.

dmesg log:
root@tegra-ubuntu:/home/admin# dmesg | grep usb
[ 1.588166] usbcore: registered new interface driver usbfs
[ 1.593659] usbcore: registered new interface driver hub
[ 1.598977] usbcore: registered new device driver usb
[ 4.314799] usbcore: registered new interface driver r8152
[ 4.320431] usbcore: registered new interface driver asix
[ 4.325980] usbcore: registered new interface driver ax88179_178a
[ 4.332227] usbcore: registered new interface driver cdc_ether
[ 4.338217] usbcore: registered new interface driver net1080
[ 4.344021] usbcore: registered new interface driver cdc_subset
[ 4.350092] usbcore: registered new interface driver zaurus
[ 4.355830] usbcore: registered new interface driver cdc_ncm
[ 4.361635] usbcore: registered new interface driver qmi_wwan_q
[ 4.367712] usbcore: registered new interface driver qmi_wwan
[ 4.373603] usbcore: registered new interface driver aqc111
[ 4.396014] tegra-xusb 3610000.xhci: Adding to iommu group 0
[ 4.402370] usbcore: registered new interface driver cdc_wdm
[ 4.408232] usbcore: registered new interface driver uas
[ 4.413696] usbcore: registered new interface driver usb-storage
[ 4.431829] usbcore: registered new interface driver xpad
[ 5.699177] usbcore: registered new interface driver usbhid
[ 5.704908] usbhid: USB HID core driver
[ 6.119333] usbcore: registered new interface driver snd-usb-audio
[ 7.456462] tegra-xusb 3610000.xhci: Firmware timestamp: 2023-02-10 03:48:10 UTC, Version: 80.05 release
[ 7.466218] tegra-xusb 3610000.xhci: xHCI Host Controller
[ 7.471789] tegra-xusb 3610000.xhci: new USB bus registered, assigned bus number 1
[ 7.480466] tegra-xusb 3610000.xhci: hcc params 0x0180ff05 hci version 0x120 quirks 0x0000000000050810
[ 7.490072] tegra-xusb 3610000.xhci: irq 232, io mem 0x03610000
[ 7.496515] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[ 7.505021] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 7.512457] usb usb1: Product: xHCI Host Controller
[ 7.517472] usb usb1: Manufacturer: Linux 5.10.120-tegra xhci-hcd
[ 7.523748] usb usb1: SerialNumber: 3610000.xhci
[ 7.537621] tegra-xusb 3610000.xhci: xHCI Host Controller
[ 7.543192] tegra-xusb 3610000.xhci: new USB bus registered, assigned bus number 2
[ 7.550987] tegra-xusb 3610000.xhci: Host supports USB 3.1 Enhanced SuperSpeed
[ 7.558529] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.10
[ 7.567038] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 7.574473] usb usb2: Product: xHCI Host Controller
[ 7.579494] usb usb2: Manufacturer: Linux 5.10.120-tegra xhci-hcd
[ 7.585764] usb usb2: SerialNumber: 3610000.xhci
[ 7.809392] usb 1-2: new high-speed USB device number 2 using tegra-xusb
[ 7.978501] usb 1-2: New USB device found, idVendor=0bda, idProduct=5411, bcdDevice= 1.16
[ 7.986922] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 7.994272] usb 1-2: Product: USB2.1 Hub
[ 7.998296] usb 1-2: Manufacturer: Generic
[ 8.098364] usb 2-3: new SuperSpeed Gen 1 USB device number 2 using tegra-xusb
[ 8.137077] usb 2-3: New USB device found, idVendor=0bda, idProduct=0411, bcdDevice= 1.16
[ 8.145492] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 8.152844] usb 2-3: Product: USB3.2 Hub
[ 8.156869] usb 2-3: Manufacturer: Generic
[ 9.823492] tegra-xusb 3610000.xhci: entering ELPG done
[ 16.417568] usb0: HOST MAC ee:bf:ad:74:b5:2e
[ 16.417575] usb0: MAC ee:bf:ad:74:b5:2f
[ 16.433139] l4tbr0: port 2(usb0) entered blocking state
[ 16.434139] l4tbr0: port 2(usb0) entered disabled state
[ 16.434242] device usb0 entered promiscuous mode
root@tegra-ubuntu:/home/admin#

[WayneWWW]

Since this is custom board, did you ever configure the device tree to match your board design?

[592803276]

Yes, all other functions are normal except for this function.By comparing the differences between JP5.1.1 and JP5.1.2 in USB device tree, I find that there is no difference, but JP5.1.1 is normal on the same customer board.

[WayneWWW]

Hi,

usb這種東西是很容易 "運氣好"會能動的
如果你用custom board但是你從來都沒有用過正確的device tree設定. 然後你的usb能使用, 這可能只是巧合讓你能夠執行…

你拿一個錯的東西一直執行之後有天忽然不能動了, 正常要做的事情應該是去改你那個一直錯到底的device tree…

---

It seems a common mistake from lots of end users… It is actually very easy to get usb work “by coincidence”.
If your custom board never had the correct usb device tree to match your board design and your usb can work fine, then it could be just your luck…

Now this thing does not work anymore. A correct way should be you need to modify the totally wrong device tree…

[592803276]

I don’t accept your argument. It’s always OK on the JP5.1.1 customer board, and we’ve been using it all the time. There is a problem with using JP5.1.2, there is no mistake, and the USB device tree has been changed to the same as JP5.1.1.Please help to analyze what’s the difference.

[DaneLLL]

Hi,
For custom board please execute compliance test. The signal quality may not be good, triggering the issue.

[592803276]

But the problem is that when I plug a device into another USB port after startup, the USB0 type-c port will works normally.

[DaneLLL]

Hi,
From the description it looks like device tree doesn’t match the custom board. If you have different design when comparing to developer kit, please refer to adaptation guide to modify device tree accordingly. It seems like VBUS pin may not correctly match with the USB port in device tree.

And once the device tree is ready, please do compliance test to ensure signal quality is good.

[592803276]

Hi DaneLLL:
Thank you for you answer
The following is the dts modification：

How to debug this problem?Can you provide some ideas?

[WayneWWW]

Please refer to the document.

https://docs.nvidia.com/jetson/archives/r35.5.0/DeveloperGuide/HR/JetsonModuleAdaptationAndBringUp/JetsonAgxOrinSeries.html?highlight=porting#porting-the-universal-serial-bus

There is no direct answer to your question because we don’t know your carrier board design.