I can not find the driver for f81534 from your link.
Pleas just share the file here.
and what I want to check is the device tree (i.e. the dts file which includes the configuration for
Why you run
lspci rather than
lsusb to check USB issue?
Please give me the info command you need directly.
orinnx-lsusb-20231120.log (831 位元組)
xavier-lsusb-20231120.log (741 位元組)
Don’t you know what is device tree?
If not, it is dtb(compiled) file on your board or dts(source) file on your host.
Please get the
/boot/dtb/kernel_XXX.dtb from both of your boards.
Actually, this driver is not from us so that I could not give you the detailed logic inside.
Just a rough example here.
Now, you got the following error:
f81534 ttyUSB0: f81534_switch_gpio_mode: failed, 1245
From the source you would know taht it’s causing from
f81534_set_mask_normal_register() returns unexpected value, you could print the what’s the value of status. You could also print both status for f81534_get_normal_register() and f81534_set_normal_register() to debug further.
You should ask your vendor to let us know where it gets stuck in USB driver.
We could not help to debug the custom driver.
We obtained the Fintek development board and tested it from Orin NX PCIe to USB 2.0. Over 12hrs, no problems occurred. What are the parts related to USB2.0_1 adjustment? Which files can be adjusted?
You could check
usb2-1 node in device tree.
What do you mean about “Fintek development board”? Could you share the current block diagram of your connection? (failed case with successful case)
PCIe → USB → COM(Reference board) ok.
USB2.0_1 ->F81534 fail.
Have you tried connecting other USB3 port from the board?
Have you checked in details what’s the error from f81534 driver?
and could you reproduce the issue on the Orin Nano devkit(p3768)?
USB2.0_2 port has the same problem.
error from f81534 driver has been checked by Fintek.
We are currently requesting the company to provide it.
Please let us know the specific error coming from USB driver so that we could do further debug.
You could also get a Orin Nano devkit to check if the issue could be reproduced.
The driver has been checked again by fintek.
So this issue has been resolved by their new driver?
No, fintek does not think the problem is with the IC or driver.
Have you gotten the Orin Nano(p3768) devkit to reproduce the issue?
Already applied for Orin Nano(p3768) devkit but have not obtained it yet.