thiruusb.txt (175.6 KB)
This i attached dts file with thiru name.
usb2-1 is working but usb3-0 is not working.i could not find the issue.
Hi,
If you are designing a custom base board, then it means some adaptation configurations are needed.
Otherwise, your board may not work fine.
For Orin AGX series, you could refer to below document
https://docs.nvidia.com/jetson/archives/r36.3/DeveloperGuide/HR/JetsonModuleAdaptationAndBringUp/JetsonAgxOrinSeries.html?highlight=universal%20serial%20bus#jetson-agx-orin-platform-adaptation-and-bring-up
(please be aware that above link is for rel-36.3/jetpack6.0)
This document includes below configuration
- pinmux change & GPIO configuration
- EEPROM change as most custom boards do not have an EEPROM on it.
- Kernel porting
- PCIe configuration
- USB configuration
- MGBE configuration
- RGMII configuration
Thanks!
board is working,usb2-0 and usb3-1 is working.
usb2-1 is working but usb3-0 is not working.
In padctl@3520000 node i did this.
usb2-0 {
mode = “otg”;
usb-role-switch;
status = “okay”;
};
usb3-1 {
nvidia,usb2-companion = <0>;
status = “okay”;
};
usb@3610000 {
status = “okay”;
phys = <&{/bus@0/padctl@3520000/pads/usb2/lanes/usb2-0}>,
<&{/bus@0/padctl@3520000/pads/usb2/lanes/usb2-1}>,
<&{/bus@0/padctl@3520000/pads/usb2/lanes/usb2-2}>,
<&{/bus@0/padctl@3520000/pads/usb2/lanes/usb2-3}>,
<&{/bus@0/padctl@3520000/pads/usb3/lanes/usb3-0}>,
<&{/bus@0/padctl@3520000/pads/usb3/lanes/usb3-1}>,
<&{/bus@0/padctl@3520000/pads/usb3/lanes/usb3-2}>;
phy-names = "usb2-0", "usb2-1", "usb2-2", "usb2-3",
"usb3-0", "usb3-1", "usb3-2";
};
dmesg log.docx (5.1 KB)
Here i attached the dmesg log
As your usb3-0+ usb2-1 are connected to a hub, please directly contact the hub vendor.
As your usb3-0+ usb2-1 are connected to usb type a connector we removed the hub now.
i did the companion usb2-1 with usb3-0
UPHY_RX0_P
UPHY_RX0_N
UPHY_TX0_P
UPHY_TX0_N
this line are using for usb3-0
USB1_P
USB1_N
this line used for usb2, to access the usb3.0 pendrive ,
I can able to access the usb2 but unable access the usb3
I per my knowledge i change by following adaption document.
Please confirm me my dts file is correct or not.
thiruusb.txt
(175.6 KB)
file name is thiruusb.txt alias( tegra234-p3737-0000+p3701-0000.dtb)
The device tree for that part looks correct. You should check with hub vendor of for more detail.
thank you for confirmation whyneWWW.
Can you please confirm we are using universal hub should work with usb2.0 if usb3.0 is not working.
Hi wayneWWW thanks you for your help. there is hardware issue that why i am unable to communicate with hub.i issue resolved my microchip people.
one small clarification i need from you,
the usb2-2 D+and D- are connected hub in hardware. USB2 is working good but usb3 is not working why.
But in evk_board this pins are connected to M.2 E usb2. i need to change in pinmux or not required to change it.
No, it is not needed.
usb2-2 for usb2
UPHY_RX20_P for usb 3
UPHY_RX20_N for usb3
UPHY_TX20_P for usb3
UPHY_TX20_N for usb3
above usb2 d+and d- lines and uphy20 lines are connected to microchip hub,
In dts file i did nvidia,usb2-companion = <2> this instead of nvidia,usb2-companion = <3>;
My dts file is correct i think,correct we if i am wrong.
usb2-2 {
mode = “host”;
status = “okay”;
};
usb3-2 {
nvidia,usb2-companion = <2>;
status = “okay”;
};
@WayneWWW can you confirm once i will look towards hardware any changes are required.
Just to clarify. This simple thing won’t help here.
Only you know your hardware status. I don’t know you or your board.
If you just gave me such connection and such simple device tree, then there is nothing I can say. I feel it is correct. But why usb3 is not working is not what I can check on my side. You need to check with your hardware team.
In hub2 is connected to usb2-1 and
UPHY_RX0_P
UPHY_RX0_N
UPHY_TX0_P
UPHY_TX0_N
this usb3 companion with usb2 in my dts but in evk board for usb2-1 lines are conected to M.2E.
Is this will not affect the usb3 functionality usb2 is detecting.
usb3 hub is not detecting.
It will not affect.
then as per dts file hub2 should work.similar to hub1.
thanks you @WayneWWW i will check toward hardware.
i kept in dts file mode = “host” and i removed Mode=“OTG”
Thank you soo much @WayneWWW for you great support.
@WayneWWW thank you soo much, there is issue in microchip hub it is confirmed.
@WayneWWW can you clarify one think i am using usb2-0 (F13,F12) and usb3-1 for typeA connector.
Can use it for flashing by keep mode = “peripheral”.
flashing is working we done force recovery from bash and flashed.
@WayneWWW thanks in supporting in usb part,with your confirmation i find out the hardware issue