Hailo-10H detected by lspci but not by HailoRT 5.4.0

General Discussion
1

Hello,

We have one Hailo-10H module that is visible in lspci as a PCIe device, but it is not recognized by HailoRT 5.4.0 and does not appear in hailortcli scan.

Other Hailo-10H modules work normally on the same host and PCIe environment.

Could you please confirm:

  • whether there is any known issue or reported case where a Hailo-10H device is detected by lspci but fails to initialize with HailoRT 5.4.0;

  • whether there is any recommended fix, firmware update, or recovery procedure for this case.

If needed, we can provide the lspci, dmesg, and Hailo driver logs for the affected module.

Thank you.

Best regards,
Jusung Kang

Additional update:

We reproduced the issue with the affected Hailo-10H 4GB module on the same PCIe slot and host where another module works correctly.

The device is visible in lspci as:



01:00.0 Co-processor: Hailo Technologies Ltd. Device 45c4 (rev ff)

However, HailoRT does not successfully initialize it. The Hailo 5.4.0 driver proceeds through PCIe BAR mapping, loads customer_certificate.bin and scu_fw.bin, reads Board SKU-ID: 1, and successfully transfers u-boot-1.dtb.signed.

The initialization then fails with:



Timeout waiting for firmware file
Failed writing SOC firmware on stage 2
Firmware load failed
Failed activating board -110
probe of 0000:01:00.0 failed with error -110

As a result, the device does not appear in hailortcli scan / runtime access, even though PCIe enumeration itself succeeds.

Could you please confirm whether this Stage 2 firmware boot timeout (-110) is a known issue, and whether there is any recommended firmware recovery, update, or diagnostic procedure for this case?

One additional point: this affected module is reported as rev ff by lspci, which differs from the working modules we tested.

Additional Info

Device enumerates normally as PCIe rev 01 after a cold boot.
During Hailo-10H Stage 2 boot, after u-boot-1.dtb.signed is transferred, the device becomes non-responsive. Its PCI configuration space reads as 0xff, the upstream link falls from 8 GT/s to 2.5 GT/s, and it does not recover after 30 seconds. The same behavior was also observed with HailoRT 5.3.