New Contributor
New ContributorThank you for your response, and apologies for the delayed reply.
The initial issue related to USB device recognition and speed negotiation was resolved by enabling the appropriate drivers in the virtual kernel of my Yocto-based project.
Due to the USB 3.0 limitation of the RealSense camera and the USB 2.0 interface available on the Arria 10 platform, I decided to switch the RGB-D camera to a Kinect v1 (Xbox 360).
I am currently attempting to interface with the Kinect using both the libfreenect library and direct USB frame communication. However, the issue appears to be within the USB subsystem: something in the USB drivers is blocking the data flow between the ARM processor and the camera.
The camera itself has been tested and works correctly on other platforms such as Jetson and Raspberry Pi, so a hardware issue is unlikely. At this point, I suspect the problem may be related to the dwc2 driver or possibly missing permissions or misconfigured drivers within the system.
Any suggestions would be greatly appreciated.
ModeratorHi angelsz15 ,
I hope you’re doing well. I wanted to follow up and check if there are any remaining questions or concerns regarding this matter. Please let us know if anything still needs clarification — we’re happy to assist further.
Thank you for your time, and we look forward to your feedback.
Best Wishes
BB
New ContributorThank you for your interest BoonBengT_Altera in my case. I am documenting all the issues I encounter in this thread, so any help or suggestions are welcome.
ContributorHi angelsz15,
What remaining questions or concerns do you have?
Sue
New ContributorHi SueC_Altera
I am currently working with a Kinect V1 (Xbox 360 Model 1414) using the Arria 10 SoC GSRD. At the moment, the system correctly detects the hardware (camera, motor, and audio are listed in lsusb). However, I am experiencing failures when initiating communication with the device, including USB transfer errors, incomplete reads, and unexpected disconnections.
I have ruled out permission issues (running as root and udev rules applied), so I suspect the root cause may be related to limitations of the USB controller (dwc2), bus saturation, or hardware constraints for handling isochronous transfers.
As a reference, I have tested with standard USB 2.0 webcam devices, and in those cases I am able to communicate with them and stream video without issues.
Full console output attached:
root@arria10-ea700498022f:~/app# ./kinect_test_app
send_cmd: Input control transfer failed (18)
[ 340.405365] usb 1-1.3: USB disconnect, device number 7
freenect_fetch_reg_info: send_cmd read 18 bytes (expected 118)
send_cmd: Output control transfer failed (-1)
freenect_fetch_reg_const_shift: send_cmd read -1 bytes (expected 8)
freenect_camera_init(): Failed to fetch const shift for device
Device 0x51fda0 open during shutdown, closing...
root@arria10-ea700498022f:~/app# [ 343.517208] usb 1-1.3: new high-speed USB device number 8 using dwc2
root@arria10-ea700498022f:~/app# lsusb -t
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/3p, 480M
|__ Port 1: Dev 4, If 0, Class=Vendor Specific Class, Driver=, 480M
|__ Port 2: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
|__ Port 3: Dev 8, If 0, Class=Vendor Specific Class, Driver=, 480M
root@arria10-ea700498022f:~/app# lsusb
Bus 001 Device 008: ID 045e:02ae Microsoft Corp. Xbox NUI Camera
Bus 001 Device 003: ID 045e:02b0 Microsoft Corp. Xbox NUI Motor
Bus 001 Device 004: ID 045e:02ad Microsoft Corp. Xbox NUI Audio
Bus 001 Device 002: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
