How should the device tree be configured for USB Type-C 3.0

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
1

Hi Nvidia，

Jetpack: JP6.0 (R36.3)

On our carrier board, the USB Type-C interface does not connect to D1_N/D1_P and D2_N/D2_P pins. How should the device tree be configured?

image
image1404×876 84.7 KB

2

*** Please note that this reply is generated by LLM automatically ***

Based on the provided context, I will provide a comprehensive answer to the question.

The question is about configuring the device tree for a custom carrier board with a USB Type-C interface that does not connect to the D1ND1P and D2ND2P pins.

From the context, we can see that the Jetson AGX Orin P3737 carrier board has a USB Type-C interface (J39) that is connected to the SOM socket through U138 and U513, the USB type-C alt mode switch. The USB2.0 signal pair is wired to UTMI pad 0 (USB2 port 0), and the USB3.2 signal pairs are wired to UPHY lane 1 (USB3.2 port 1 according to UPHY lane mapping).

However, in the case of the custom carrier board, the USB Type-C interface does not connect to the D1ND1P and D2ND2P pins. This means that the device tree configuration needs to be adjusted accordingly.

To configure the device tree, we need to refer to the NVIDIA Jetson AGX Orin Series SOC Technical Reference Manual (TRM) and the NVIDIA Jetson AGX Orin Series Product Design Guide (DG). We also need to contact NVIDIA for further guidance.

In general, the device tree configuration for a USB interface involves specifying the USB controller, the USB port, and the USB connector. Since the custom carrier board has a different USB interface configuration, we need to update the device tree to reflect this.

Here is an example of how the device tree configuration might look like for a USB Type-C interface on the Jetson AGX Orin P3737 carrier board:

&xusb {
    status = "okay";
    usb@0 {
        status = "okay";
        usb-phy = <&u2phy0>;
        usb-phy-names = "usb2-phy";
        vbus-supply = <&vbus-5v>;
    };
    usb@1 {
        status = "okay";
        usb-phy = <&u3phy0>;
        usb-phy-names = "usb3-phy";
        vbus-supply = <&vbus-5v>;
    };
};

However, since the custom carrier board has a different USB interface configuration, we need to update the device tree to reflect this. For example, we might need to change the USB controller, the USB port, or the USB connector configuration.

In summary, to configure the device tree for a custom carrier board with a USB Type-C interface that does not connect to the D1ND1P and D2ND2P pins, we need to refer to the NVIDIA Jetson AGX Orin Series SOC Technical Reference Manual (TRM) and the NVIDIA Jetson AGX Orin Series Product Design Guide (DG), and contact NVIDIA for further guidance. We also need to update the device tree to reflect the custom USB interface configuration.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

4

This hardware design is invalid. Our software driver does not support such.