usb fail on migration from tx1 to tx2

Hello,

We have usb issue when migrating from tx1 to tx2 in our custom board:

At first we used tx1 module: we checked tx1 with tx1 developer kit and then with our custom board. usb works fine in both.

We then migrated to tx2.
We first checked it with tx1 developer kit - usb works fine.
But then in our custom board - usb fails ! (we get ubuntu screen but there is no response from mouse, keyboard)

Is there any idea ?

Thank,
ranran

Hi ranchu,

TX2 and TX1 carrier board is the same. Only the gpio mapping is different.

Could you share the error or the code you are using?

Hi,

I’ve edited the original post:

Our problem is related to USB:

At first we used tx1 module: we first checked it with tx1 developer kit and then with our custom board. usb worked in both.

We then migrated to tx2.
We first checked it with tx1 developer kit - usb works fine.
But then in our custom board - usb fails ! (we get ubuntu screen but there is no response from mouse, keyboard)

Is there any idea ?

Thanks,
ranchu

I think the driver is not up due to some regulator failure.
Please share the dmesg(kernel log) with us.

Thanks.

Hello,

Thank you very much for the reply.
I don’t have ethernet, and serial on the custom board, so that is a bit hard for me to check dmesg.

I use 28.1 source code :

wget -O Tegra18x_Linux_R28.1.0_aarch64.tbz2 https://developer.nvidia.com/embedded/dlc/l4t-jetson-tx2-driver-package-28-1

wget -O Tegra_Linux_Sample-Root-Filesystem_R28.1.0_aarch64.tbz2 https://developer.nvidia.com/embedded/dlc/l4t-sample-root-filesystem-28-1

wget -O source_release.tbz2 https://developer.nvidia.com/embedded/dlc/l4t-sources-28-1

[b]Is the bug fix comes after 28.1 ? Is so, it means that our driver need this patch , Right ?

This is tx1-tx2 migration document:
https://developer.download.nvidia.com/assets/embedded/downloads/secure/tx2/Jetson%20TX1-TX2%20Interface%20Comparison%20and%20Migration/Jetson_TX1_TX2_Interface_Comparison_and_Migration_v1.1.pdf?JneKj1xMCspXkK6-wOhSNJmcSLVN3LA2tZR5wxcKzwfhRQtWRUbL-rk-nv20h8IO9WNUWz3UXwLYOGQ4b65sM_EaH4G3EUHr4hWBJ002UQUan6GzzkxM_AYtrt4BdBM_Mvi0mTiUjxIpiVqB_EjmHfFzoB1DxDZEC38J2ps5iE-Xc7FZfK8oH-6Mut1yoLK8P6ajF6LSrna7KlnqJWirvsgufZhOGSG28OitZn_2guecrGN9Fc-7M6rJNM3A2lKJzeO3yzZWjCmvsns4cYLZSKhv05j_XyeV0W0

It seems from this document that there is a usb difference between tx1 and tx2, which might require additional gpio ?

Thanks you very much for any idea,
ranchu

It should be better to get the dmesg for any bring up work.
Please try to set the vbus to battery_reg as this link.

https://elinux.org/Jetson/TX2_USB

Thank you very much,
I’ll try it.

by the way, is it possible to get dmesg without serial,ethernet, and usb ?
I can move the tx2 module from the custom board to developer kit carrier, but does dmesg log is saved in non-volatile ? not sure.

I am not sure if syslog is able to be saved in disk w/o being refresh. Maybe you could write a script to automatically backup syslog during each boot.

Or just write a script to save dmesg as “dmesg >> dmesg.txt”