Axelera Assist

How can I deploy WASB model on metis m2?

Dear all, I am trying to set up the metis PCIe accelerator on a intel workstation. Later we will move to a full risc-v embedded setup.In out lab workstation we are forced to use singularity instead of docker, so i am trying to translate the docker container into a singularity one.I think i am very close to make everything work. However, i am now stuck with a problem i can’t figure how to solve. in particular, i get a weird error when i try to run a simple ./inference.py with one of the pre-trained models. Below the full description on how i create, run the container, and how i run the example from the voyager sdk my `voyager-sdk-1.2.5.def` fileBootstrap: dockerFrom: ubuntu:22.04%labels Author You Version voyager-sdk-1.2.5%environment export DISPLAY=$DISPLAY%post apt-get update && apt-get install -y \

Hi all,I am trying to enable the the usage of the Metis PCIE rev02 on RISC-V Hosts, in particular the Sifive P550. Currently I could successfully (at least I think so), install the drivers and the device gets correctly identified and mapped in the system. I attach the loggings just to be sure: dmesg (after rescan):[  858.500785] pci 0000:01:00.0: [1f9d:1100] type 00 class 0x120000[  858.500843] pci 0000:01:00.0: reg 0x10: [mem 0x04380000-0x04380fff 64bit][  858.500865] pci 0000:01:00.0: reg 0x18: [mem 0x08000000-0x09ffffff][  858.500922] pci 0000:01:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref][  858.500943] pci 0000:01:00.0: Max Payload Size set to 512 (was 128, max 512)[  858.501115] pci 0000:01:00.0: supports D1[  858.501121] pci 0000:01:00.0: PME# supported from D0 D1 D3hot[  858.516166] pci_bus 0000:01: busn_res: [bus 01] end is updated to 01[  858.516197] pcieport 0000:00:00.0: BAR 14: assigned

Hi folks,after I resolved some of the issues I had with my Metis PCIe device, I stopped working with it since it was so loud that I got headache after 30min of runtime.Now I realized that there is a new FW which silences the fan and I upgraded the SDK and the FW:(venv) root@holodeck7:/voyager-sdk# axdevice -vINFO: Found PCI device: 01:00.0 Processing accelerators: Axelera AI Metis AIPU (rev 02)INFO: Found AIPU driver: metis 90112 0INFO: Firmware version matches: v1.3.1INFO: Using device metis-0:1:0Device 0: metis-0:1:0 4GiB pcie flver=1.2.0-rc2 bcver=1.0 clock=800MHz(0-3:800MHz) mvm=0-3:100% device_runtime_firmware=v1.3.1 board_controller_board_type=matterhorn sw_throttling: 200°C, hysteresis 5°C, throttle rate:12% hw_throttling: 105°C, hysteresis 10°C pvt_warning_threshold: 95°CBUT the fan keeps on spinning at m

Have you seen our fruit demo? If not, ​@David explains it amazingly here.Basically, it is running 3 different yolov8 models on a single chip to process 4k camera input to segment fruit, while only using 640x640 models!I love this demo and use it to evaluate any system that comes across my desk! So, obviously, when ​@Victor Labian posted the setup for the Orange Pi here, I just had to try it out! And it works perfectly straight after following the instructions!I shaded the fruit to look different from the original to show the accuracy of the segmentation.

Hi all,I’m a docker noob, so please bear with me if this is a stupid question.To get the SDK operational on my Ubuntu-24.04 system I followed the Install Voyager SDK in a Docker Container and can make it up to test-running some inferences. Alas, while I expected the videos to be displayed in a dedicated window at full resolution, for me they are shown in the active text-console (ncurses-based I assume), obviously coarse and slow.I tried to learn how to activate graphics output from within docker, but all I got was that docker essentially is meant to be text-only and graphics usually is provided via web-browser of pages served from within docker.So to put it bluntly: those videos showing Voyager SDK performing object detection at exhibitions at full-resolution and full-framerate, are thos

Hi! I wanted to upgrade my M.2 card with latest firmware 1.3.0 but when trying to invoke command from instruction https://github.com/axelera-ai-hub/voyager-sdk/blob/release/v1.3/docs/tutorials/firmware_flash_update.md#flash-the-board-controller-firmware, I got an error:Do you know how this can be resolved? I’m using Intel i5 processor.

This may not be possible because of how the software and hardware work together. I’m new here, and not traditionally a SW engineer, but I have a question/ suggestion. I noticed when I attempted to run the example local LLM inference scripts in the SDK that I can’t run them with only 1GB of DDR memory on the card. I think the example needs to be edited so that the model can be run on 1 GB of DDR (a model like tinyllama or similar that’ll actually fit in the 1GB of space.)After thinking about it, I do have an intel Raptor Lake integrated GPU, and an external NVIDIA A500 from Adlink Technologies. Is there any way to use the memory in the integrated CPU or the thunderbolt connected A500 GPU to run the LLM inference demos by using the DDR memory in the other devices? That would be very very useful!

i am using Metis M.2 Eval System with Aetina RK3588 Industrial Motherboard . i connected everything to it keyboard, monitor and mouse and power supply . the monitor is showing blank screen . but yesterday it is working . why it is not working now . is there any solution. 

Hi there,I've been truly impressed by this chip over the past couple of days—its object detection and LLM capabilities, combined with its energy efficiency, are remarkable. However, for my current project, I need to use Gemma3 and Whisper. From what I understand, your SDK requires using precompiled paths, which suggests that if a model isn’t officially supported by Axelera AI, we might not be able to run it directly.Am I understanding this correctly, or is there an alternative way to use custom models like Gemma and Whisper within your ecosystem?Thanks in advance!

I wanted to try the new SDK version `v1.3.1` but I now run into authentication issues with the installer.Authentication is required for the package index URL: https://software.axelera.ai/artifactory/axelera-dev-pypi/ - for the subset developmentChecking credentials with: pip install --dry-run --force --no-deps --no-cache-dir --break-system-packages --index-url https:/<email>:<token>@software.axelera.ai/artifactory/axelera-dev-pypi/ axelera_compilerERROR: Authentication failed for the supplied email address (florianzaruba@gmail.com) and token.When trying to run the step manually it succeeds though: ➜ voyager-sdk git:(v1.3.1) ✗ pip install --dry-run --force --no-deps --no-cache-dir --break-system-packages --index-url https://florianzaruba@gmail.com:<token>@software.axelera.ai/artifactory/axelera-dev-pypi/ axelera_compilerDefaulting to user installation because normal si

Hello everyone,I’m new to working with this hardware and recently installed the Metis M.2 chip (Firmware version: v1.2.0-rc2+bl1-stage0) on an ASRock Z170 Pro4S motherboard. The device was detected successfully.I’ve installed the Voyager SDK and attempted to run the following command from the Quick Start Guide:./inference.py yolov5s-v7-coco dataset --no-display However, I encountered an input/output error when executing the command. I’ve included the full error message below for reference.I would appreciate any guidance or suggestions you may have to help resolve this issue.Thank you in advance for your support. INFO    : Using default val dataset INFO    : Using device metis-0:5:0 INFO    : Network type: NetworkType.SINGLE_MODEL INFO    : Input INFO    :   └─detections INFO    : Imported DataAdapter ObjDataAdaptor from /home/tud/voyager-sdk/ax_datasets/objdataadapter.py Stream Playing:  71%|█████████████████

