Jetson TX2 USB phy is not available

We have a board with TX1 installed and everything works as expected

We want to upgrade to TX2 and we are unable to connect to USB on a custom board.

For the purpose of clarifying the evaluation board, everything is working properly.

The TX2 card has JetPack_4.6_Linux

I have read in various forums about a similar glitch when in most cases it is JetPack 4.2

I did what they recommended to do here as well as what they recommended to do here

Given the oral answer written here by DaneLLL on Sep 11 '18

vbus-2-supply = <0x0000001a>;

& battery_reg is compiled into 0x0000001a

The actual changes I made:

In the kernel_tegra186-quill-p3310-1000-c03-00-base.dtb file

And in the tegra186-quill-p3310-1000-c03-00-base.dtb file

Under pinctrl @ 3520000 I changed the parameter

vbus-2-supply = <0x1a>;

I copied the edges to the paths

Linux_for_Tegra / rootfs / boot / tegra186-quill-p3310-1000-c03-00-base.dtb

Linux_for_Tegra / bootloader / tegra186-quill-p3310-1000-c03-00-base.dtb

Linux_for_Tegra / kernel / dtb / tegra186-quill-p3310-1000-c03-00-base.dtb

And I installed on the card by command:

sudo ./flash.sh jetson-tx2 mmcblk0p1

In practice, no change appears on the custom board.

The lsusb command does not return anything.

I am not sure if you really understand how things work or you just want to copy and paste something and expect it would work.

Those <0x1a> is just a like a id for the dtb in that topic to use. For example, 0x1a may represent battery_rag in that case. But it may not be the same thing in your dtb. So just copy and paste it may not work.

Also, if you are using rel-32 based source code, then refer to any post from 2018 may not work. Those posts are mostly for rel-28 release.

Please refer to the adaptation guide to understand how to modify device tree for customization board.

Hi Wayne,

attached more information from our test between your EVB- PN:945-82771-0000-000 to our PCB:
lsusb command on EVB - we connected Realtek USB HUB, Mouse and Keyboard :
airobotics@UAV999:~$ lsusb
Bus 002 Device 002: ID 0bda:0411 Realtek Semiconductor Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
Bus 001 Device 003: ID 04d9:1702 Holtek Semiconductor, Inc. Keyboard LKS02
Bus 001 Device 002: ID 0bda:5411 Realtek Semiconductor Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lsusb command on our BOARD No device were found:
airobotics@UAV999:~$ lsusb

Status command on EVB:

Status command on our BOARD:

Hi,

The information you are sharing does not help.

Just share your board schematic and tell us which port is not working. Also, share the full dmesg and your current device tree.

Hi,

