I’ll leave that one to @WayneWWW since I don’t know the specifics of the device tree for this. However, do know that if you altered anything to do with which controllers are present, then there will be device tree changes (device tree includes more or less “stitching together” the function of the USB3 controller and the USB2 controller for correct routing depending on what is detected).
-
You need to give out your schematic first so that someone else could tell whether device tree is correct or not. I already told before. This device tree needs to follow your hardware design.
We are not your coworkers so we don’t know any of your routing or how the ID pin /vbus-det are connecting to. Without these info, we could not tell if your device tree is correct. -
I saw an obvious error there. What is that remote-endpoint doing here? There is no such device 0xf8 mapping to.
port {
endpoint {
remote-endpoint = <0xf8>;
phandle = <0x106>;
};
};
Hello,
- Will share the schematic over a private message.
- Okay will remove it.
Update:
After removing it it’s not detecting it still.
Your design has no ID pin so this could only be in device mode.
If this is Jetpack5, then your device tree should be like something as below.
146 ports {
147 usb2-0 {
148 mode = "otg";
149 status = "okay";
150
151 usb-role-switch;
152 connector {
153 compatible = "usb-b-connector", "gpio-usb-b-connector";
154 label = "micro-USB";
155 type = "micro";
156 vbus-gpio = <&tegra_main_gpio TEGRA194_MAIN_GPIO(Z, 1) GPIO_ACTIVE_LOW>;
157 };
158
159 };
Please modify the vbus gpio to match your Vbus_det GPIO.
Yes there is no ID pin. Okay.
We are flashing Jetpack 6. Should something be changed for it.
The VBUS_DET is going to pin 87
@WayneWWW any updates regarding for Jetpack6 ?
We tried with the above format it shows syntax error while converting to dtb file
Sorry for the late response.
Is this still an issue to support? Any result can be shared?
Hello,
Yes the issue is still there. Support is needed on enabling it.
please refer to document.
Hello,
Is there a reference for the micro USB connector as the type C incorporates the ID pin. Had followed the steps mentioned by @WayneWWW previously. Got a syntax error for Jetpack 6.
Is something wrong if the above format?
At least tell what kind of syntax error did you see there… we don’t know how you actually did on your side.
For example, if you forgot to add a “}” or a “;” then you could get a syntax error too…
PFA the dts file. It’s unkown what was the syntax error.
orin_nx_modified.zip (35.4 KB)
please share what error did you see on your screen… It will tell which line has error…
The system is not with me at the time will share it by tomorrow. Sorry for the inconvience
It’s an error in this line.
”vbus-gpio = <&gpio TEGRA234_MAIN_GPIO(Z, 1) GPIO_ACTIVE_LOW>;”
PFA the dts file and the error image
orin_nx_modified.zip (35.4 KB)
dtc tool won’t know the definition of “TEGRA234_MAIN_GPIO”…
if you want to use such macro, you should build it from source code directly but not using dtc to convert it.
Okay, so how to proceed further?
Can you guide?
this document guides how to build kernel dtb from source code.
Okay. Thanks, will look into it.
There is no workaround around it?
no, this is basic item that you should pick up.
Okay. Will post here for further queries on it.