Hi,
I’m experiencing HAILO_COMMUNICATION_CLOSED(62) error with Hailo-10H on
Jetson AGX Orin. All software components are correctly installed and the
firmware loads successfully, but hailortcli fw-control identify fails.
Environment
- Hardware: NVIDIA Jetson AGX Orin Developer Kit (64GB)
- Hailo device: Hailo-10H (M.2, via PCIe expansion board)
- OS: Ubuntu 22.04.5 LTS
- Kernel: 5.15.185-tegra (aarch64)
- JetPack: 6.2.2 (L4T R36.5.0)
- CUDA: 12.6
- HailoRT: 5.3.0
- Driver: hailo1x_pci 5.3.0 (DKMS built)
What works
PCIe device recognized:
$ lspci | grep -i hailo
0005:01:00.0 Co-processor: Hailo Technologies Ltd. Device 45c4 (rev 01)
Firmware loads successfully (~1.7 seconds):
[10.346632] hailo1x 0005:01:00.0: SOC Firmware Batch loaded successfully
[10.346640] hailo1x 0005:01:00.0: Firmware loaded in 1724 ms
[10.363675] hailo1x 0005:01:00.0: Device created at /dev/h1x-0
Device files created:
/dev/h1x-0 (crw-rw-rw-)
/dev/hailo0 → /dev/h1x-0 (symlink)
hailortcli scan works:
$ hailortcli scan
Hailo Devices:
[-] Device: pci/0005:01:00.0
What fails
$ hailortcli fw-control identify
[HailoRT] [error] CHECK_SUCCESS failed with status=HAILO_COMMUNICATION_CLOSED(62)
[HailoRT] [error] CHECK_SUCCESS failed with status=HAILO_COMMUNICATION_CLOSED(62)
[HailoRT] [error] CHECK_SUCCESS failed with status=HAILO_COMMUNICATION_CLOSED(62) - Failed to set default notification callbacks for Device HRPC-client
[HailoRT CLI] [error] CHECK_SUCCESS failed with status=HAILO_COMMUNICATION_CLOSED(62)
[HailoRT CLI] [error] CHECK_SUCCESS failed with status=HAILO_COMMUNICATION_CLOSED(62)
Firmware boot sequence (from dmesg)
The firmware loads the following files in sequence:
- customer_certificate.bin
- scu_fw.bin
- u-boot-0.dtb.signed
- u-boot-spl.bin
- fitImage (11MB Linux kernel image)
- image-fs (100MB Linux root filesystem)
This looks like a full Linux boot sequence rather than NPU-only mode.
Is this expected for Hailo-10H? Or should there be a different firmware
for NPU-only mode?
Attempted fixes (all failed)
- Module reload (modprobe -r / modprobe hailo1x_pci)
- force_hailo_pcie_boot_mode_over_bars=1
- force_hailo10h_legacy_mode=1
- Cold boot (DC adapter disconnected for 1+ minute)
- USB virtual ethernet activation (l4tbr0, usb0, usb1) - NO-CARRIER
Network interfaces (no Hailo Linux connection found)
usb0: <NO-CARRIER,BROADCAST,MULTICAST,UP> master l4tbr0 state DOWN
usb1: <NO-CARRIER,BROADCAST,MULTICAST,UP> master l4tbr0 state DOWN
ping 192.168.55.2 → 100% packet loss
ping 192.168.7.2 → 100% packet loss
Driver info
$ modinfo hailo1x_pci
filename: /lib/modules/5.15.185-tegra/updates/dkms/hailo1x_pci.ko
version: 5.3.0
vermagic: 5.15.185-tegra SMP preempt mod_unload modversions aarch64
Questions
- Is the firmware boot sequence (fitImage + image-fs) expected for
Hailo-10H in NPU mode, or is this a Linux/AI Vision Module mode? - If this is Linux mode, how do I switch to NPU mode for use with
hailortcli and HailoRT API? - Are there specific configurations required for Hailo-10H on
Jetson AGX Orin with JetPack 6.2.2?
I found a similar case where downgrading HailoRT version resolved the issue (4.19→4.18 on Windows). Is there a known compatibility issue between HailoRT 5.3.0 and Hailo-10H firmware on Jetson platforms?
Any help would be greatly appreciated. Thank you.