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.
From the source you would know taht itās causing from Line:1245. 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.
Hi Kevin
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?
What do you mean about āFintek development boardā? Could you share the current block diagram of your connection? (failed case with successful case)
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.
Observed from LA
The first out token requires the device to perform the following actions:
offset 00: 00h (UART0)
offset 01: 02h (UART command TX)
offset 02: 64h (TX 100 bytes)
offset 03: donāt care.
offset 04~104: TX data (from 64~c7h)
But the second out token, is completely messed up.
2.After Driver timeout, print the current packet data expected to be sent.
The expected information to be sent is following picture 1. The last picture in picture 1 is c4/c5/c6/c7, and the information to be sent here is c8/c9/caā¦ which is correct.
But what was recorded by USB LA was not sent by the Driver (the second out token in Figure 1)
Hi Kevin
In the first picture, the last out token is TX c6 / c7, so theoretically the next out token should start from c8.
However, the picture recorded by USB analysis is a messed up packet. The second picture is the actual data of the packet to be transmitted, and it is inconsistent with what was recorded.