TX2 usb3.0 config 6 usb3-0 usb-3-1 can not connect

background: custom carrierd baord jetpack 4.5
question:usb3.0 can not connect
divece tree
extracted.dts (495.7 KB)
log
a.log (95.0 KB)

Please attach your board schematic.


new dts
extracted.dts (495.6 KB)

Why do you put ODMDATA inside the device tree…???

That is for the MB1, you should let the flash script do the work. Not device tree.

And pcie lane should be 2,1,1. Not 1,2,1…

Also, the status is “disabled”… not “disable”.

Read the adaptation guide please…

new dts
a.dts (491.6 KB)

I modified the error of the device tree. Please help me check it, but I didn’t find the location of ODMDATA in the device tree, but I modified it in “p2771-0000.conf.common”
image

dmesg and lsusb log please.

image
a.log (84.2 KB)

Hi,

You didn’t mention there is a hub on it. Could you clarify what is the whole topology of your usb connection is like?

USB3-1 not connect a hub,It connects directly from the CPU to the port

Share us all the topology. Not just usb3-1.

Please try to describe more about your desing instead of sharing us same info again and again.

Please disable 3-0 usb, connect a SS device to 3-1 and dump dmesg again.

What is the SS device? I connect a usb3.0 ssd device. Do I need to close the 2.0 port corresponding to 3.0?
dmesg log
a.log (83.5 KB)

image

device tree
extracted.dts (495.5 KB)

HI,

Could you firstly disable all the usb3.0 devices in your device tree, debug usb2 device one by one and see if they can work?

all usb2.0 port can work, each interface can recognize the mouse


Ok, now can you enable usb3-1 only and share dmesg.

dmesg.log (83.8 KB)
I connect a usb3.0 ssd device, but there was no response

please use the register dump to make sure the odmdata is correctly set.

3. UPHY lane 0: ./devmem2 0x02520284
4. UPHY lane 1: ./devmem2 0x02530284
5. UPHY lane 2: ./devmem2 0x02540284
6. UPHY lane 3: ./devmem2 0x02550284
7. UPHY lane 4: ./devmem2 0x02560284
8. UPHY lane 5: ./devmem2 0x02570284

and please remove them from your dts. They shouldn’t be here.

odm-data {
disable-pmic-wdt = <0x1>;
no-battery = <0x1>;
enable-debug-console = <0x1>;
enable-xusb-on-uphy-lane0 = <0x1>;
normal-flashed = <0x1>;
disable-tegra-wdt = <0x1>;
android-build = <0x1>;
enable-sata-on-uphy-lane5 = <0x1>;
enable-xusb-on-uphy-lane1 = <0x1>;
enable-denver-wdt = <0x1>;
enable-pcie-on-uphy-lane4 = <0x1>;
disable-sdmmc-hwcq = <0x1>;
enable-pcie-on-uphy-lane2 = <0x1>;

I can not read register, What’s wrong with the operation
image

I have remove this from dts, but when i get device tree from tx2 core by “sudo dtc -I fs -O dts -o ./extracted.dts
/proc/device-tree”, it will be add, because flash.sh?
odm-data {
disable-pmic-wdt = <0x1>;
no-battery = <0x1>;
enable-debug-console = <0x1>;
enable-xusb-on-uphy-lane0 = <0x1>;
normal-flashed = <0x1>;
disable-tegra-wdt = <0x1>;
android-build = <0x1>;
enable-sata-on-uphy-lane5 = <0x1>;
enable-xusb-on-uphy-lane1 = <0x1>;
enable-denver-wdt = <0x1>;
enable-pcie-on-uphy-lane4 = <0x1>;
disable-sdmmc-hwcq = <0x1>;
enable-pcie-on-uphy-lane2 = <0x1>;

Try to use devmem from busybox.