Skip to main content
Question

Firmware loading error on Windows

  • June 25, 2026
  • 1 reply
  • 8 views

I received my Metis M.2 card yesterday and tried it out on Windows 11 on an ACEMAGIC F3A AMD Ryzen AI 9 HX 370 Mini PC using the instructions in https://docs.axelera.ai/sdk/user-guides/windows-setup/.  I had some troubles with the WSL part of the setup so I decided to skip that, and got to step 5 with the driver properly installed in device manager and the Axelera Windows packages installed. The axrunmodel sample returns the following output: 

[libaxldev.c:419] Firmware load address 0xffffffffffffffff exceeds 32-bit address space on Metis. WARNING:axelera.runtime:Failed to load runtime stage0: C:\AxeleraDevice-1.7.0\opt\axelera\device\omega\bin\start_axelera_runtime_stage0.bin [AxeleraDevice.cpp:455] Failed to get board DDR size. WARNING:axelera.runtime:Failed to get SW throttling from device metis-0:0:0 WARNING:axelera.runtime:Failed to get HW throttling from device metis-0:0:0 WARNING:axelera.runtime:Failed to get freq downscaling from device metis-0:0:0 [utils.c:264] sysctl_get_datastream_area: bad magic 0xffff (expected 0xf0f0) ERROR:axelera.runtime:Invalid log source: sysctrl C:\users\nicov\Code\voyager-sdk\build\resnet50-imagenet-onnx\resnet50-imagenet-onnx\1\model.json,FAIL: AXR_ERROR_INVALID_ARGUMENT: Invalid log source: sysctrl

I also tried to get some info about the hardware: 

axdevice -v INFO: Found PCI device: Instance ID: PCI\VEN_1F9D&DEV_1100&SUBSYS_11001F9D&REV_00\4&c1676ec&0&0011 Device Description: Metis Device Class Name: ComputeAccelerator Class GUID: {f01a9d53-3ff6-48d2-9f97-c8a7004be10c} Manufacturer Name: Axelera AI B.V. Status: Started Driver Name: oem27.inf INFO: Found AIPU driver: oem27.inf INFO: Current firmware version \xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff != required version v1.7.0 INFO: Device firmware version is not compatible, loading now [libaxldev.c:419] Firmware load address 0xffffffffffffffff exceeds 32-bit address space on Metis.

 

Somehow it seems it does not have any firmware loaded?

Maybe there is some BIOS incompatibility, after shutdown I couldn't restart the computer again, and after removing the M.2 Metis card it booted properly again.

The machine also seemed rather slow with the M.2 card installed.

Any ideas on how to proceed? I could try installing Linux, but the boot issue seems like there is something else in play. Unfortunately I don't have a spare system with a free M.2 slot to try it in a different hardware config.

I am just using Windows for testing purposes, ultimately I want to run it (if my evaluation (and corresponding software development) works out well) on an SBC like an RK3588 board or so.

 

1 reply

Spanner
Axelera Team
Forum|alt.badge.img+3
  • Axelera Team
  • June 25, 2026

Hi ​@nicov ! Thanks for the detailed logs, it always helps to see those.

I think our key clue is that every value the SDK reads back is 0xff / 0xffffffffffffffff (firmware version, board DDR size, the bad magic 0xffff line), which suggests the PCIe link to the card not coming up properly. Windows enumerates the device and binds the driver, but it doesn’t look like the host can actually read the card's memory over PCIe. And if that’s the case, it’s not so much that the firmware is missing as the SDK can't talk to the card to read or load it.

That’d tally with the PC refusing to reboot with the card installed and running slowly when it does, then being fine once you’ve removed it. So I’m feeling like it’s the M.2 slot / PCIe configuration on that specific mini PC...

Here’s something quick to try first:

  • Go into the BIOS and check the M.2 slot's mode. A quick search suggests a lot of mini-PC M.2 slots are set to SATA/NVMe-storage-only or limited PCIe lanes. If there's a setting for PCIe mode / lane configuration / "M.2 mode" or something for that slot, set it to PCIe (and the widest lane width available), then reboot and re-run axdevice -v.

Let’s see f that helps us narrow it down and then go from there! 👍