Hello ​@pautu227 

Thanks for reaching us.

I tested both Ubuntu 24.04 and Raspberry Pi OS, but remember that at the moment you need to use Docker container for this.

The only setting you need to do in config.txt is:

Enable PCIe Gen3 by following the instructions in: 

• https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#pcie-gen-3-0

If you use a M.2 HAT different to the official Raspberry Pi HAT, you might need to add something extra. But that always appears in the documentation from the HAT’s manufacturer.

You can find all the details in https://support.axelera.ai/hc/en-us/articles/26362016484114-Bring-up-Voyager-SDK-in-Raspberry-Pi-5. I’d highly recommend to go through it :)

Hope this info helps,

Victor

Welcome on board!  . What kind of project are you working on ​@pautu227?

​@Victor Labian Thanks for fast response.

 

I'm using the official Raspberry Pi M.2 HAT+ (M-key) from RaspberryPi.dk with a Raspberry Pi 5. I’ve added the following line to config.txt:

dtparam=pciex1_gen=3

I also followed the Docker-based installation steps provided by Axelera. However, the Metis card does not appear (e.g., no /dev/metis-0:86:0 device is created).

The same m2 metis board does work correctly on my Gigabyte G292-Z20 server, where I get the following output:

refreshing pcie and firmware 0000:86:00.0 : Axelera AI Metis AIPU (rev 02) Device 0: metis-0:86:0 board_type=m2 fwver='v1.2.5' clock=800MHz(0-3:800MHz) mvm=0-3:100% Installation complete. To activate the environment...

However, I tried the board on other systems:

• Jetson Orin Nano

• Odroid M1

• Raspberry Pi 5 with M.2 HAT+

• Lenovo M910q

And on all of these, I get an error like:

Failed to: refreshing pcie and firmware

My Question:

Could there be different versions of the Metis M.2 card (e.g., firmware, revision, compatibility) that cause this issue on ARM and some x86 devices? Or are there specific PCIe, power, or BIOS/firmware requirements that must be met for the card to initialize correctly?

Great to be here!
I’m building observation system with two sensors RGB + THERMAL. Doing custom object detection and object segmentation with YOLO

Hello ​@pautu227 

Thanks for sharing the info.

Just to confirm, you are using Docker container, right?

Let’s take these actions:

1. In Raspberry Pi 5 can you try doing a reboot and see if it helps?
2. ​@pautu227 can you try following the troubleshooting guide in https://support.axelera.ai/hc/en-us/articles/26261515755538-PCIe-Troubleshooting-Guide and share with us the output you see for the different suggestions in the guide? Let’s start with the Raspberry Pi 5 with the following sections in the guide (can you also specify which OS you are using?):
   1. Check lspci output
   2. Update PCI IDs
   3. Remove and rescan devices with axdevice Voyager SDK tool
   4. Check the driver is loaded
   5. Check Firmware version of your Metis card uses triton_multi_ctx]
   6. Check Board Controller version of your Metis card uses triton_multi_ctx]

Thanks beforehand,

Victor

Setup:

Raspberry pi 5b 4gb 
Official Raspberry pi m2.hat+
Official power supply

Debian Bookworm 64bit
USB Boot from SSD

1. Reboot doesn’t help

2.1 lspci output: 

0002:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2712 PCIe Bridge (rev 21)
0002:01:00.0 Ethernet controller: Raspberry Pi Ltd RP1 PCIe 2.0 South Bridge

paulius@raspberrypi:~ $ lspci -tv
-+-r0000:00]-
 \-r0002:00]---00.0--01]----00.0  Raspberry Pi Ltd RP1 PCIe 2.0 South Bridge

if I connect nvme drive - disk drive is present but no Metis present.
lspci -tv
-+-<0000:00]-
 +-<0001:00]---00.0-001]----00.0  KIOXIA Corporation NVMe SSD Controller BG4 (DRAM-less)
 \-s0002:00]---00.0-:01]----00.0  Raspberry Pi Ltd RP1 PCIe 2.0 South Bridge

Any ideas?

 

Setup:

Raspberry pi 5b 4gb 
Official Raspberry pi m2.hat+
Official power supply

Debian Bookworm 64bit
USB Boot from SSD

 

1. Reboot doesn’t help

2.1 lspci output: 

0002:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2712 PCIe Bridge (rev 21)
0002:01:00.0 Ethernet controller: Raspberry Pi Ltd RP1 PCIe 2.0 South Bridge

paulius@raspberrypi:~ $ lspci -tv
-+- 0000:00]-
 \- 0002:00]---00.0--01]----00.0  Raspberry Pi Ltd RP1 PCIe 2.0 South Bridge

if I connect nvme drive - disk drive is present but no Metis present.
lspci -tv
-+-b0000:00]-
 +-b0001:00]---00.0-001]----00.0  KIOXIA Corporation NVMe SSD Controller BG4 (DRAM-less)
 \-)0002:00]---00.0-:01]----00.0  Raspberry Pi Ltd RP1 PCIe 2.0 South Bridge

Any ideas?

 

​@Victor Labian ​@Spanner  backing to initial topic. Any ideas why I cannot see Metis on PCIe?

Hi ​@pautu227! I just found on the RPi forums about it sometimes negotiating itself back down to PCIe Gen2 in some circumstances (in that case it was a cable issue in the end). It did have a quick check to make sure Gen3 is running if you wanted to make extra sure about that?

sudo lspci -vv | grep -i 'LnkSta'

… should give you something like:

LnkSta: Speed 8GT/s (ok), Width x1 (ok)

If it says 5GT/s instead of 8GT/s, it’s still in Gen2 apparently. Worth a quick test?

Hi ​@pautu227 ,

We have tested Raspberry Pi 5 on Raspberry Pi OS and on Ubuntu 24.04 both with Docker.

We have tested booting from SD cards but not from SSD.

I would recommend you to:

• Remove SSD
• Get a micro SD card 
• Use RPi imager app to image the card with RPi OS
• Then follow the guide in https://support.axelera.ai/hc/en-us/articles/26362016484114-Bring-up-Voyager-SDK-in-Raspberry-Pi-5 step by step. I recommend you to keep track of all your steps for debugging purposes.

This approach have been tested different times, so we expect it to work. If this works for you then we can test two things:

1. Debian on SD card
2. Boot from SSD but with RPi OS

That way we can see if the issue comes from using Debian or from booting from SSD.

Kind regards,

Victor