Support Central

I followed the official Windows setup guide, and the Metis device is detected and started:However, running axrunmodel fails:How can I fix this parsing error with pnputil.exe?

Hi Guys,I'm quite stuck and would really appreciate your help. I'm  a uni student trying to update aMetis Compute Board (RK3588 SBC) from Voyager SDK 1.2.5 to SDK 1.7 or newer (to use axmonitorand run LLMs), but I can't figure out the correct/safe update path for my board andI don't want to risk a wrong flash (this is for my university internship). Goal: run Voyager SDK 1.7. In the 1.7 container, axdevice fails with:  "kernel driver 0.07.14 not compatible with 1.4.18 supported by this SDK"I’ve read the user manual an found this; Here's what I found on the device. At the SDK-1.2.5 level everything works: axdevice(in the 1.2.5 container) reports board_type=sbc, fwver='v1.2.5' and the AIPU healthy(mvm=0-3:100%). The running kernel is 6.1.84-rockchip-standard, built back in February2025 (uname -r), and the current Metis driver reports version 0.07.14(/sys/class/metis/version). Looking at the installed packages (dpkg -l), the drivercomes from kernel-module-metis-6.1.84-rockchip-standard and

Dear Axelera Support,I am currently following the Voyager SDK quick start guide (YOLO inference demo) on an RK3588-based Compute Board (received out-of-the-box), using Voyager SDK version 1.5.3. However, I am unable to successfully run inference due to persistent device communication issues with the Metis AIPU.--------------------------------------------------System Overview- Platform: RK3588 (Compute Board, out-of-the-box setup)- Voyager SDK: 1.5.3 (and also tested with 1.4.0)- Connection: PCIe (Metis AIPU detected as 01:00.0 [1f9d:1100])--------------------------------------------------Initial IssueRunning the quick start inference:./inference.py yolov5s-v7-coco usb:/dev/video1Result:ERROR: No devices foundAt that moment:- lspci returned no devices, indicating a PCIe enumeration issue.--------------------------------------------------After Cold BootAfter performing a full power cycle:- lspci correctly shows:  01:00.0 Processing accelerators: Axelera AI Metis AIPU (rev 02) [1f9d:1100]

Hi team,We are currently deploying the Axelera Metis PCIe 4-AIPU AI Accelerator Card (AXE-BME20P4) in an HPE ProLiant DL380 Gen11 server as part of a k3s-based AI inference cluster.The card is physically seated in a PCIe Gen 3.0 x16 slot and Ubuntu Server 24.04 LTS is installed. However, we are facing a challenge with the auxiliary power connection.The Metis card requires a 2x4 (8-pin) PCIe auxiliary connector, but the HPE DL380 Gen11 uses a proprietary internal power header on the riser side. We have identified HPE part P77896-B21 (DL380 Gen11 2U 8-pin GPU Power Cable Kit) as the likely adapter cable needed.Before we proceed with the order, we wanted to check with you directly:1. Have you or any of your customers successfully deployed the Metis PCIe 4-AIPU in an HPE ProLiant DL380 Gen11?2. Can you confirm that HPE P77896-B21 is the correct cable to connect the Metis card's 2x4 auxiliary power connector to the DL380 Gen11's internal power distribution?3. Are there any other HPE DL380 G

I created a post, formatting is poor. I need to edit/update the formatting. Checked the site couldn’t find a way to do that. How do I edit a post?

SummaryOn a Metis dev system, ./deploy.py <model> fails at the compile step: it exits with RC=1 and writes nothing to stdout or stderr (captured 1>out.txt 2>err.txt → both empty), produces no log file, and no traceback. It reproduces on a trivial 27×30 model, so it is not model‑size related. The one time the compiler did emit an error (earlier run, attached earlier_pkl_memoize_PermissionError.md) it was a TVM .pkl_memoize_py3 PermissionError, which makes me suspect the current silent failure is the same TVM‑cache / working‑directory‑writability problem, now swallowed.EnvironmentHardware: Metis dev system — Portenta X8 on the board, host access via a Raspberry Pi acting as an adb relay over USB. SDK: Voyager container voyager-sdk-1.4.0, SDK at /home/ubuntu/voyager-sdk, venv /home/ubuntu/.cache/axelera/venvs/b4c581dc (Python 3.10, TVM backend). from axelera import compiler, runtime imports successfully (prints OK).What I'm deployingA single 1×1 Conv2d exported to ONNX (it imp

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_datas

