If wired correctly, dmesg reveals the following: [ 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 And when mesa is built with the rocket driver enabled, it can be used via teflon.

Could you try to write SPI image to spi flash manually? (not the sata one) Also, can you send the content of /boot/armbianEnv.txt which is located in the ssd.

# TV Box X88PRO13 My TV box is the X88PRO13. It is equipped with the RK3528 chip. I successfully running Armbian on the box. Find How To build and create Image for this BOX on http://github.com/joilg/x88pro A ready to go iso image is on https://github.com/joilg/x88pro/releases/tag/0.3 ------------------------------------------------------------------------------------------------- ## For those who have a different TV Box with RK3528 CPU, try the following procedure: The USB 2.0 and HDMI interfaces are the same for most boxes, so the console output should also be posible over HDMI here. 1. Flash MMC with the x88pro image and insert it into the box's MMC slot. 2. Connect a monitor via the HDMI interface. 3. Connect a USB keyboard to a USB port. 4. Power on the box. 5. In most cases, boot messages appear on the monitor, ending in a login prompt. 6. Follow the instructions on the monitor. ## 7. Extracting the correct DTB file binwalk /dev/mmcblk1 | grep -i "Flattened device tree" This should give output something like this: 67451654 0x4053B06 Flattened device tree, size: 99077 bytes, version: 17 67550731 0x406BE0B Flattened device tree, size: 99112 bytes, version: 17 138280448 0x83DFE00 Flattened device tree, size: 99112 bytes, version: 17 143958080 0x894A040 Flattened device tree, size: 379 bytes, version: 17 143960064 0x894A800 Flattened device tree, size: 99078 bytes, version: 17 Select the row with the largest size value. Replace the placeholders in the following commands: - `<TV_BOX_NAME>` with your box's name - `<START_ADDR>` with the first number from the selected row - `<SIZE>` with the size value from the selected row Extract the DTB file with: dd if=/dev/mmcblk1p2 of=rk3528-<TV_BOX_NAME>.dtb skip=<START_ADDR> count=<SIZE> bs=1 Copy it to boot directory: ```bash cp rk3528-<TV_BOX_NAME>.dtb /boot/dtb-6.1.115-vendor-rk35xx/rockchip/ # or cp rk3528-<TV_BOX_NAME>-android.dtb /boot/dtb-$(uname -r)/rockchip/ ``` Edit the `armbianEnv.txt` file: sed -i '/fdtfile=/c\fdtfile=rockchip/rk3528-<TV_BOX_NAME>.dtb' /boot/armbianEnv.txt sync and reboot your box. Now test if LAN, Audio, IR Remote Control, RTC ... is OK. Wifi is only implemented for the AIC8800 Chip. ### optional convert dtb file to readable DTS source file:: dtc -@ -I dtb -O dts -o rk3528-<TV_BOX_NAME>-android.dts rk3528-<TV_BOX_NAME>-android.dtb ## Additional notes I only have a X88PRO13 box, so I 'm not be able to test whether this works for your device. But it might be worth a try. ### all in one Script #! /bin/sh ## Note:** Replace all placeholders (`<TV_BOX_NAME>`, `<START_ADDR>`, `<SIZE>`) with your actual values. dd if=/dev/mmcblk1 of=rk3528-<TV_BOX_NAME>-android.dtb skip=<START_ADDR> count=<SIZE> bs=1 cp rk3528-<TV_BOX_NAME>-android.dtb /boot/dtb-$(uname -r)/rockchip/ sed -i '/fdtfile=/c\fdtfile=rockchip/rk3528-<TV_BOX_NAME>-android.dtb' /boot/armbianEnv.txt dtc -@ -I dtb -O dts -o rk3528-<TV_BOX_NAME>-android.dts rk3528-<TV_BOX_NAME>-android.dtb ``` ## contribute please report if you have success or anny problens. please contribute also Info to your box, embedded chips (wifi,RTC) and publish your DTB or DTS file.

Do you know if the access to Rockchip NPU is OK ?

All. After some more research I could dig further, but still no picture on the tft screen. It seemes, the same probelm already popped up elsewhere: https://github.com/notro/fbtft/issues/577 by using some ideas there, I could achieve the follwoing: [ 11.299717] fbtft: module is from the staging directory, the quality is unknown, you have been warned. [ 11.305551] fb_hktft32 spi1.0: fbtft_property_value: bpp = 16 [ 11.305563] fb_hktft32 spi1.0: fbtft_property_value: debug = 0 [ 11.305574] fb_hktft32 spi1.0: fbtft_property_value: rotate = 270 [ 11.305584] fb_hktft32 spi1.0: fbtft_property_value: fps = 20 [ 4.988032] /soc/spi@12d30000/hktft_cs_ogst@0: Fixed dependency cycle(s) with /soc/spi@12d30000/hktft_cs_ogst@0/hktft_cs_ogst_pins [ 11.305404] SPI driver fb_hktft32 has no spi_device_id for odroid,hktft32 [ 11.855462] graphics fb0: fb_hktft32 frame buffer, 320x240, 150 KiB video memory, 4 KiB buffer memory, fps=20, spi1.0 at 40 MHz Which seemes the display is visible by the system now. fbset mode "320x240" geometry 320 240 320 240 16 timings 0 0 0 0 0 0 0 nonstd 1 rgba 5/11,6/5,5/0,0/0 endmode following this route: https://unix.stackexchange.com/questions/20458/how-to-use-dev-fb0-as-a-console-from-userspace-or-output-text-to-it To use the framebuffer as console you need the fbdev module. Ok, let's see this. config-6.6.113-current-odroidxu4 has reference saying ONFIG_FRAMEBUFFER_CONSOLE=y so the above referenced fbdev should already be here. The lcd scripts coming with cloudhell al trying to send text to /dev/tty1 as the output console. So I assume, I should have something similar: dmesg|grep tty [ 0.000000] Kernel command line: splash=verbose console=ttySAC2,115200n8 console=tty1 consoleblank=0 loglevel=1 root=UUID=4cac61c9-e109-4524-9fd2-c9859f87842c rootfstype=ext4 rootwait rw drm_kms_helper.edid_firmware=edid/1024x768.bin smsc95xx.macaddr=00:1e:06:61:7a:55 governor=ondemand hdmi_tx_amp_lvl=31 hdmi_tx_lvl_ch0=3 hdmi_tx_lvl_ch1=3 hdmi_tx_lvl_ch2=3 hdmi_tx_emp_lvl=6 hdmi_clk_amp_lvl=31 hdmi_tx_res=0 HPD=false vout=dvi usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u [ 0.002547] printk: console [tty1] enabled [ 2.122547] 12c00000.serial: ttySAC0 at MMIO 0x12c00000 (irq = 124, base_baud = 0) is a S3C6400/10 [ 2.123447] 12c20000.serial: ttySAC2 at MMIO 0x12c20000 (irq = 125, base_baud = 0) is a S3C6400/10 [ 2.123502] printk: console [ttySAC2] enabled [ 9.707531] systemd[1]: Created slice system-serial\x2dgetty.slice - Slice /system/serial-getty. [ 9.716917] systemd[1]: Expecting device dev-ttySAC2.device - /dev/ttySAC2... ttySAC is the UART what I'm using at the moment. tty1 however is my main "screen", on the HDMI. So the question is, how should I able to tell the system to open an other tty console with fbdev for the LCD screen?