-
Notifications
You must be signed in to change notification settings - Fork 76
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
Add Hailo8 support on pi5 machines #1202
base: master
Are you sure you want to change the base?
Conversation
At this moment, when building with OS_DEVELOPMENT=1, earlycon is added to kernel command line, however the current configuration is only valid on the Pi4 family. Using it with any other device type will make the kernel hang. This patch limits the configuration to Pi4, Pi400 and CM4. Change-type: patch Signed-off-by: Michal Toman <[email protected]>
At this moment the RPi5 image does not build properly, and CM5 and RPi500 are not supported at all. This patch does several things: * Bumps kernel to 6.6 on the Pi5 image * Bumps the balena bootloader kernel to 6.6 * Adds CM5 and RPi500 device trees to the RPi5 image It was necessary to backport the 6.6 recipe from meta-raspberrypi, as 6.6 is only available from scarthgap up, and balena-raspberrypi is still on kirkstone. RPi5, RPi500 and CM5 are therefore supported by a single device type. Change-type: minor Changelog-entry: Add support for CM5 and RPi500 Signed-off-by: Michal Toman <[email protected]>
Hi balena-os developers, very cool to see this is worked on! Just a comment, hailo 4.20.0 is available. Is there a reason you use 4.19.0 here? Looking forward to using this! |
Hi @n1mda yeah, I saw that 4.20 is available but planned to try align the version to what is officially shipped with raspberry Pi OS currently which today ships with 4.19.0, which means that installing this in your docker container doesn't require building the userspace libs from source, its just a matter of doing |
This PR introduces support for the hailo8 chip found in the raspberry pi AI Kits on the raspberrypi5 family of machines by adding the following components:
It depends on #1201 being merged to support kernel 6.6 on the pi5 first.
This can be tested from a container/app using the following dockerfile:
You should then be able to run
hailortcli scan
from within the container and have the device correctly detected.