FWIW, on my rk3588 devices the NPUs are working with recent mainline releases: [ 5.967316] [drm] Initialized rocket 0.0.0 for rknn on minor 0 [ 5.975499] rocket fdab0000.npu: Rockchip NPU core 0 version: 1179210309 [ 5.978652] rocket fdac0000.npu: Rockchip NPU core 1 version: 1179210309 [ 5.985602] rocket fdad0000.npu: Rockchip NPU core 2 version: 1179210309 This script runs the Mesa example with the latest available working versions: And with this script, the Mesa example runs, with a small adjustment, also with the TFLite successor LiteRT: A MediaPipe sample can also be set up easily: But unfortunately, the MediaPipe framework does not support the extended delegate functionality of LiteRT (TFLite). And therefore no NPU support. classification-3.11-tflite.logclassification-3.13-litert.logobject_detection-3.12-litert.log

you may actually want to extract the dtb file on the android side of the tvbox you have just to get the OS to get recognize that chipset (but may not work due to missing driver).The odds for this kind of tv box to have a working wifi chipset is a lottery, most likely you better off not waste that effort and just buy a USB WiFi dongle instead, at least it works far better than a SDIO based wifi chipset like that.

I'll try. So far, just booting the board did not work. I suppose it does need mainline uboot. Need to figure out this fdt stuff somehow too...

Wonderful.

Yes. We should add `pahole` as a dependency of the linux-headers package, otherwise during headers install, the `.config` is different from the image build, leading to all kinds of sad. While we might fix the future, unfortunately, installing pahole manually (and removing/re-installing the linux-headers package) is the only way forward for versions already out of the door.