USB is not recognized after removing the USB HUB from the redo carrier board. What should be changed, DTS? Does the kernel need to be changed? Where is the kernel and DTS downloaded?
Not sure. It all depends on your hardware design.
software guidance (jp5):
https://docs.nvidia.com/jetson/archives/r35.3.1/DeveloperGuide/text/HR/JetsonModuleAdaptationAndBringUp/JetsonXavierNxSeries.html#porting-universal-serial-bus
code download:
I can’t access the download site. Is there any other site
sorry, I just edited the link.
After removing the RTS5489-GR USB HUB on the P3509-0000 carrier board, I used the USB1 port to connect the mouse through an OTG connector, indicating that the USB enumeration failed. How should I solve this problem? Should I change anything?
jetcon@jetcon:~$ lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=tegra-xusb/4p, 10000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=tegra-xusb/4p, 480M
jetcon@jetcon:~$
jetcon@jetcon:~$
jetcon@jetcon:~$
jetcon@jetcon:~$
jetcon@jetcon:~$ [ 523.620931] usb 1-2: Device not responding to setup address.
[ 523.828727] usb 1-2: Device not responding to setup address.
[ 524.036426] usb 1-2: device not accepting address 6, error -71
[ 524.156869] usb 1-2: Device not responding to setup address.
[ 524.364817] usb 1-2: Device not responding to setup address.
[ 524.572393] usb 1-2: device not accepting address 7, error -71
[ 525.128538] usb 1-2: device descriptor read/64, error -71
[ 525.356587] usb 1-2: device descriptor read/64, error -71
[ 525.704572] usb 1-2: device descriptor read/64, error -71
[ 525.932538] usb 1-2: device descriptor read/64, error -71
[ 526.040552] usb usb1-port2: unable to enumerate USB device
yes you should refer to the document and modify the device tree to match your hardware.
Is there any documentation on this issue? I refer to etson Module Adaptation and Bring-Up: Jetson Xavier NX Series, but I can’t find anything about this problem
There is also a problem, we are using P3668-0000 SOM, just remove the USB HUB on the carrier board, normally should not change the things in the device tree? Do you want to change something about the kernel or the driver?
If you just removed the usb hub, then why do USB1 became a OTG port?
I was using a type-C socket on my pad, so I used a USB-to-Type-C OTG adapter to connect my USB mouse (or other drive-free device) to the jeston, but the USB enumeration failed, Compared with the USB1 part of my carrier board, the USB HUB is only removed from the P5489-3509.
Hi,
Sorry that I have no idea about what you are talking about. So what is the port in use to connect mouse on the carrier board side?
If you changed anything on the carrier board, then you must change the device tree according to the document. Even adding a type C port requires to make device tree change.
Please be aware that our document is not something like “oh I saw -71 error, what should i do” " I saw usb xxx error, what should I do". We are just programming the device tree to match the board design.
-71 could indicate signal quality issue too.
Also, I have seen lots of users talking about “my board is same as devkit except xxx”. Turns out their board is not same at all. So if you want us to help, clarify all the usb port design on your board .
I removed the USB HUB on the P3509-0000 that connects the USB1 to the USBSS, replaced the USB socket on the USB1 to the USBSS with a type-C socket, and then connected my mouse with a removable USB-to-Type-C OTG converter.
What does that mean connects USB1 to the USBSS? pin 161/163/166/168?
How does it tell which side should be used on your type C if there is no type C controller?
Have you tried to flip back your cable and test?
将USBSS(161 163 166 168)与USB1(115 117)一起接在type-C上，因为焊接上去的，所以没办法调换方向测试
Should I change the mode attribute of the usb node in DTS to OTG instead of host
No need. Your usecase is pure host mode. I guess your design is pure host mode too.
Without the schematic, I am not sure.
This is my schematic
microplane_nx.pdf (926.5 KB)
Hi,
please try to follow the design guide document of AGX Xavier or Orin to design a type C port. We don’t guarantee your design would work fine.