According to XavierNX Tuning guide, the usb3.1 compliance test is as follows.
> $echo on > '/sys/bus/usb/devices/usb1/power/control'
> $echo on > '/sys/bus/usb/devices/usb2/power/control'
> $devmem2 0x03610440
> /dev/mem opened.
> Memory mapped at address 0x7fb5733000.
> Value at address 0x3610440 (0x7fb5733440): 0x2A0
> $devmem2 0x03610440 w 0x10340
But we cannot get any compliance pattern. Could you please help on this? thanks!
Besides, Jetson module is directly connected to USB Type A connector on our carrier board and USB3 compliance test is verified successfully with Jetson Nano.
Hi, your command lines are correct, not sure why no pattern output. Seems you are testing on custom board, did you check it simultaneously to eliminate any possible issue?
We use original Xavier NX image and get the same result. Nvidia dev kit use usb3 hub, but It is not directly connect to connector. How do you confirm the document is correct?
Remark: our kernel has not change iomem structure.
There is other setting if hub exists, the guide doc is for port w/o hub like yours and was validated on prior dev kit.
There is no update from you for a period, assuming this is not an issue any more.
Hence we are closing this topic. If need further support, please open a new one.
Could you try to use the devmem from busybox instead of demvme2 from apt?
For anyone who hit error for usb3.0 compliance on rel-32.4.3, please
use devmem tool from busybox
Please try to see move back to rel-32.2.1 or rel32.2 and see if your issue is still.
If you can work on rel-32.2.1 but not rel-32.4.3, please consult us.
For those who hit error in usb3 compliance test on xavier. Please copy the old xusb fw (v60.05) to replace the v60.06 one in initrd under Linux_for_Tegra/bootloader.
We try to use the devmem from busybox, but still could not get compliance pattern.
Thanks for your help!
$echo on > ‘/sys/bus/usb/devices/usb1/power/control’
$echo on > ‘/sys/bus/usb/devices/usb2/power/control’
$busybox devmem 0x3610440
$busybox devmem 0x3610440 32 0x10340
It is confirmed rel-32.4.3 has issue on usb3 compliance. A workaround is use the old fw or use old release.