Hailo8 runs the Yolo detection program in Hef format and freezes occasionally

Hello everyone! I’m running the Yolo detection program on a Raspberry Pi with Hailo 8 as the acceleration module. After about half an hour of operation, the detection froze . When I restarted, the system failed to detect the Hailo 8 module. Does anyone know why this happened? Is there a hardware issue? Could it be related to voltage or connectivity problems? Or perhaps other factors?(I’ve encountered similar issues when running Hailo 8L.)

error:( the detection froze and I operate to exit it)

HailoRT] [warning] Failed to acquire buffer because the buffer pool is empty. This could be caused by uneven reading and writing speeds, with a short user-defined timeout. (timeout=10000ms)
[HailoRT] [error] Non-recoverable Async Infer Pipeline error. status error code: HAILO_TIMEOUT(4)
[HailoRT] [error] Shutting down the pipeline with status HAILO_TIMEOUT(4)
[HailoRT] [error] CHECK_SUCCESS failed with status=HAILO_TIMEOUT(4) - Can’t handle inference request since pipeline status is HAILO_TIMEOUT(4).
[HailoRT] [error] CHECK_SUCCESS failed with status=HAILO_TIMEOUT(4)
QoS message received from source
CHECK_EXPECTED failed with status=4
CHECK_SUCCESS failed with status=4
[HailoRT] [warning] Failed to acquire buffer because the buffer pool is empty. This could be caused by uneven reading and writing speeds, with a short user-defined timeout. (timeout=10000ms)
[HailoRT] [critical] Failed to acquire from pool in LastAsyncEl0NmsPPMuxEl0YOLOV8-Post-Process element!
[HailoRT] [error] CHECK_SUCCESS failed with status=HAILO_TIMEOUT(4)
[HailoRT] [error] CHECK_SUCCESS failed with status=HAILO_TIMEOUT(4)
[HailoRT] [error] CHECK_SUCCESS failed with status=HAILO_TIMEOUT(4)
[HailoRT] [error] CHECK_SUCCESS failed with status=HAILO_TIMEOUT(4)
[HailoRT] [error] CHECK_SUCCESS failed with status=HAILO_TIMEOUT(4)
[HailoRT] [error] CHECK_SUCCESS failed with status=HAILO_TIMEOUT(4)
[HailoRT] [error] CHECK_SUCCESS failed with status=HAILO_TIMEOUT(4)
[HailoRT] [critical] Dequeueing external buffers failed with status HAILO_TIMEOUT(4)
QoS message received from source
Error: gst-resource-error-quark: Output window was closed (3), ../sys/xvimage/xvimagesink.c(586): gst_xv_image_sink_handle_xevents (): /GstPipeline:pipeline0/GstFPSDisplaySink:hailo_display/GstAutoVideoSink:autovideosink0/GstXvImageSink:autovideosink0-actual-sink-xvimage
Shutting down… Hit Ctrl-C again to force quit.
Exiting with error…
System shutdown complete

error:(restart)

(venv_hailo_rpi5_examples) junyan@raspberrypi:~/hailo/hailo-rpi5-examples $ source setup_env.sh
Setting up the environment…
Setting up the environment for hailo-tappas-core…
TAPPAS_VERSION is 3.31.0. Proceeding…
You are in the venv_hailo_rpi5_examples virtual environment.
TAPPAS_POST_PROC_DIR set to /usr/lib/aarch64-linux-gnu/hailo/tappas/post_processes
[HailoRT] [error] CHECK failed - Failed to open device file /dev/hailo0 with error 6
[HailoRT] [error] CHECK_SUCCESS failed with status=HAILO_DRIVER_OPERATION_FAILED(36)
[HailoRT] [error] CHECK_SUCCESS failed with status=HAILO_DRIVER_OPERATION_FAILED(36)
[HailoRT] [error] CHECK_SUCCESS failed with status=HAILO_DRIVER_OPERATION_FAILED(36)
[HailoRT CLI] [error] CHECK_SUCCESS failed with status=HAILO_DRIVER_OPERATION_FAILED(36)
Error: Device Architecture not found. Please check the connection to the device.

Hey @Ethan ,

Welcome to the Hailo Community!

Looks like you’re running into a connectivity issue where the system can’t open the device. This could be a couple of things - might be a kernel compatibility problem or just a general connectivity hiccup.

Mind running these commands for me so I can take a look at what’s going on? Just paste the output here when you get a chance:

uname -r
ls -l /dev/hailo*
dmesg -T | egrep -i 'hailo|pcie|aer|nvme|reset|link|voltage|throttl'
lspci -nn | egrep -i '1e60|hailo|accel'
hailortcli scan
hailortcli fw-control identify

Let me know what you find and we’ll get this sorted out for you!