-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kernel 4.19 support for Raspberry Pi 4 #4818
Comments
A bug-fix for Kernel 4.19 was added in SDK version 2.24.0. Some users continued to report problems with using 4.19 though. A RealSense user succeeded in using 4.19 with Pi4 and Raspbian Buster with a method suggested by a member of Intel's RealSense team. |
We only support official kernel versions used in i86 LTS versions of Ubuntu 16 / 18. This doesn't mean it will or will not work on non-i86 hardware, we just cannot make such commitments. For non-i86 platforms we recommend libuvc_installation.md installation without kernel patching. |
I've got it working as well on a Pi4 with Raspbian Buster 4.19 |
Is the IMU data working as well ? |
I'm using the D410 module, it doesn't have an IMU, so I can't say unfortunately. |
I'm using Ubuntu 18 in my Pi 4. With some adjustments, realsense works but Ubuntu does not have official kernel to Pi 4 then some drivers like WiFi need some attention. |
Hi, |
Apparently the STM32MP1 uses ARM Cortex-A7 for its compatibility with open-source operating systems such as Linux and Android. There was a case where somebody was using T265 with a Cortex-A7 processor and Ubuntu. It looks as though the BananaPi Zero hardware they were using was running Kernel 4.19.0. http://wiki.banana-pi.org/Banana_Pi_BPI-M2_ZERO The user had some initial problems but got it working fine shortly afterwards, as indicated in the comments below the linked-to one. |
Thanks MartyG, |
The T265 can stream pose data on USB2 but needs USB3 for fisheye streams. So USB2 OTG would not be appropriate if you need fisheye data in your project. I don't know about connecting T265 to OTG, but it is certainly possible to connect RealSense depth cameras to OTG if you use an OTG adapter to connect a full-size USB A connector to an OTG micro-port. |
So if we only need the pose data you mean that we could get it using the USB 2.0 port of the STM32F7 for example? But is there any library to know how to initiate this communication and to parse the received data? |
The official T265 documentation page says "Any board with USB2 capable of receiving pose data at 200 times a second should be sufficient". Intel have published a guide to getting IMU data from the T265 that has a pose-data script at the end of it, in the 'API' section. https://www.intelrealsense.com/how-to-getting-imu-data-from-d435i-and-t265/ |
Thanks for your help. |
If you scroll right to the bottom of the page and then scroll a little up, the API section is near the bottom of the page. You can also access more sample programs compatible with T265 tracking here: https://github.com/IntelRealSense/librealsense/blob/master/doc/t265.md#examples-and-tools |
Hi All Is there more that is needed on this thread? Thanks to @MartyG-RealSense for links to other threads with updates on this topic. |
Issue Description
Are you planning to add support to Kernel 4.19? In order to use the cameras in Raspberry 4 and Raspbian Buster.
I am getting the error of this issue: #2850
The text was updated successfully, but these errors were encountered: