Hi @Yu_Eunsang 
The empty column is not a mistake in the table. The tool was renamed to Hailo
Accelerator Integration Tool and it follows its own release cycle, so it does not
ship with the suite anymore — you have to search “integration” in the Developer Zone
downloads. The last version I have seen mentioned is v1.20, tied to HailoRT 4.20.
And that tie is a hard one, it is not just a documentation thing. The tool links
against the exact libhailort version. On 4.23 the library is installed like this,
with no backward symlink:
$ ls -l /usr/lib/libhailort.so*
lrwxrwxrwx /usr/lib/libhailort.so -> /usr/lib/libhailort.so.4.23.0
-rw-r--r-- /usr/lib/libhailort.so.4.23.0
So a prebuilt tool made for 4.20 will fail with libhailort.so.4.20.0: cannot open shared object file. The same thing happened here with 1.19 running on 4.20. You can
rebuild the tool from source pointing the CMakeLists at 4.23, but I did not test that.
That said, if what you need is the tests and not the tool itself, hailortcli ships
with 4.23 and covers most of them. This is on a Hailo-8L M.2, HailoRT 4.23.0, Ubuntu:
$ hailortcli run yolo26s_hailo8l.hef -t 10 --measure-temp
Network group: yolo26s
Frames count: 564
FPS: 56.21
Send Rate: 552.52 Mbit/s
Recv Rate: 635.97 Mbit/s
Device: 0000:06:00.0
Minimum chip temperature: 40.9077C
Average chip temperature: 42.5356C
Maximum chip temperature: 43.3865C
Send/Recv Rate is the PCIe traffic of the real inference, so it also works as a
bandwidth check. For a stress test you only raise -t (-t 172800 for 48h). And
hailortcli benchmark <hef> gives you FPS and latency in one run:
FPS (hw_only) = 56.0163
(streaming) = 57.41
Latency (hw) = 16.1918 ms
One warning, power did not work on my board:
[HailoRT CLI] [error] CHECK failed - Power measurement not supported.
Disable the power-measure option
--measure-power needs a board exposing the DVMs and --measure-current needs M.2
with overcurrent protection — mine has neither, so if you need power numbers that
is the part you cannot replace with hailortcli. I only ran this on Linux, I don’t
know if the Windows build behaves the same.
Hope this helps!