Axelera Embedded

Hi,For context, I am using the Axelera Embedded 110m module (Metis AIPU) on a NanoPC-T6 Plus board.Please note that I am using the NanoPC-T6 Plus (LPDDR5 architecture), not the standard NanoPC-T6 (LPDDR4X). The official image provided for the standard NanoPC-T6 does not resolve the PCIe memory allocation failure (error -12) on the T6 Plus due to hardware and Device Tree differences between the two boards.I have tested the official Ubuntu 22.04 and Ubuntu 24.04 OS images provided on the official NanoPC-T6 Plus wiki page, as well as the Armbian 26.8.3 NanoPC LTS and suggested joshuariek image, but the issue persists on all of them.Here are the troubleshooting steps I have attempted so far: Added the recommended kernel parameters (pci=realloc=on and pcie_aspm=off) to the boot configuration. Decompiled and manually updated the ranges property in the Device Tree (.dtb) to expand the non-prefetchable MMIO window for the PCIe controller node. Performed a full cold power cycle (completely

I am trying to get the Axelera Metis M.2 module working on a NanoPC-T6 Plus board powered by the Rockchip RK3588 SoC running Ubuntu 22.04 (Linux kernel 5.10.0-1012-rockchip / ARM64).(I installed image file in this link https://support.axelera.ai/hc/en-us/articles/31859388491794-Bring-up-Voyager-SDK-in-NanoPC-T6?_gl=1*3zteth*_gcl_au*MTc5ODEwMTM1MC4xNzg3NzI0Mjgx because I have tested other OS images provided on the official NanoPC-T6 Plus wiki, but the issue persists, indicating a known PCIe memory allocation bug within the Ubuntu 22.04 kernel for this platform.)However, the driver fails to probe the device due to PCI resource assignment failure (ENOMEM / error -12).1. Device Identification & lspci StatusThe PCIe device is visible on the bus (0000:01:00.0), but the Linux kernel fails to assign memory resources (MMIO) to Region 0 and Region 2:$ lspci -vv -s 0000:01:00.0 | grep -iE 'Region|Memory|flags' Region 0: Memory at <ignored> (64-bit, non-prefetchable) [disabled] Region 2:

Help me is tha work

I recently acquired a Metis M.2 module and was so excited to get started with it. To my horror, I installed it into a standard, modern x86 mini PC (with power disconnected, all by the books), and the system was bricked upon my first attempt to boot. At first, I thought maybe the M.2 slot on the system was not providing adequate power for the device, and to the benefit of the Metis, I decided to try another host system. HUGE mistake. The same thing happened with a LattePanda x86 SBC, confirmed to have enough power to the M-key M.2 slot. These systems are not cheap, so to say I am disappointed is an incredible understatement.  Maybe I’m just not understanding where to look for host system specs, but it doesn’t seem like this issue is warned against anywhere in your docs or on the community page here. Has anyone else had this problem? I’m down two systems, so if someone could please tell me with certainty which system I CAN reliably plug this thing into, I would be very appreciative. EDIT

We want to connect multiple camera to detect object and track it. Each camera at different location. We could do that with Yolo. In Axelera, we can do it with 1 camera. When 2nd camera is started, error is thrown. Please advice 

On a x64 based system with a Metis M.2, i am trying to do a firmware update for the device but getting an error.(axelera-env) devuser@linuxdev:~/voyager-sdk$ axdevice interactive_flash_updateWARNING: AXELERA_DEVICE_DIR environment variable not set.Using AXELERA_DEVICE_DIR=/home/devuser/voyager-sdk/axelera-env/lib/python3.12/site-packages/axelera/omegaWARNING: AIPU_RUNTIME_STAGE0_OMEGA environment variable not set.Using AIPU_RUNTIME_STAGE0_OMEGA=/home/devuser/voyager-sdk/axelera-env/lib/python3.12/site-packages/axelera/omega/bin/start_axelera_runtime_stage0.bin>>> Metis Flash Update Script>>> =========================>>> Auto-detecting and updating all connected devices...>>> Detected 1 device(s) from axdevice>>> ==============================================>>> Found 1 device(s):>>> - metis-0:81:0>>> ==============================================>>> Device metis-0:81:0 needs firmware update (current: 1.2

Hello, i just got my m.2 card and on my AMD64 desktop workstation, the Metis M.2 AIPU does not survive an S3(suspend-to-RAM) cycle. After resume, every large DMA transfer to the cardfails permanently. Only a full cold power-cycle restores function — a warmreboot is not enough. This makes the card unusable on any normal desktop,where suspend/resume is the standard daily workflow.I narrowed this down together with Claude Opus 4.8 (Anthropic) over a detaileddebugging session. Full diagnosis below.## Hardware / Software- Host: AMD Ryzen, B850 platform, RTX 3090 in primary slot- OS: CachyOS (Arch-based), kernel 7.0.12 (Clang/LLVM-built), Secure Boot off- Metis M.2 AIPU, PCIe 0000:0c:00.0 (1f9d:1100 rev 02), Gen3 x4- Driver: axelera-driver release/v1.6 (module version 1.4.17), built with  make LLVM=1, DKMS-managed- SDK: Voyager 1.6.1 (axelera-rt / devkit), inference via distrobox/Ubuntu 24.04## Reproduction1. Cold boot. Run inference (yolo26s-coco-onnx, fakevideo) → works, ~529 fps.2. system

Dear Axelera Support, I am attempting to install Voyager SDK on the radxa rock 5T board with the axelera AI Accelerator M.2. While the SDK suggests using Ubuntu 22.04, I could not find a version of ubuntu for the 5T (https://github.com/DHDAXCW/ubuntu-rockchip-rk3588?tab=readme-ov-file)  I have reviewed previous threads but either they’re not fixed (https://community.axelera.ai/support-central-47/subject-metis-aipu-detected-on-pcie-but-not-responding-stage0-load-failure-on-rk3588-compute-board-voyager-sdk-1-5-3-1280) or there’s an ubuntu version available (https://community.axelera.ai/metis-pcie-7/pcie-connection-doesn-t-work-with-radxa-rock-5b-1101)  I’m not exactly sure if I can use the ubuntu image meant for the Radxa Rock 5B+ on the Rock 5T? radxa@rock-5t:~$ cat /etc/os-releasePRETTY_NAME="Debian GNU/Linux 12 (bookworm)"NAME="Debian GNU/Linux"VERSION_ID="12"VERSION="12 (bookworm)"VERSION_CODENAME=bookwormID=debian radxa@rock-5t:~$ cat /sys/class/metis/version1.4.16 Installation of S

Is there a possibility of having voyager SDK installed on laptop running Linux and having Metis m2 card connected to laptop over some adapter?My setup is Linux laptop and Axelera Metis m2 card seated in a USB4 M.2 NVMe SSD enclosure from Ugreen (input 5V 3A max) that is connected to laptop via thunderblot usb cable.I have voyager SDK installed and the OS recognizes the axelera device and I have been able to communicate with it. But when running actual detection processes it seems to power reset the adapter device or PCIe comunication errors out…Any tips to have this metis card working with a laptop reliably? 

I'm having trouble getting a Metis M.2 card to be detected on a Gigabyte B550I AORUS PRO AX system, and I'm trying to determine whether this is a compatibility issue or if the card itself may be faulty.System configuration Motherboard: Gigabyte B550I AORUS PRO AX (latest BIOS) CPU: AMD Ryzen 5 5600 Operating System: Windows 11 I tested the card in both available M.2 slots: M2A_CPU (front slot) M2B_SB (rear slot) To rule out an issue with the motherboard, I first installed a known-good NVMe SSD in each slot. The SSD is detected correctly by both the BIOS and Windows in either slot.When I replace the SSD with the Metis card, using the same BIOS configuration, the behavior changes completely: The BIOS does not detect any device in the M.2 slot. Windows Device Manager does not show a new PCIe device, not even as an unknown device. The MetisOmega INF driver installs successfully, but reports that it was installed on 0 devices, which makes sense since Windows never detects the card

As the title suggests, I want to factory reset the board so that I can reinstall and setup the board from a clean state? How can I do it?

Hello Axelera support team,I am running the Axelera Metis M.2 accelerator on a Radxa Rock 5B (RK3588 SoC) with Armbian and kernel 6.18.10-current-rockchip64. After extensive debugging over several days, I have identified a compatibility issue between the metis driver and the ARM SMMU-v3 on this platform. I would appreciate your guidance on resolving this.HARDWARE & SOFTWAREBoard: Radxa Rock 5B (RK3588, 8GB RAM, PCIE3.0-X4) not 5B+ model. OS: Armbian, kernel 6.18.10-current-rockchip64 (mainline) Accelerator: Axelera Metis M.2 Driver version: metis 1.4.16 SDK/Runtime version: voyager-sdk / runtime-1.6.0-1 PSU: 65WWHAT WORKSThe Metis is detected correctly via PCIe: lspci shows "Axelera AI Metis AIPU (rev 02)" at 0000:01:00.0 After patching the Device Tree to expand the PCIe memory window (the default 14MB window was too small; expanded the 64-bit prefetchable range at 0x900000000 to 128MB), the driver loads successfully: /dev/metis0 -> metis-0:1:0 is created "Axelera AIPU PCIe Dri

Hi there,I saw few posts about users having difficulties in having a working setup as Metis M.2, Radxa RockPi 5B and Ubuntu.I found the correct combination and applied a modification to the standard device tree of the RockPi 5BSETUPOS: Ubuntu 24.04 from the Joshua-Riek ubuntu-rockchip project (https://github.com/Joshua-Riek/ubuntu-rockchip) Voyager SDK 1.7.0 Metis M.2 in the board's M.2 slotSYMPTOM The Metis driver installed cleanly and the device enumerated on the PCIe bus (visible in lspci), but running axdevice from the Voyager SDK failed with:min() iterable argument is emptyIn practice this means the runtime enumerated the card but couldn't actually connect to it — the device tree wasn't exposing the PCIe node the way the runtime expects.SOLUTION The fix is the same device-tree recompile documented for the Orange Pi 5 Plus: https://support.axelera.ai/hc/en-us/articles/27059519168146-Bring-up-Voyager-SDK-in-Orange-Pi-5-PlusThe one gotcha: on this Ubuntu build the Rock 5B device tree

Will this ever be made available? I am interested in the 16gb version.   

Hey everyone,I am evaluating the Metis lineup for an edge AI project and have a specific question about multi-card architecture that I haven't found a definitive answer to in the docs or SDK references.What I understand is supported today: The Voyager SDK detects multiple Metis cards in a single host. Each card runs its own independent inference pipeline. A real-world surveillance example shows three 4-chip PCIe cards running five primary models + one secondary model in parallel across 48 AIPU cores. My question: Is there any current or planned SDK support for splitting a single neural network across multiple Metis cards (e.g., layer sharding or tensor parallelism across two M.2 cards)? Or is the architecture strictly "one model must fit entirely within a single card's memory and AIPU"?Context for my use case: I am looking at a host with dual M.2 slots (e.g., Radxa Orion O6N) and weighing whether two standard Metis M.2 cards could act as a unified 2-GB / 428-TOPS accelerator for a

Hi, when running inference on Metis M.2 on raspberry CM5 we noticed these errors occuring after couple minutes. error log: [libtriton_linux.c:531] DMABUF_METIS_XFER failed: Input/output error [AxeleraDmaBuf.cpp:222] DMA transfer failed: Input/output error [ERROR][axeShareMemoryExecute]: Dmabuf transfer failed. [ERROR][axeCommandQueueExecuteCommandListsAsync]: Level-zero memory operation failed: 0x70010001. terminate called after throwing an instance of 'std::runtime_error' what():  axr_run_model failed with Error at zeCommandQueueExecuteCommandLists(cmdqueue, n_cmdlists, cmdlists, nullptr): cmdqueue_run_cmdlists: 319: Exit with error code: 0x70010001 : ZE_RESULT_ERROR_NOT_AVAILABLE kernel errror log: axl 0001:01:00.0: DMA error WR CH0 (ctrl 0x1) setup:  Runtime: runtime-1.5.3-1 - Voyager SDK: v1.5.2 - metis-dkms: 1.4.4 - Firmware: flash version 1.5.0 - bcver 7.1

Hi! My name is Salvador and I’ve been trying to integrate the Metis M.2 on a Jetson Orin NX 16GB to perform Computer vision tasks.Recently the Axelera team shared a guide to Bring up Metis M.2 on Jetson Orin, where they explain the steps required to modify the kernel to use the Metis Accelerator.For me these changes were not enough, so I had to perform additional steps to make it work, I hope this post is useful for anybody trying to accomplish the same. The following steps build upon the instructions provided by the Axelera team.Prepare the Nvidia files necessaryWe will use a host machine running Ubuntu 20.04 or 22.04 (newer versions are not compatible with some Nvidia tools) where we will run all the described process, download the kernel sources, the Jetson Sample Filesystem, and the Jetson linux toolchain, and execute the cross compilation of the linux kernel, and the flashing into the Jetson Oring NX. To install the Jetson toolchain just follow the instructions provided on the lin

use the metis m.2, zed x and nvme on a jetson orin nx 16gb a condensed field guide to a real-time vision stack on the orin nx 16gb: preempt_rt kernel, axelera metis npu, zed x stereo, nvme. every section here exists in long form in the repository docs, linked throughout and listed at the end. what this isa complete recipe for taking a stock jetson orin nx 16gb and turning it into a real-time vision platform:custom preempt_rt kernel with low-jitter tuning (cyclictest avg ~3 µs on the isolated cores; max under the 100 µs gate make verify enforces. run it headless — a desktop session adds ~150 µs ipi spikes) axelera metis m.2 as the inference accelerator (in-tree driver, not oot, vermagic-safe). detection costs the jetson's gpu essentially nothing, which is the whole point stereolabs zed x via the zed link mono capture card (max9296 deserializer) nvme boot + a btrfs data partition for recordings dmabuf zero-copy pipeline (design goal: camera → isp → npu with no cpu memcpy)everything below

Hello.I recently received the m.2 metis accelerators and did a test on the boards provided by Axelera and got results close to the published benchmarks. It was succesful.I then connected these accelerators to the Orin (via the m.2 slot) in order to use them also for the my Jetson AGX Orin environment. But in the voyager-sdk installation i got “WARNING: Failed to refresh pcie and firmware” error. The installation completes but the accelerator device does not show up on my system. In lspci -tv command I get the output attached to this post. Can’t see metis there.I didn't see any information about the compatibility of these accelerators with Jetson systems (my m2 slot is M-key). If they are compatible, can you help me to fix the installation?Thanks :)

Hello,There seems to be two different published benchmarks for ResNet50.The first is in the Voyager SDK’s documentation : 1756 FPS (M.2) / 1946 FPS (PCIe) :- https://github.com/axelera-ai-hub/voyager-sdk/blob/latest/docs/reference/model_zoo.mdThe second is on the Metis Marketing page : Up to 3200 frames per second (ResNet-50)- https://axelera.ai/ai-accelerators/aipu/metis I was able to achieve 2050 FPS, which is higher than the modelzoo documentation, but MUCH lower than the marketing claim:- https://mariobergeron.com/posts/edge-ai-power-p04-axelera-metis/ Where does the 3200 FPS benchmark claim come from ?   How was this benchmark achieved on Metis ?  Which hardware platform ?Which brings me to the next marketing claim : Industry-Leading FPS / Watt ratios on ResNet50v1 (graph showing 614 FPS/W- https://axelera.ai/ai-accelerators/aipu/metis I was only able to achieve 270 FPS/W :- https://mariobergeron.com/posts/edge-ai-power-p04-axelera-metis/ What does the 614 FPS/W benchmark come fro

How can I deploy WASB model on metis m2?

Hello Axelera support team,I am running the Axelera Metis M.2 accelerator on a Radxa Rock 5B (RK3588 SoC) with Armbian and kernel 6.18.10-current-rockchip64. After extensive debugging over several days, I have identified a compatibility issue between the metis driver and the ARM SMMU-v3 on this platform. I would appreciate your guidance on resolving this.HARDWARE & SOFTWAREBoard: Radxa Rock 5B (RK3588, 8GB RAM, PCIE3.0-4X) OS: Armbian, kernel 6.18.10-current-rockchip64 (mainline) Accelerator: Axelera Metis M.2 Driver version: metis 1.4.16 SDK/Runtime version: voyager-sdk / runtime-1.6.0-1 PSU: 65WWHAT WORKSThe Metis is detected correctly via PCIe: lspci shows "Axelera AI Metis AIPU (rev 02)" at 0000:01:00.0 After patching the Device Tree to expand the PCIe memory window (the default 14MB window was too small; expanded the 64-bit prefetchable range at 0x900000000 to 128MB), the driver loads successfully: /dev/metis0 -> metis-0:1:0 is created "Axelera AIPU PCIe Driver, version 1.

I would like to use the Metis M.2 in an embedded system running Open Embedded with a 4.19 kernel. (It doesn’t have the “modern” /dev/dma_heap/ interface, it uses /dev/ion). I have the driver installed in the host, and when I use the SDK in a Ubuntu 22.04 docker container I get this error:[libaxldev_linux.c:394] No dmabuf driver found[ERROR][axeShareMemAllocMap]: Fail to alloc dmabuf[ERROR][axeMemAllocShared]: Share memory allocate mao failed: 0x70010001.terminate called after throwing an instance of 'std::runtime_error'  what():  axr_load_model_instance failed : Failed to create executor for model: kernel_function_batchedAborted Can the driver/library be compiled to use ION instead of dmabuf?

Title says it all -- any timeline for a “wrynose” release for the M.2 card so it can be included in a wrynose Yocto Project build?

I'm trying to do a pci passthrough from proxmox to my VM.I keep getting the error when starting my VM. error writing '1' to '/sys/bus/pci/devices/0000:02:00.0/reset': Inappropriate ioctl for devicefailed to reset PCI device '0000:02:00.0', but trying to continue as not all devices need a resetkvm: ../hw/pci/pci.c:1815: pci_irq_handler: Assertion `0 <= irq_num && irq_num < PCI_NUM_PINS' failed.TASK ERROR: start failed: QEMU exited with code 1This is my machine details agent: 1bios: ovmfboot: order=scsi0;ide2;net0cores: 4cpu: x86-64-v2-AESefidisk0: local-lvm:vm-103-disk-0,efitype=4m,ms-cert=2023,pre-enrolled-keys=1,size=4Mhostpci0: 0000:02:00.0,pcie=1,rombar=1ide2: none,media=cdrommachine: q35memory: 4096meta: creation-qemu=10.1.2,ctime=1776892906name: axeleranet0: virtio=BC:24:11:A4:8C:9B,bridge=vmbr0,firewall=1numa: 0ostype: l26scsi0: local-lvm:vm-103-disk-1,iothread=1,size=32Gscsihw: virtio-scsi-singlesmbios1: uuid=49dcbf39-39e5-4a39-a8ad-cc02f5c886bfsockets: 1vmgenid: 9