The dmesg:
airobotics@UAV999:/opt/nvidia/l4t-usb-device-mode$ dmesg | grep usb
[ 0.000000] Kernel command line: console=ttyS0,115200 androidboot.presilicon=true firmware_class.path=/etc/firmware root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 isolcpus=1-2 video=tegrafb earlycon=uart8250,mmio32,0x3100000 nvdumper_reserved=0x2772e0000 gpt rootfs.slot_suffix= usbcore.old_scheme_first=1 tegraid=18.1.2.0.0 maxcpus=6 no_console_suspend boot.slot_suffix= boot.ratchetvalues=0.2031647.1 vpr_resize bl_prof_dataptr=0x10000@0x275840000 sdhci_tegra.en_boot_part_access=1 quiet root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 isolcpus=1-2
[ 0.520886] usbcore: registered new interface driver usbfs
[ 0.520920] usbcore: registered new interface driver hub
[ 0.520947] usbcore: registered new device driver usb
[ 0.577216] vdd-usb0-5v: 5000 mV
[ 0.577491] vdd-usb1-5v: 5000 mV
[ 0.925829] tegra-xusb-padctl 3520000.xusb_padctl: failed to setup XUSB ports: -517
[ 1.061021] usbcore: registered new interface driver r8152
[ 1.061051] usbcore: registered new interface driver asix
[ 1.061080] usbcore: registered new interface driver ax88179_178a
[ 1.061109] usbcore: registered new interface driver cdc_ether
[ 1.061135] usbcore: registered new interface driver net1080
[ 1.061160] usbcore: registered new interface driver cdc_subset
[ 1.061186] usbcore: registered new interface driver zaurus
[ 1.061219] usbcore: registered new interface driver cdc_ncm
[ 1.064880] usbcore: registered new interface driver uas
[ 1.064919] usbcore: registered new interface driver usb-storage
[ 1.064984] usbcore: registered new interface driver usbserial
[ 1.066672] tegra-usb-cd usb_cd: otg phy is not available yet
[ 1.069424] usbcore: registered new interface driver xpad
[ 1.245051] usbcore: registered new interface driver usbhid
[ 1.245053] usbhid: USB HID core driver
[ 1.264764] usbcore: registered new interface driver snd-usb-audio
[ 1.427928] tegra-xusb-padctl 3520000.xusb_padctl: failed to setup XUSB ports: -517
[ 1.430755] tegra-usb-cd usb_cd: otg phy is not available yet
[ 1.437174] tegra-xusb-padctl 3520000.xusb_padctl: failed to setup XUSB ports: -517
[ 1.439993] tegra-usb-cd usb_cd: otg phy is not available yet
[ 1.446496] tegra-xusb-padctl 3520000.xusb_padctl: failed to setup XUSB ports: -517
[ 1.556109] tegra-usb-cd usb_cd: otg phy is not available yet
[ 1.560593] tegra-xusb-padctl 3520000.xusb_padctl: failed to setup XUSB ports: -517
[ 2.125609] tegra-usb-cd usb_cd: otg phy is not available yet
[ 2.130453] tegra-xusb-padctl 3520000.xusb_padctl: failed to setup XUSB ports: -517
[ 4.604883] tegra-usb-cd usb_cd: otg phy is not available yet
[ 4.612492] tegra-xusb-padctl 3520000.xusb_padctl: failed to setup XUSB ports: -517
[ 4.616784] tegra-usb-cd usb_cd: otg phy is not available yet
[ 4.627809] tegra-xusb-padctl 3520000.xusb_padctl: failed to setup XUSB ports: -517
[ 4.648591] tegra-usb-cd usb_cd: otg phy is not available yet
[ 4.657490] tegra-xusb-padctl 3520000.xusb_padctl: failed to setup XUSB ports: -517
[ 4.920068] tegra-usb-cd usb_cd: otg phy is not available yet
[ 4.928635] tegra-xusb-padctl 3520000.xusb_padctl: failed to setup XUSB ports: -517
[ 4.934786] tegra-usb-cd usb_cd: otg phy is not available yet
[ 4.951649] tegra-xusb-padctl 3520000.xusb_padctl: failed to setup XUSB ports: -517
[ 5.603998] tegra-usb-cd usb_cd: otg phy is not available yet
[ 5.616001] tegra-xusb-padctl 3520000.xusb_padctl: failed to setup XUSB ports: -517
[ 5.621862] tegra-usb-cd usb_cd: otg phy is not available yet
[ 5.640418] tegra-xusb-padctl 3520000.xusb_padctl: failed to setup XUSB ports: -517
[ 31.824614] vdd-usb0-5v: disabling
[ 31.824624] vdd-usb1-5v: disabling
airobotics@UAV999:/opt/nvidia/l4t-usb-device-mode$ sudo ./nv-l4t-usb-device-mode-stop.sh
./nv-l4t-usb-device-mode-stop.sh: line 34: l4t/UDC: No such file or directory
rmdir: failed to remove ‘l4t/configs/c.1/strings/0x409’: No such file or directory
rmdir: failed to remove ‘l4t/functions/ncm.usb0/’: No such file or directory
rmdir: failed to remove ‘l4t/functions/ecm.usb0/’: No such file or directory
rmdir: failed to remove ‘l4t/functions/mass_storage.0/’: No such file or directory
rmdir: failed to remove ‘l4t/functions/acm.GS0/’: No such file or directory
rmdir: failed to remove ‘l4t/functions/rndis.usb0/’: No such file or directory
rmdir: failed to remove ‘l4t/configs/c.1/’: No such file or directory
rmdir: failed to remove ‘l4t/strings/0x409’: No such file or directory
rmdir: failed to remove ‘l4t’: No such file or directory
l4tbr0: ERROR while getting interface flags: No such device
bridge l4tbr0 doesn’t exist; can’t delete it
airobotics@UAV999:/opt/nvidia/l4t-usb-device-mode$ sudo ./nv-l4t-usb-device-mode-sta
nv-l4t-usb-device-mode-start.sh nv-l4t-usb-device-mode-state-change.sh
airobotics@UAV999:/opt/nvidia/l4t-usb-device-mode$ sudo ./nv-l4t-usb-device-mode-start.sh
No known UDC device found

Hi,

Do not grep anything. Just attach the full dmesg here. This forum is able to post files.

Hi,
Attached syslog and dtc file
dtc.txt (499.3 KB)
syslog.txt (763.4 KB)

Hi,

Please attach the dmesg. No one is asking for your syslog…

Attached the dmesg and the schematics of the USB part
USB schematics.docx (191.9 KB)
dmesg.txt (58.9 KB)

Hi,

The picture on your schematic is not clear enough. How about you directly tell us which usb pin is in use here?

Do you have only one usb2 hub and another one as usb2 otg?

USB HUB PINS:
TX1_USB1_DP - pin A38
TX1_USB1_DN - A39

usb2 OTG:
U_USB_CONN_DM - pin B40
U_USB_CONN_DP - pin B39

We have only one usb2 hub and another one as usb2 otg.

Hi,

Honestly, I guess you didn’t read the adaptation guide at all… Your dts file has some common error that document already covered…

Please read the document first.

Can you please send me the adaptation guide.

https://docs.nvidia.com/jetson/l4t/index.html#page/Tegra%20Linux%20Driver%20Package%20Development%20Guide/adaptation_and_bringup_tx2.html

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.