Usbserial does not load though usb device is recognised

I have a problem similar to one described here Jetpack 6.0 doesn't include the ttyUSB driver

I have a microcontroller based device which recognized as a USB Device. On x86 I use a rule which loads usbserial if particular vendor and product ids are found. After it the device is shown as /dev/ttyUSB0

On the AGX with Jetpack 6 it doesnt work. A Usb device being inserted is recognized and shown in lsusb with the same vendor and product ids. But loading usbserial doesnt lead to anything. No error in logs.

In contrast to working x86 config dmesg shows only
[ 1647.157360] usb 1-1.1: new high-speed USB device number 10 using tegra-xusb

Though on x86 it show more line from usb x-x.x before loading usbserial. like ‘New USB device found, idVendor …’

What could be a reson and how to solve it?

Sorry for the late response.
Is this still an issue to support? Any result can be shared?

Incidentally, the devices in “/dev/ttyUSB*” are generally using the FTDI serial UART driver. In JetPack 6.x (L4T R36.x) Jetsons switched to using the mainline kernel. This includes the default configuration of the mainline kernel. You can build the FTDI driver as a module and simply copy the module to the right place, followed by “sudo depmod -a” and from then on it should work.

Embedded systems often have less space, including RAM and disk. So you won’t find everything that a distribution comes with to be enabled by default.

Hi,
If you would like to enable certain kernel configs for the function, please refer to the section in developer guide:

Kernel Customization — NVIDIA Jetson Linux Developer Guide 1 documentation

Thanks for the replies. We downgraded to the Jetpack 5.1. But it helped only with a proper usb device identification. Then we found out, that we need the usbserial generic driver, which was not activated in the compilation config. So the kernel was recompiled with this option. And the usbserial module with the Image were replaced. Now it works. The same approach with the Jetpack 6.1 didnt work unfortanutely. We didnt investigate it further.