How do I persist Devicetree with OrangePi5 Plus on MicroOS

Nelson · August 2, 2026, 6:07pm

I have a k3s cluster running on 3 Orange Pi 5 Plus systems and MicroOS. I have installed EDK2 and it all works wonderfully. Thank you!

I want to use the NPUs on the rk3588 and they do not seem to be detected. I have fixed this by installing: dtb-rockchip-7.1.4-1.1.aarch64. I copied the rk3588-orange-pi-5-plus.dtb from /boot/dtb/ in to /boot/efi/dtbs/rk3588-orange-pi-5-plus.dtb and then I created a new file in /boot/efi/loader/entries called npu.conf by copying the newest entry and added the line:
devicetree /dtbs/rk3588-orangepi-5-plus.dtb

It works. I can boot in to that, the rocket drivce is detected and installed:

[    6.549533] [    T575] [drm] Initialized rocket 0.0.0 for rknn on minor 0
[    6.549737] [    T575] rocket fdab0000.npu: Rockchip NPU core 0 version: 1179210309
[    6.550650] [    T575] rocket fdac0000.npu: Rockchip NPU core 1 version: 1179210309
[    6.552300] [    T575] rocket fdad0000.npu: Rockchip NPU core 2 version: 1179210309

I have device nodes in /dev/accel.

Is there a proper fix for this so that it’s automatic? I expect a new 7.1.5 kernel in the coming weeks. Will I have to make a new entry and make sure files are installed in to the right places in the efi partition? Or is there a way to sort of make this work going forward?

dezza · August 2, 2026, 7:06pm

There is a make devicetree or make dtb in the kernel. You need to match to version, you can’t take it from build and apply to diff rev.

Nelson · August 2, 2026, 8:11pm

dtb-rockchip appears to be matched to the kernel version. I just want to get systemd-boot to add it to the entries automatically each time there is a new kernel

dezza · August 3, 2026, 2:37am

Does orangepi5 use uboot?

github.com/ARM-software/u-boot

doc/README.distro

master

SPDX-License-Identifier: GPL-2.0+
/*
 * (C) Copyright 2014 Red Hat Inc.
 * Copyright (c) 2014-2015, NVIDIA CORPORATION.  All rights reserved.
 * Copyright (C) 2015 K. Merker <merker@debian.org>
 */

Generic Distro Configuration Concept
====================================

Linux distributions are faced with supporting a variety of boot mechanisms,
environments or bootloaders (PC BIOS, EFI, U-Boot, Barebox, ...). This makes
life complicated. Worse, bootloaders such as U-Boot have a configurable set
of features, and each board chooses to enable a different set of features.
Hence, distros typically need to have board-specific knowledge in order to
set up a bootable system.

This document defines a common set of U-Boot features that are required for
a distro to support the board in a generic fashion. Any board wishing to
allow distros to install and boot in an out-of-the-box fashion should enable

This file has been truncated. show original

Seems like there’s a way to load devicetree from there similar to how rpi5 does it

Nelson · August 3, 2026, 1:54pm

I’m using MicroOS mainline which uses systemd-boot.

Nelson · August 3, 2026, 2:26pm

It looks like /usr/lib/kernel/install.d/90-loaderentry.install Has some logic to do what is needed, I just need to reverse engineer it and figure out how to make it do it

malcolmlewis · August 3, 2026, 2:43pm

You should log into IRC or Matrix and join the ARM room and ask there…

Nelson · August 12, 2026, 2:19pm

I found the solution.

echo 'DEVICETREE_SOURCE="/boot/dtb-%V/rockchip/rk3588-orangepi-5-plus.dtb"' >> /etc/default/sdbootutil

Putting it here for future googlers and this thread can be closed.