Jetpack4.2 USB not recognized

Hi.
Thank you for always quick help.

We are developing a vehicle solution based on Tx2 based target board.
We are using an LTE module with an onboard USB interface.

On the same board
In Jetpack 3.2, the recognized module

nvidia@tegra-ubuntu:~ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub <u>Bus 001 Device 003: ID 1ecb:0205 </u> Bus 001 Device 002: ID 0424:2513 Standard Microsystems Corp. 2.0 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub nvidia@tegra-ubuntu:~ uname -a
Linux tegra-ubuntu 4.4.38 #1 SMP PREEMPT Fri Apr 19 16:14:24 KST 2019 aarch64 aarch64 aarch64 GNU/Linux

It will not be recognized until after Jetpack 4.2 is installed.

nvidia@tegra-ubuntu:~ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0424:2513 Standard Microsystems Corp. 2.0 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub nvidia@tegra-ubuntu:~ uname -a
Linux tegra-ubuntu 4.9.140 #1 SMP PREEMPT Mon Apr 22 09:41:33 KST 2019 aarch64 aarch64 aarch64 GNU/Linux

Power Voltage was found to be OK.
Dmesg check result did not show any special message when I plug it in again.

I did not do anything special about USB.

Is there a fix for USB interface in Jetpack 4.2?

How can I debug it?

Hi,
We are working on adaptation guide for r32.1.

Please check if below post helps your case:
https://devtalk.nvidia.com/default/topic/1049988/jetson-tx2/third-usb-on-custom-board-not-working-with-jetpack-4-2/post/5330117/#5330117

Is it correct that it is just this one device not showing up? You might try verbose mode (the “-d” is to limit to that specific vendor and product ID, the “-vvv” is the most verbose you can list):

sudo lsusb -d 1ecb:0205 <b>-vvv</b>

If you look up the USB vendor ID here you’ll see a note related to this:
https://usb-ids.gowdy.us/read/UD/1ecb

The note is here:
https://unix.stackexchange.com/questions/416562/why-doesnt-lsusb-list-a-device/416563

It is quite possible that it is a case of the brief listing mode ignoring the device because it isn’t a known vendor ID. If you were to go to http://www.linux-usb.org/usb.ids, then you’d see the list does not have that number (“1ecb”).

If this is the case, then you could probably add the ID to the usb.ids file. However, this is probably not the correct way to do it since some other update might overwrite an edit (this would be a nice way to test though if it is just a case of requiring verbose mode listing).

To. DaneLLL

Good.
USB has been recognized after applying the above contents.
Thank you very much.