Ovaday

The one from MR / my previous message

Created a Pull Request:
https://github.com/armbian/linux-rockchip/pull/500

Final DTB: rk3566-box-X88PRO20-npu.dtb

@Hqnicolas do you know how I can add the board as selectable from the Armbian website? Do I have to also add DTS that will work for latest kernel?
 

@Ovaday First of all, thank you for the initiative.

This repository contains the files that will be used as example to enable your board in Armbian:
https://github.com/hqnicolas/ArmBoardBringUp

The example file you're referring to is this one:
https://github.com/hqnicolas/ArmBoardBringUp/blob/main/config/boards/h96-tvbox-3566.tvb

The boot settings you should use may vary considerably from this reference, but your device will need a configured bootloader.
https://github.com/hqnicolas/ArmBoardBringUp/tree/main/patch/u-boot/v2026.04/board_h96-tvbox-3566

You will need to focus on the new kernels like:
https://github.com/hqnicolas/ArmBoardBringUp/tree/main/patch/kernel/archive/rockchip64-7.1/dt

The repository you need to interact with to include these files is this one:
https://github.com/armbian/build

You need to validate everything before publishing, so do some hard work using this compiler:
https://docs.armbian.com/Developer-Guide_Overview/

 

Created a Pull Request:
https://github.com/armbian/linux-rockchip/pull/500

Final DTB: rk3566-box-X88PRO20-npu.dtb

@Hqnicolas do you know how I can add the board as selectable from the Armbian website? Do I have to also add DTS that will work for latest kernel?
 

Created a Pull Request:
https://github.com/armbian/linux-rockchip/pull/500

Final DTB: rk3566-box-X88PRO20-npu.dtb

@Hqnicolas do you know how I can add the board as selectable from the Armbian website? Do I have to also add DTS that will work for latest kernel?
 

Patched the .dtb for v6.1, currently not yet in final format. I will probably create a commit to Armbian with a .dts for our board.
I am attaching the dtb/dts just to keep track of the progress.

Here are results of the RKNN test launch:
 
rknn_api/rknnrt version: 2.3.2 (429f97ae6b@2025-04-09T09:09:27), driver version: 0.9.8 model input num: 1, output num: 1 input tensors:   index=0, name=input, n_dims=4, dims=[1, 224, 224, 3], n_elems=150528, size=150528, fmt=NHWC, type=INT8, qnt_type=AFFINE, zp=0, scale=0.007812 output tensors:   index=0, name=MobilenetV1/Predictions/Reshape_1, n_dims=2, dims=[1, 1001, 0, 0], n_elems=1001, size=2002, fmt=UNDEFINED, type=FP16, qnt_type=AFFINE, zp=0, scale=1.000000 custom string: Begin perf ...    0: Elapse Time = 8.06ms, FPS = 124.12 ---- Top5 ---- 0.935059 - 156 0.057037 - 155 0.003881 - 205 0.003119 - 284 0.000172 - 285

So:
CPU: OK
GPU: OK via Panfrost
NPU: OK, RKNN inference works on RKNPU
rk3566-box-X88PRO20-npu.dtb rk3566-box-X88PRO20-npu.dts

my Rupa 88 Pro 20, wifi/bt chip is cdtech 208821c (rtl8821cs), with real 4g32 had no bluetooth with mmie4jbcu's dtb or the included box-demo.dtb. with a lil help from claude.ai, i mix mmie4jbcu's dtb with x96x6.dtb from another thread here. et voilá bluetooth is working after  
apt install armbian-firmware-full rk3566-box-X88PRO20.dtb

I extracted DTB/DTS from the Android FW (files attached).
 
For whatever reason they are signed in the image as rk3568. No ideas why.
02_dtbdump_rockchip,rk3568-evb.dtb 02_dtbdump_rockchip,rk3568-evb.dtb.dts
 
 
Attention: They are for Android! Linux might not boot with them!

I've created a guide here how to run a Home Assistant OS
 
suprisingly it run mostly natively. Didn't do anything except replacing the DTB. Also right away flashed it into a emmc. On my board emmc is from Samsung and has a read speed on 180Mb/s...

I extracted DTB/DTS from the Android FW (files attached).
 
For whatever reason they are signed in the image as rk3568. No ideas why.
02_dtbdump_rockchip,rk3568-evb.dtb 02_dtbdump_rockchip,rk3568-evb.dtb.dts
 
 
Attention: They are for Android! Linux might not boot with them!

I know it was already written here in some of the messages that these devices are not secure. But now I got a message from Telekom that they detected a Chineese spyware connection:



The timeframe is exactly when I have switched the device on with an Android on board.