OneAPI for Agilex 7 I-Series Dev Kit: aocl diagnose acl0 and board_test sample fail

[gustifix2]

Hello!

This is a follow up to my previous post.

I am following the oneAPI ASP Getting Started User Guide for the Agilex 7 I-Series Development Kit (2x R-Tile, 1x F-Tile) . At step 2.5.3 Initialize Board and Run Diagnostic Test `aocl diagnose` succeeds but `aocl diagnose acl0` fails. I also tried the `board_test` sample in the next section of the guide. Both fail with the same error:

/nfs/site/disks/hld_runners_2/dynamic/alxa_kress/_work/applications.fpga.oneapi.stella/applications.fpga.oneapi.stella/external/opencl-fpga-runtime/src/acl_hal_mmd.cpp:2061: void acl_hal_mmd_status_handler(int, void*, aocl_mmd_op_t, int): Assertion `status == 0' failed.

As mentioned in the last post, I tried using the pre-compiled FIMs from https://github.com/OFS/ofs-agx7-pcie-attach/releases/tag/ofs-2024.2-1. The default one (iseries-dk-images_ofs-2024-2-1.tar.gz) leads to the same error in step 2.5.1 that my last post was originally about. The other two (iseries-dk-1link-images_ofs-2024-2-1.tar.gz and iseries-dk-2link-images_ofs-2024-2-1.tar.gz) work but also fail `aocl diagnose acl0` and `board_test` like the self-built FIM.

That is why I don't think the FIM is the problem and I am investigating the other parts of the stack now. So far I tried the latest release of the OPAE SDK (2.14.0-1) and the latest commit of linux-dfl-backport instead of the versions mentioned in the guide. This did not change anything about the errors.

Next I'll take a closer look at the OpenCL runtime source code where the error message stems from (acl_hal_mmd_status_handler) and try debugging the `board_test` and other oneAPI samples with GDB to narrow down where in the software stack the problem occurs.

I will post an update as soon as I find anything new, but I'd appreciate it if you could help me already with the information provided so far. Thanks! I also attached the output of `aocl diagnose` and `board_test`.

Best regards!

Felix

[BoonBengT_Intel]

Hi @gustifix2,

Thank you for posting in Intel community forum and hope all is well.

Noted on the situation and just to updated, we have contacted the relevant team on the following issues mention.

Will get back to you as soon as possible once we gotten an updates.

Thank you for the patients.

Best Wishes

BB

[gustifix2]

Hello,

I couldn't really narrow down the cause of the error and I'm not sure the OpenCL runtime code is the right place to look. Do you have any recommendations how to proceed from here?

Thanks and best regards!

Felix