Hi I'm Zero (sudo name) I'm a reverse engineering expert. Here to learn how can I involve Ai in my work and make it more sturdy

Subject Metis M.2 on Toradex Verdin i.MX95 enumerates over PCIe but all Axelera commands time out after (reportedly) successful firmware update; MSI interrupts never increment and board firmware version can no longer be queried Summary We are using an Axelera Metis M.2 accelerator on a Toradex Verdin i.MX95 WB on Mallow carrier. PCIe enumeration succeeds and the `metis` kernel driver binds to the endpoint, but all Axelera device commands fail to retrieve board/device information. The kernel repeatedly logs: axl 0000:01:00.0: IRQ MSI timeout (12 1) This persists with ARM SMMU passthrough enabled via `iommu.passthrough=1`. The most important observation is that the Metis MSI interrupt counters do not increment when an Axelera command is issued. The endpoint advertises MSI and the driver allocates MSI vectors, but the expected completion interrupt is never observed by Linux. Environment Host: Toradex Verdin iMX95 WB on Mallow BoardLinux 6.6.138-7.6.1-develTDX Wayland with XWayland 7.6.1-d

My colleagues don't remember the Ubuntu password and I have to use the miniPC. I have tried some passwords they have given me, but no luck.

Hi,I’m interested to know if there is any way to measure AIPU power usage on Metis-equipped devices. The idea would be to measure yolo inference power usage on AIPU. 

Dear axelera teamI wish to start a deep dive conversation on the idea of working closely with your team to build products that's we working on.We need partner like you and community to work with for support and to contribute. Looking to connect with you soonSincerelyPulkit 

So far we had 7 boards, 5 are fine and working with no issues. But on 1 we get errors when running "axdevice --refresh" which points to some sort of hardware or firmware issue since the others work properly. Another one behaves the same way but sporadically, sometimes it works and sometimes it shows the same errors. We are connecting the cards into a cm5 i/o board, and are running RPI OS and voyager sdk 1.5.2 inside the ubuntu docker. Below is the ouput:-------------------------------------------------------------------------------------------------------------------axdevice --refresh0001:01:00.0 : Axelera AI Metis AIPU (rev 02)[libtriton_linux.c:1313] Device communication timed out: device did not respond within 1 seconds. (300)WARNING: Failed to get valid board type for device metis-1:1:0 got 8[libtriton_linux.c:1313] Device communication timed out: device did not respond within 1 seconds. (110)ERROR: Failed to load runtime stage0: /opt/axelera/device-1.5.2-1/omega/bin/start_axelera_

I have a Metis Dev System board with Arduino x8. I followed the getting started guide  On the step to make the operators:make clobber-libs && make operatorsit fails. It gives error is as on the image below (sorry for photo instead of text)Any suggestions what is the root cause and how to fix it?

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 8Device 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.shFirmware Flasher - Extracting files...Extracting firmware files...Files extracted successful

Hello Axelera team,I successfully got my Metis PCIe card (16 GB single-AIPU, Device 1f9d:1100) detected and running on a Dell PowerEdge R420 (Ubuntu 24.04 LTS, kernel 6.17.0-14-generic) using Voyager SDK release/v1.5.Quick summary how I got the hardware/driver working:Installed in a PCIe x4 slot (bus 0a:00.0) Disabled third-party PCIe fan response via IPMI raw command to stop jet-engine fans: ipmitool -I lanplus -H -U root -P calvin raw 0x30 0xce 0 0x16 5 0 0 0 5 0 1 0 0 Updated BIOS/iDRAC to latest available for R420 Cloned repo: `git clone https://github.com/axelera-ai-hub/voyager-sdk.git && cd voyager-sdk && git checkout release/v1.5` Ran `./install.sh --all --media` as non-root user Driver loaded successfully: `metis` module active, lspci shows "Axelera AI Metis AIPU (rev 02)", `/dev/metis-0:a:0` exists  `axdevice` confirms: "Device 0: metis-0:a:0 16GiB pcie flver=1.4.0 bcver=1.4 clock=800MHz(0-3:800MHz) mvm=0-3:100%"The install finishes with "Installation complete"