Hello!I am facing some problems tring to run a network inference on the Metis M.2 with Raspberry Pi via Docker. To try the inference I have followed the steps in the guide (https://support.axelera.ai/hc/en-us/articles/26362016484114-Bring-up-Voyager-SDK-in-Raspberry-Pi-5) but after trying to run the inference.py, I face the following errors:  (venv) root@iak:/home/voyager-sdk# ./inference.py yolov8s-coco-onnx ./media/traffic1_480p.mp4INFO    : Using device metis-1:1:0WARNING : Failed to get OpenCL platforms : clGetPlatformIDs failed: PLATFORM_NOT_FOUND_KHRWARNING : Please check the documentation for installation instructionsINFO    : Default OpenGL backend gl,3,3 overridden, using gles,3,1INFO    : Network type: NetworkType.SINGLE_

0000:01:00.0 : Axelera AI Metis AIPU (rev 02)ERROR:axelera.runtime:No AIPU driver found in lsmod outputERROR: AXR_ERROR_CONNECTION_ERROR: No AIPU driver found in lsmod output 

Hello,I am currently working with a lane detection model named culane_res18.onnx, and I would like to know how I can run this model on the Metis M2 device.Here are some details about the setup:The model is culane_res18.onnx, which is a lane detection model. The training dataset is from the CULane dataset, and I have the link to the dataset here. The model file can be found here.Could you kindly guide me on how to run this lane detection model on Metis M2? I would appreciate any step-by-step instructions or basic guidance on how to deploy

Hello!!Do you have any news about support for Ubuntu 24.04? I wanted to use axelera on raspberry pi cm5 however there is no support for 22.04 and I wanted to run it on the host, not in a docker container.Thank you 😊

Hello,I’m having trouble getting my AXELERA M2 to be recognized under Linux. Until recently everything was working fine; now when I try to run an inference the SDK can’t find the board. I’ve already tried rebooting, but the issue persists.aravind@aravind-H610M-H-V2:~/Desktop/voyager-sdk$ source venv/bin/activate(venv) aravind@aravind-H610M-H-V2:~/Desktop/voyager-sdk$ ./inference.py yolov5s-v7-coco chinmay/Vehicle-CV-ADAS/assets/challenge_video.mp4 --save-output ~/Desktop/voyager-sdk/chinmay/saved_videos/yolov5s-v7-coco.mp4ERROR : No target device found in lspci outputERROR : AXR_ERROR_CONNECTION_ERROR: No target device found in lspci output 

​@Victor Labian I’m also trying to setup rpi5 with metis m2. I have question what host OS you was using and have you changed anything in config.txt?

Hi, I am also working on same thing deploying the YOLOPv2 model on to Metis M2. I have downloadded the data set from bdd100k and arranged in this manner.voyager-sdk/├── data/│   └── yolopv2_dataset/│       ├── images/│       ├── labels/│       ├── cal.txt│       ├── val.txt│       └── data.yaml├── customers/│   └── my_yolopv2/│       └── yolopv2.pt└── yolopv2-custom.yamlso when i am trying to deploy the model using yaml I am getting this error(venv) aravind@aravind-H610M-H-V2:~/Desktop/voyager-sdk$ ./deploy.py customers/my_yolopv2/yolopv2.yamlINFO    : Using device metis-0:1:0INFO    : Detected Metis type as pcieINFO    : Compiling network yolopv2-custom /home/aravind/Desktop/voyager-sdk/c

hello I hijack this a little bit … once I type “lspci” it gave me following output on a pi 5 0001:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2712 PCIe Bridge (rev 30)0001:01:00.0 Processing accelerators: Axelera AI Metis AIPU (rev 02)0002:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2712 PCIe Bridge (rev 30)0002:01:00.0 Ethernet controller: Raspberry Pi Ltd RP1 PCIe 2.0 South Bridge how to activate the device and getting to work with my python3 script  

Hi, I followed the "Install Voyager SDK in a Docker Container" guide to try installing SDK version 1.2.5, but I encountered an error with one of the packages during the process.Could you please let me know how to resolve this issue?The attached file contains the installation log. ---    [150/193] Installing development libraries    [150/193] Install axelera_compiler    [150/193] python3 -m pip --disable-pip-version-check install --index-url XXXX@software.axelera.ai/artifactory/axelera-dev-pypi/ --no-deps -c cfg//requirements-ubuntu-2204-amd64.txt "axelera_compiler"    [150/193] Looking in indexes: XXXX:****@software.axelera.ai/artifactory/axelera-dev-pypi/    [150/193] WARNING: 401 Error, Credentials not correct for https://software.axelera.ai/artifactory/axelera-dev-pypi/axelera-compiler/(X)    [150/193] ERROR: Cannot install axelera_compiler because these package versions have conflicting dependencies.

it ask me every time about token … yes I use my registered emailand I did not found any token in my accountwtf

Dear all,I am trying to get my hands on the Metis PCIe card on my current working PC, beingmainboard: Asus Prime X570-P CPU: AMD Ryzen 9 3900X OS: Ubuntu 24.04.2 LTS, 6.8.0-58-generic x86_64The first issue I face is that the warm-reset does not seem to work for me, i.e. if I issue a reboot without re-powering the system, the Metis device does not show up in lspci, while after a power-down (with physical PSU switching off) it is there. This is reproducible and based on my experience points to either my mainboard BIOS issuing a wrong reset sequence to the PCIe slot, or the device itself not issuing a full reset sequence on warm-boot. Since I know how to get the card detected, this is only an annoyance - but I saw that also another user of AMD64 system in the forum has similar issues and the problem might go deeper.Which leads to the second issue I am observing and which I filed already a support request but realized here would b

Hello my name is Kevin, i am trying to work on a project that the m.2 is going to interfere with my cpu and later on maybe my gpu.is there a way, and another question whats the command to go on rtsp?  my system is:AMD 9950X3D CPUAMD 7900XTX GPU48 gb DDR5 on 8200MHZMetis Axelera AI on an m.2 port. 

This is a very interesting thread as I’m testing and M.2 card on an AMD system as well and am having what seems to be the exact same problems. Things added / tried: kernel command line includes md_iommu=off pcie_aspm=off update-pciids → resulted in card having the correct name in lspci : Axelera AI Metis AIPU (rev 02) axdevice --refresh -v results in: INFO:axelera.runtime.axdevice:Removing 0000:20:04.0INFO:axelera.runtime.axdevice:PCIE rescan0000:25:00.0 : Axelera AI Metis AIPU (rev 02)INFO:axelera.runtime:Found PCI device: 25:00.0 Processing accelerators: Axelera AI Metis AIPU (rev 02)INFO:axelera.runtime:Found AIPU driver: metis                  90112  0WARNING:axelera.runtime:4PCI device count mismatch: lspci=1, triton=0(removed