This is the publishable summary of a local XDNA2 source-build recovery. Raw logs, package files, machine paths, and downloaded kernel sources are kept out of the repository.
| Check | Result |
|---|---|
| Kernel driver | Ubuntu in-tree amdxdna; not replaced or rebuilt |
| Userspace | XRT 2.20.0 and xrt_plugin-amdxdna 2.20 |
| Hardware | RyzenAI-npu4, firmware 1.1.2.64 |
| GEMM | passed, 51.0 TOPS |
| Latency | passed, 46.0 us average |
| Throughput | passed, up to 83267.0 op/s average |
| Locked memory | unlimited soft and hard limits |
The shim was built with -nokmod; its package audit found no kernel module,
DKMS source, or firmware payload.
The then-current XRT 2.26 userspace built successfully but failed physical-NPU
validation with DRM_IOCTL_AMDXDNA_EXEC_CMD EINVAL against the Ubuntu 7.0
in-tree driver. The Ubuntu source caps command BOs at 32 KiB; the newer stack
issued larger ones. The branch-1.6/XRT-2.20 baseline retained the compatible
contract and passed all validation workloads.
The packaged pyxrt extension was built for CPython 3.14. It imported under
that interpreter but is not importable from Python 3.12. This does not affect
the XRT C++ runtime or xrt-smi; build a separate XRT tree with the Python
3.12 virtual environment active when a Python 3.12 binding is needed.
source /opt/xilinx/xrt/setup.sh
ulimit -l
xrt-smi examine
xrt-smi validate -d 0000:67:00.1 -r all --batch