I try to use Metis M.2 on Jetson Nano, I followed all the steps to install the board but when I try to run the first example from Voyager-SDK I get the following error:(venv) adrianza@ubuntu:~/voyager-sdk$ ./inference.py yolov5s-v7-coco media/traffic1_1080p.mp42026-02-05 09:54:10.578538286 [W:onnxruntime:Default, device_discovery.cc:164 DiscoverDevicesForPlatform] GPU device discovery failed: device_discovery.cc:89 ReadFileContents Failed to open file: "/sys/class/drm/card1/device/vendor"WARNING : Failed to get OpenCL platforms : clGetPlatformIDs failed: PLATFORM_NOT_FOUND_KHRWARNING : Please check the documentation for installation instructionsINFO : Deploying model yolov5s-v7-coco for 4 cores. This may take a while...|████████████████████████████████████████| 7:53.1 Opening in BLOCKING MODE NvMMLiteOpen : Block : BlockType = 261 NvMMLiteBlockCreate : Block : BlockType = 261 WARNING : capsfilter0: BUS: not negotiatedWARNING : (../libs/gst/base/gstbasetransform.c(1431): gst_base_tr

On an AMD CPU with ubuntu 24.04, I see these warnings. Inference does open, but it seems to render poorly.(venv) my@machine:~/voyager-sdk$ ./inference.py yolov8l-coco-onnx media/traffic1_1080p.mp4 media/traffic1_1080p.mp4 media/traffic1_1080p.mp4 media/traffic1_1080p.mp4INFO    : Could not exec vainfo: Command '['vainfo']' returned non-zero exit status 3.WARNING : Failed to get OpenCL platforms : clGetPlatformIDs failed: PLATFORM_NOT_FOUND_KHRWARNING : Please check the documentation for installation instructionsOpenCL doesn't find any platforms(venv) my@machine:~/voyager-sdk$ clinfoNumber of platforms                               0ICD loader properties  ICD loader Name                                 OpenCL ICD Loader  ICD loader Vendor                               OCL Icd free software  ICD loader Version                              2.3.2  ICD loader Profile                              OpenCL 3.0

Hi all!I’m currently trying to setup a simple pipeline with yolo pose + tracker.The attached YAML works fine, but how to link the tracker results back to the tracked object?It seems the trackers meta data does not contain any reference to the tracked object from stage 1.I feel like I’ missing something obvious here..axelera-model-format: 1.0.0name: yolo11lpose-coco-trackerdescription: yolo11l pose estimation with ByteTrack trackingpipeline: - keypoint_detections: model_name: yolo11lpose-coco-onnx input: type: image preprocess: - letterbox: height: ${{input_height}} scaleup: true width: ${{input_width}} - torch-totensor: inference: handle_all: false postprocess: - decodeyolopose: box_format: xywh conf_threshold: 0.65 max_nms_boxes: 3000 nms_iou_threshold: 0.45 nms_top_k: 300 normalized_coord: false - tracking: model_name: t

Hello everyone, I’m trying to install some packages using APT with my Axelera Metis Compute Board with Voyager Linux 1. However the /etc/apt/sources.list is empty. What kind of repositories should I use?Are there any tutorials?Thanks.Best regards

Hello,I created a request from support.axelera.ai and I’m part of a team, how can i gave access to my request to my team?I saw that there is a tab in request “Request I’m CC’d on” so i think there is some implementation for this but i can’t find it anywhere.

Hi,Bit of a weird issue with the M.2 Evaluation System (SBC model AIB-MR1B-A1), and I’m worried it could be a hardware fault. I somehow got to a state where I would see AXR_ERROR_CONNECTION_ERROR: No target device found in lspci output".lspci didn’t show the accelerator card, but instead listed “Non-VGA unclassified device”:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3588 (rev 01)01:00.0 Non-VGA unclassified device: Synopsys, Inc. DWC_usb3 / PCIe bridgedmesg showed:Tue Sep 2 19:51:14 2025] rk-pcie fe170000.pcie: PCIe Linking... LTSSM is 0x3 [Tue Sep 2 19:51:16 2025] rk-pcie fe170000.pcie: PCIe Link Fail [Tue Sep 2 19:51:16 2025] rk-pcie fe170000.pcie: failed to initialize hostAfter trying a few things, I resorted to re-imaging the SBC. Then, on the first log-in from adb shell, I still saw Non-VGA unclassified device, but after a reboot, SSH’ing into the Eval System, I saw it as:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd Device 3588 (rev 01)01:00.0 Processing accelerators

Thank you for your continued support.Could you please tell me the performance (fps) under the following conditions?1. METIS COMPUTE BOARD2. YOLOv8n model3. USB WEB CAMERA (1080P@60FPS)Thank you in advance.