We designed ower own carrier board with xavier core-board,and has 3 usb3.0 ports(1 tpyeA,2 typeB,all without PD controller).Now we face a problem，the typeA usb port works very well(it can recognise 3.0 devices and 2.0 devices)，but the other two typeB usb ports port can only recognise usb2.0 devices.Can anybody help me?
Hi, are you using the USB 3.1, PCIe & UFS Lane Mapping Configurations in OEM DG?
Hi,Trumany,out design is as follows：
UPYH 0 — not used
UPYH 1 — USB3.1(P2) typeA
UPYH[2-5] — PCIE *4(C0)
UPYH 6 — USB3.1(P0) typeB
UPYH 7 — not used
UPYH[8-9] — PCIE *2(C4)
UPYH 10 — not used
UPYH 11 — USB3.1(P3) typeB
NVHS[0-7] — PCIE *8(C5)
should we modify the device tree?The only thing now we have modified is that we changed the usb2-0 mode from “otg” to “host” and removed the “extcon-*” properties.
Please refer to the xavier adaptation guide. Removing the pd controller requires the change in device tree.
Also, your power tree is still using the one from devkit, which may not apply to your design.
→ nvidia/platform/t19x/galen/kernel-dts/common/tegra194-power-tree-p2888-0001-p2822-1000.dtsi
52 ports {
53 usb2-0 {
54 vbus-supply = <&battery_reg>;
55 };
56 usb2-1 {
57 vbus-supply = <&battery_reg>;
58 };
59 usb2-2 {
60 vbus-supply = <&battery_reg>;
61 };
62 usb2-3 {
63 vbus-supply = <&p2822_vdd_5v_sata>;
64 };
We use battery_reg on devkit because PD controller would handle it. However, since you don’t have pd on it, please use correct regulator for vbus.
In our design，the vbus is directly connected to +5v，should we also need to modify the power-tree？
also，all usb ports can recognise usb2.0 devices like keyboard…
In our design，the vbus is directly connected to +5v，should we also need to modify the power-tree？
Such design would have problem. You shared the similar issue as below topic. Though it is on TX2.
TX2 JetPack4.2, After reboot TX2 can't recogonize USB3.0 Camera, but USB3.0 UDisk can be recogonized... - Jetson TX2 - NVIDIA Developer Forums
if we do not change our design（vbus is directly connected to +5v），just modify the dts by creating a new regulator,can we fix our problem?
I think you could read the adaptation guide for some device tree node first. If you confirm no problem, then we go back to check the power tree.
Just discussed with our dev team, this design should work (except for some devices as the topic I shared).
OK
I noticed some errors,when I connet the udisk：
[ 114.484177] tegra-xusb 3610000.xhci: exiting ELPG
[ 114.489929] tegra-xusb 3610000.xhci: Firmware timestamp: 2018-03-29 14:24:42 UTC, Version: 60.05 release
[ 114.492359] tegra-xusb 3610000.xhci: exiting ELPG done
[ 115.343496] tegra-xusb 3610000.xhci: Cannot set link state.
[ 115.343723] usb usb2-port1: cannot disable (err = -32)
[ 116.087262] tegra-xusb 3610000.xhci: Cannot set link state.
[ 116.087479] usb usb2-port1: cannot disable (err = -32)
[ 116.087622] tegra-xusb 3610000.xhci: Cannot set link state.
[ 116.087832] usb usb2-port1: cannot disable (err = -32)
[ 116.207118] usb 1-2: new full-speed USB device number 4 using tegra-xusb
[ 116.228518] usb 1-2: not running at top speed; connect to a high speed hub
[ 116.230367] usb 1-2: New USB device found, idVendor=0781, idProduct=5597
[ 116.230409] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 116.230414] usb 1-2: Product: Cruzer Glide 3.0
[ 116.230420] usb 1-2: Manufacturer: SanDisk
[ 116.230423] usb 1-2: SerialNumber: 4C530001150319121533
[ 116.232629] usb-storage 1-2:1.0: USB Mass Storage device detected
[ 116.239871] scsi host0: usb-storage 1-2:1.0
[ 116.243734] Could not get extcon-dev /host1x/nvdisplay@15210000:typec0(0)
[ 116.244981] drivers/extcon/extcon.c 1570 UCAS test cable_name:typec0
[ 116.246563] Could not get extcon-dev /host1x/nvdisplay@15220000:typec1(1)
[ 116.246718] drivers/extcon/extcon.c 1570 UCAS test cable_name:typec1
[ 117.253107] scsi 0:0:0:0: Direct-Access SanDisk Cruzer Glide 3.0 1.00 PQ: 0 ANSI: 6
[ 117.259384] Could not get extcon-dev /host1x/nvdisplay@15220000:typec1(1)
[ 117.259544] drivers/extcon/extcon.c 1570 UCAS test cable_name:typec1
[ 117.259932] Could not get extcon-dev /host1x/nvdisplay@15210000:typec0(0)
[ 117.260061] drivers/extcon/extcon.c 1570 UCAS test cable_name:typec0
[ 117.260997] sd 0:0:0:0: [sda] 30605312 512-byte logical blocks: (15.7 GB/14.6 GiB)
[ 117.264867] sd 0:0:0:0: [sda] Write Protect is off
[ 117.264992] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
[ 117.266571] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn’t support DPO or FUA
[ 117.292973] sda: sda4
[ 117.298504] sd 0:0:0:0: [sda] Attached SCSI removable disk
Could you share your current device tree?
you can get it in #4,and now we have not modified the power tree yet.
Hi sclsdhlr,
- Could you also try other SS devices?
- Try add “nvidia,usb3-gen1-only= <1>;” in other usb3 ports
Hi WayneWWW，
Thanks for your advice
Hi sclsdhlr,
Does it work?
The question remains the same.
Hi,
How about the result of question (1)?
Could you also try other SS devices? Could they get enumerated successfully?