![\"\"](\"https:\/\/rageworx.info\/wp-content\/uploads\/2024\/10\/Hailo_logo.png\"){kind=logo}
<\/p>\n<\/p>\n
Hailo-8 is<\/a><\/span> an AI accelerator device based on PCIe BUS. And I have a chance to testing with Rockchip RK3588.<\/p>\n Installed M.2 (M-Key) Hailo-8 module on NVMe slot of NanoPi6 (RK3588). It supports PCIe 4x lanes.<\/p>\n Hailo released version 4.18.0 driver<\/a><\/span> and APIs on their github<\/a><\/span>. And if you succeeded to load as like this: Hailo supports their own CLI, and it must be installed on the system to control Hailo-8 device. Then check Hailo-8 device running well with this : Found some pre-compiled HEF model (from ONNX) for RaspberryPI5 series. And RPI5 module is not Hailo-8, but I tested with this model as Hailo-8L.<\/p>\n Performance marked as average 115 and 116 (for streaming) fps.<\/p>\n Performance marked as average 355 fps.<\/p>\n Hailo-8 is a small chipset for enables HW based powerful AI acceleration for low powered ARM architecture systems. But thermal may a small issue …<\/p>\n And Hailo officially recommend to use heat sink.<\/p>\n And maximum thermal is argued as : <\/p>\n It maybe a good choice to acquire 26 TOPs AI power for small embedded system if has good thermal solution to prevent over heating up to 100\u2103.<\/p>\n","protected":false},"excerpt":{"rendered":" Hailo-8 is an AI accelerator device based on PCIe BUS. And I have a chance to testing with Rockchip RK3588. Installation Installed M.2 (M-Key) Hailo-8 module on NVMe slot of NanoPi6 (RK3588). It supports PCIe 4x lanes. Driver implementation Hailo released version 4.18.0 driver and APIs on their github. So… Read more »<\/a><\/p>\n","protected":false},"author":1,"featured_media":2689,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[800,5,735,3],"tags":[802,26,804,25,805],"class_list":["post-2687","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ai","category-development","category-linux-development","category-raphs","tag-ai","tag-driver","tag-hailo","tag-kernel","tag-rk3588"],"_links":{"self":[{"href":"https:\/\/rageworx.info\/index.php?rest_route=\/wp\/v2\/posts\/2687","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rageworx.info\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rageworx.info\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/rageworx.info\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/rageworx.info\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2687"}],"version-history":[{"count":0,"href":"https:\/\/rageworx.info\/index.php?rest_route=\/wp\/v2\/posts\/2687\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/rageworx.info\/index.php?rest_route=\/wp\/v2\/media\/2689"}],"wp:attachment":[{"href":"https:\/\/rageworx.info\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2687"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rageworx.info\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2687"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rageworx.info\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2687"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Installation<\/h2>\n
![\"\"](\"https:\/\/rageworx.info\/wp-content\/uploads\/2024\/10\/m2installed_1.jpg\")
<\/p>\nDriver implementation<\/h2>\n
\nSo I implemented kernel driver 4.18.0 for RK3588 kernel 6.1. It needs to modify some part of kernel sources. If you want to do this, follow this way.<\/p>\n\n
\n👉 \n\thailort_kdrv_v4.18.0_for_rk3588_kernel_6.1.tar.gz\t(407 downloads\t)\n<\/a>\n<\/li>\ndriver\/misc<\/code>, you can see a new driver directory driver\/misc\/hailort<\/code>.
\n👉 tar -xf ${downloaded.tar.gz} -C driver\/misc<\/code><\/li>\ndriver\/misc\/Kconfig<\/code>. to include hailort\/Kconfig<\/code> .\n\n
source drivers\/misc\/hailort\/Kconfig<\/code> before endmenu<\/code> line.<\/li>\n<\/ul>\n<\/li>\n\n
CONFIG_PCIE_BUS_DEFAULT<\/code>” as “y<\/code>“<\/li>\nCONFIG_HAILORT_PCIE<\/code>” to “m<\/code>” or “y<\/code>” (recommend as “m<\/code>“)<\/li>\n<\/ul>\n<\/li>\n.config<\/code>” file that enabled “CONFIG_HAILORT_PCIE=y|m<\/code>“.<\/li>\nPlace firmware to “\/lib\/firmware\/hailort”<\/h2>\n
\n
\/lib\/firmware\/hailort<\/code> and extract downloaded firmware in there.<\/li>\n<\/ul>\nCreate an udev rule file<\/h2>\n
\n
\/etc\/udev\/rules.d\/51-hailo-udev.rules<\/code> as sudoer.<\/li>\n
\n#Change mode rules for Hailo's PCIe driver<\/code>
\nSUBSYSTEM==\"hailo_chardev\", MODE=\"0666\"<\/code><\/li>\n<\/ul>\nCheck kernel driver load<\/h2>\n
![\"\"](\"https:\/\/rageworx.info\/wp-content\/uploads\/2024\/10\/kernel_drv_loaded_dmesg.jpg\")
<\/p>\nBuild Hailo CLI 11<\/h2>\n
\nNow you need to build Hailo CLI-11 from Here<\/a><\/span>.<\/p>\nhailortcli fw-control identify --extended<\/code>
\n![\"\"](\"https:\/\/rageworx.info\/wp-content\/uploads\/2024\/10\/hailocli-fw-info.jpg\")
<\/p>\nPerformance test<\/h2>\n
\n
YOLOv5-n-seg (for Hailo-8L)<\/h3>\n
![\"\"](\"https:\/\/rageworx.info\/wp-content\/uploads\/2024\/10\/hailo_running_test_for8L_YOLOv5nseg.jpg\")
<\/p>\nYOLOv6-n (for Hailo-8L)<\/h3>\n
![\"\"](\"https:\/\/rageworx.info\/wp-content\/uploads\/2024\/10\/hailo_running_test_for8L_YOLOv6n.jpg\")
<\/p>\nConclusion<\/h2>\n
\nAnd I impressed in their performance to handle YOLO in real-time.<\/p>\n![\"\"](\"https:\/\/rageworx.info\/wp-content\/uploads\/2024\/10\/RB00424X.jpg\")
<\/p>\n![\"\"](\"https:\/\/rageworx.info\/wp-content\/uploads\/2024\/10\/capture_hailo_pdf_thermal-960x441.png\")
<\/p>\n![\"\"](\"https:\/\/rageworx.info\/wp-content\/uploads\/2024\/10\/capture_hailo_pdf_themal_limit.png\")
<\/p>\n