I am using two Flir Blackfly S cameras connected to the USB Type C connectors of the AGX dev kit. During development, I have also been attaching a USB hub to the third USB in order to connect a keyboard and mouse. Now that I am trying to make the system headless and only access the dev kit via Ethernet, I’m encountering a performance problem.
The camera attached to J513 (usb 2-1) cannot run at its full frame rate after a power cycle. The second camera still performs well at 30-40 FPS but the one attached to J513 is only getting ~6FPS. Querying the device via /sys/bus/usb/devices/2-1/speed and version indicates it is recognized as USB 3.1. The only workarounds I have found are to again attach the (unneeded) hub to the J507 port and reboot or to physically disconnect and reconnect the camera with the problem. Either workaround resolves the issue until the system is power-cycled without something attached to J507.
I have tried different cameras and different cables and the problem consistently stays with the port. Also, based on other forum posts, I’ve tried setting usbcore.autosuspend=-1.
I am attaching two captures from dmesg. One is from a fresh boot with the hub attached (when there is no problem) and one when the hub is not attached (and then slow performance on J513). I’ve had a thought regarding the following messages:
tegra-xusb 3610000.xhci: Upgrade port 0 to USB3.0
tegra-xusb 3610000.xhci: Upgrade port 1 to USB3.0
Since the usb2-1 is loaded just after this, could the upgrade process still be in progress resulting in the device actually being loaded up as a USB 2.0 device even though it will report otherwise?
-Is there a way to adjust the boot process to allow more time between the upgrade process and loading of usb2-1?
-Are there any other suggestions on how to troubleshoot or solve this issue?
Any help is greatly appreciated…thanks in advance!