thanks for the answer. i wonna boot from the emmc, so i have bought an little emmc module, so there should no hassle with the MASK-ROM, right ? just trying to build mainline u-boot ragarding this: https://uthings.uniud.it/building-mainline-u-boot-and-linux-kernel-for-orange-pi-boards but, of course, getting errors 😞 Image 'simple-bin' is missing external blobs and is non-functional: rockchip-tpl atf-bl31 /binman/simple-bin/mkimage/rockchip-tpl (rockchip-tpl): An external TPL is required to initialize DRAM. Get the external TPL binary and build with ROCKCHIP_TPL=/path/to/ddr.bin. One possible source for the external TPL binary is https://github.com/rockchip-linux/rkbin. /binman/simple-bin/fit/images/@atf-SEQ/atf-bl31 (atf-bl31): See the documentation for your board. You may need to build ARM Trusted Firmware and build with BL31=/path/to/bl31.bin Image 'simple-bin' has faked external blobs and is non-functional: rockchip-tpl Image 'simple-bin' is missing optional external blobs but is still functional: tee-os /binman/simple-bin/fit/images/@tee-SEQ/tee-os (tee-os): See the documentation for your board. You may need to build Open Portable Trusted Execution Environment (OP-TEE) and build with TEE=/path/to/tee.bin Image 'simple-bin-spi' is missing external blobs and is non-functional: rockchip-tpl atf-bl31 /binman/simple-bin-spi/mkimage/rockchip-tpl (rockchip-tpl): An external TPL is required to initialize DRAM. Get the external TPL binary and build with ROCKCHIP_TPL=/path/to/ddr.bin. One possible source for the external TPL binary is https://github.com/rockchip-linux/rkbin. /binman/simple-bin-spi/fit/images/@atf-SEQ/atf-bl31 (atf-bl31): See the documentation for your board. You may need to build ARM Trusted Firmware and build with BL31=/path/to/bl31.bin Image 'simple-bin-spi' has faked external blobs and is non-functional: rockchip-tpl Image 'simple-bin-spi' is missing optional external blobs but is still functional: tee-os /binman/simple-bin-spi/fit/images/@tee-SEQ/tee-os (tee-os): See the documentation for your board. You may need to build Open Portable Trusted Execution Environment (OP-TEE) and build with TEE=/path/to/tee.bin Some images are invalid so getting the blobs from the rokchip repos : -rw-rw-r-- 1 baumgart baumgart 430880 Jul 23 10:58 rk3588_bl31_v1.48.elf -rw-rw-r-- 1 baumgart baumgart 473512 Jul 23 10:58 rk3588_bl32_v1.19.bin -rw-rw-r-- 1 baumgart baumgart 75320 Jul 23 10:58 rk3588_ddr_lp4_2112MHz_lp5_2400MHz_v1.18.bin -rw-rw-r-- 1 baumgart baumgart 71600 Jul 23 10:58 rk3588_ddr_lp4_2112MHz_lp5_2736MHz_eyescan_v1.11.bin -rw-rw-r-- 1 baumgart baumgart 6464 Jul 23 10:58 rk3588_pcie_v2.20.bin -rw-rw-r-- 1 baumgart baumgart 512 Jul 23 10:58 rk3588_ramboot_null0.bin -rw-rw-r-- 1 baumgart baumgart 512 Jul 23 10:58 rk3588_ramboot_null1.bin -rw-rw-r-- 1 baumgart baumgart 49276 Jul 23 10:58 rk3588_ramboot_v1.06.bin -rw-rw-r-- 1 baumgart baumgart 239010 Jul 23 10:58 rk3588_spl_v1.13.bin -rw-rw-r-- 1 baumgart baumgart 90268 Jul 23 10:58 rk3588_usbplug_v1.11.bin so, ROCKCHIP_TPL should be the rk3588_ddr_lp4_2112MHz_lp5_2400MHz_v1.18.bin but BL31 ? rk3588_bl31_v1.48.elf or rk3588_bl32_v1.19.bin where do i get an OP-TEE bin ?

It all depends on what version or variant of OS you are using. I have a R6C and have done many fixes and workarounds for various OSses/distros to the point that I just maybe take what generic upstream kernel does. I anyhow change/fake MAC addresses as I use bridges and also VLANs. Is in Armbian Bookworm and Opensuse Tumbleweed. Ubuntu based has and extra netplan layer that is even more a PITA as it keeps .nmconnections file also in another place (generated) then /etc/NetworkManager/system-connections/ Recently a change in scripting has been done so that name 'wan' is/or has been changed into 'wan1', so at least this does not match what is printed on the metalcase. At least that is what I remember from a quick check on github; See what is in your udev rules scripts yourself. https://github.com/armbian/build/blob/main/config/boards/nanopi-r6s.conf

it all depends on what your plan is what the device should do; I have a R6C for about 18 months now and bought it as an alternative/better more integrated alternative for existing RPi4 (and also RPi5 that still has no M.2 socket). I see many people on for example RPi forum who want to create some router thing, so they buy HATs and USB stuff for an RPi, but this NanoPi series has even WRT preinstalled. I removed it as I wanted generic server box (virtual machines host mainly). I do not really need the 2x RJ45 currenlty, but the metal case is great. Is simple passive cooling and insect/animal proof. It is mainly bootloader and kernel (and DTB/overlays) that matter. The userspace can be taken from elsewhere if you know how to. I currently use the R6C as desktop as well in another cooler room (summer hot here). EDK2-UEFI v1.1 bootloader, Armbian edge 6.16-rc3 kernel, Opensuse Tumbleweed for Btrfs rootfs to drive a DVI monitor KDE plasma 6.4.x. It means various Rockchips HW blocks do not work like NPU and video codecs HW accel block, but that is a choice. If you need those, use vendor kernel and see what exctly you need/want. The 2x RJ45 might be a chalenge, see maybe also:

I also needed a desktop on my Orange Pi Zero 2. I installed an "Armbian 25.5.1 Bookworm Minimal / IOT", then installed an XFCE desktop using some short guide I found on the Internet: sudo apt install lightdm xfce4 xfce4-goodies xorg After a reboot, my desktop started without any additional configurations. It's so good that now I have a new system with a desktop on my old hardware, which doesn't provide fresh OS images anymore.

That is a lot of work to get video for TVs that today have HDMI anyway. The audio out for an orangepione would also require audio amplifiers. Not many people have the skills to solder to the tiny pads on the orangepione and could easily destroy the board. HDMI for the orangepione works very well for both audio and video. That said, the orangepione with 512KB memory is under powered to run a desktop environment.