Skip to main content
Question

Can not Enable Update

  • January 5, 2026
  • 7 replies
  • 87 views

Hi,

I have 3 axelera metis m2 device. I could not enable update for all of them. I have Voyager SDK 1.5.2 version that installed successfully. When i enter the command “./enable_bootloader_update.sh" it gives an error such as “Device communication timed out” and “Failed to load firmware”. I disabled the IOMMU option in BIOS and disabled the secure boot. My device is seen as “03:00.0 Processing accelerators: Axelera AI Metis AIPU (rev 02)" in the lspci output. Also when i enter the “axdevice” command it says : "[libtriton_linux.c:1313] Device communication timed out: device did not respond within 1 seconds. (0)
WARNING: Failed to get valid board type for device metis-0:3:0 got 8
Device 0: metis-0:3:0 board_type=unknown (not responding)"

How can i solve this problem ? Can you help me ? 

The full terminal output of the command is that : 

(venv) ysf@ysf:~/Desktop/voyager-sdk$ ./enable_bootloader_update.sh
Firmware Flasher - Extracting files...
Extracting firmware files...
Files extracted successfully!

Starting firmware flashing sequence...

Step 1: Loading bootloader update...
[libtriton_linux.c:1313] Device communication timed out: device did not respond within 1 seconds. (0)
Could not query firmware version.
WARNING: Firmware version check override forced, continuing despite incompatibility.
Fail to get logtrace area. Make sure that host and device versions are aligned
[libtriton_linux.c:1313] Device communication timed out: device did not respond within 1 seconds. (0)
Could not query firmware version.
WARNING: Firmware version check override forced, continuing despite incompatibility.
Fail to get logtrace area. Make sure that host and device versions are aligned
[libtriton_linux.c:1313] Device communication timed out: device did not respond within 1 seconds. (0)
Failed to load firmware.

7 replies

Spanner
Axelera Team
Forum|alt.badge.img+2
  • Axelera Team
  • January 5, 2026

Hi there ​@meva-ysf !

Hmm, odd that it’s not working for any of them. Looks like a PCIe communication issue with the host. To help us dig deeper, can you provide the following?

  • What host systemare you using?
  • What's your OS and kernel version?
  • Driver version: cat /sys/class/metis/version
  • Is the driver loaded? lsmod | grep metis
  • And are all three in one host system, or in individual computers?

👍


  • Author
  • Cadet
  • January 9, 2026

Thank you for your interest ​@Spanner 

I connected the M2 Metis device to my Lenovo ThinkStation P2 Tower computer. All three devices are installed in this computer.

Ubuntu Version : 22.04.5 LTS x86_64

Kernel version   : 6.8.0-90-generic.

CPU                   : Intel i7-14700K (28) @ 5.500GHz. 

ysf@ysf:~$ cat /sys/class/metis/version -> 1.4.4

ysf@ysf:~$ lsmod | grep metis -> metis                 147456  0


Forum|alt.badge.img+2

Hi ​@meva-ysf , can you provide the output of running `sudo dmesg` as a txt file here so we can analyse it and look for errors?

 


  • Author
  • Cadet
  • January 9, 2026

Hi, thank you for your interest ​@Victor Labian 

The output of command “sudo dmesg” is in the dmesg_output.txt file. 

 


Spanner
Axelera Team
Forum|alt.badge.img+2
  • Axelera Team
  • January 10, 2026

Morning ​@meva-ysf , thanks for sharing that!

@Victor Labian is waaaaaay better at this than I am, but I had a quick butcher’s at the output file, and from a glance it looks like only one of the three M.2 boards is being enumerated - are all three slots turned on in the system BIOS? Seems probably that they are, but worth double checking maybe.

Alternatively, I wonder if it’s worth rotating them, to see if it’s a specific card that’s working, or a specific slot?

And a full power cycle reboot followed by an axdevice --refresh never hurts, although I suspect you’ve done that multiple times already 😅


  • Author
  • Cadet
  • January 12, 2026

Good morning! ​@Spanner  I hope you're having a good day. I’ve currently installed only one of the three Metis cards. When i tried the other two one by one, I got the same result for all of them. I'm swapping the slot for the current card and re-sharing the dmesg output. Here is also the output for axdevice --refresh

(venv) ysf@ysf:~/Desktop/voyager-sdk$ axdevice --refresh 
[sudo] password for ysf: 
0000:02:00.0 : Axelera AI Metis AIPU (rev 02)
[libtriton_linux.c:1313] Device communication timed out: device did not respond within 1 seconds. (0)
WARNING: Failed to get valid board type for device metis-0:2:0 got 8
[libtriton_linux.c:1313] Device communication timed out: device did not respond within 1 seconds. (0)
ERROR: Failed to load runtime stage0: /opt/axelera/device-1.5.2-1/omega/bin/start_axelera_runtime_stage0.bin
ERROR: AXR_ERROR_CONNECTION_ERROR: Failed to load runtime stage0: /opt/axelera/device-1.5.2-1/omega/bin/start_axelera_runtime_stage0.bin
 


Forum|alt.badge.img+2

Hi ​@meva-ysf ,

Thank you for sharing the output of sudo dmesg.

I have inspected it and I can see that:

  - Driver loads successfully: "Triton Linux Driver, version 1.4.4, init OK" (line 1215)
  - Device detected and registered correctly
  - MSI interrupts registered (32 vectors)
  - Memory BARs mapped successfully
  - No DMA errors, no timeout errors, no communication failures in dmesg

Can you share the output for the following command with us?

sudo lspci -vvv -s 02:00.0
 

@meva-ysf Do you have by any chance another PC in which you can test the Metis card to see if there is the same issue?