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
