USB 2.0 not work

Hello,
I designed two usb2.0,usb1(A38 A39 A18) works well,usb2(B42,B43,A19) not work.The A19 is not high level,the usb can not enable 5v power.My device tree is as follows.What can i do next?Thank you.
pinctrl@3520000 {
vbus-0-supply = <&vdd_usb0_5v>;
vbus-1-supply = <&vdd_usb1_5v>;
#vbus-2-supply = <&vdd_usb2_5v>;
vbus-2-supply = <&battery_reg>;
vbus-3-supply = <&battery_reg>;
vddio-hsic-supply = <&battery_reg>;
avdd_usb-supply = <&spmic_sd3>;
vclamp_usb-supply = <&spmic_sd2>;
avdd_pll_erefeut-supply = <&spmic_sd2>;
};

Hi,
Please check
https://devtalk.nvidia.com/default/topic/1048285/jetson-tx2/how-to-setup-usb-config-4-for-tx2-l4t-28-2-1-/post/5320279/#5320279

A19 is unconnected.

Hi DaneLLL,
I changed the tegra186-quill-p3310-1000-c03-00-base.dts as follows.Because I used the one USB3.0 ODMDATA=0x1090000.The power if up when system startup the usb 2.0 is not work now,should I have to change other device tree?Thank you.
pcie-controller@10003000 {
pci@1,0 {
nvidia,num-lanes = <4>;
nvidia,disable-clock-request;
};
pci@2,0 {
nvidia,num-lanes = <0>;
};
pci@3,0 {
nvidia,num-lanes = <1>;
};
};

    xhci@3530000 {
            phys = <&tegra_xusb_padctl TEGRA_PADCTL_PHY_UTMI_P(0)>,
                    <&tegra_xusb_padctl TEGRA_PADCTL_PHY_UTMI_P(1)>,
                    <&tegra_xusb_padctl TEGRA_PADCTL_PHY_UTMI_P(2)>,
                    <&tegra_xusb_padctl TEGRA_PADCTL_PHY_USB3_P(0)>;
            phy-names = "utmi-0", "utmi-1", "utmi-2", "usb3-0";
    };

    pinctrl@3520000 {
        pinmux {
            usb3-std-A-port2 {
                    nvidia,lanes = "usb3-0";
                    nvidia,port-cap = <TEGRA_PADCTL_PORT_HOST_ONLY>;
                    status = "okay";
            };
            e3325-usb3-std-A-HS {
                status = "okay"; //This is usb2.0 port on M.2
            };
    };

Hi,
Please check https://elinux.org/Jetson/TX2_USB
and debug tips are at
https://devtalk.nvidia.com/default/topic/1048285/jetson-tx2/how-to-setup-usb-config-4-for-tx2-l4t-28-2-1-/post/5320806/#5320806

Hi DaneLLL,
I have solved the problem,because the device changed wrong.
Thank you!