Link Star H68K is, according to multiple sources, exactly the same as Hinlink H68K. But that's not the problem (yet). I'd been using an old version of RKDevTool (2.84 IIRC) which was unable to load the .img file from the Armbian site, but uninformative as to the nature of the problem. Updating to RKDevTool 3.37 at least yielded an error message when attempting to load the image: Googling this suggests a corrupted download (not the problem here, the SHA sum matches) or a raw .img format rather than the packed .img format expected by RKDevTool. So I compiled an image according to the Armbian Build Framework instructions. Same error message. More Googling suggests that a couple of Linux CLI utilities, upgrade_tool or rkdeveloptool, may be able to flash a raw image to the board's EMMC. More later...

After boot, check systemctl status easy-eai-nano-bcmdhd.service --no-pager journalctl -u easy-eai-nano-bcmdhd.service -b --no-pager ls -l /lib/firmware/fw_bcm43455c0_ag.bin /lib/firmware/nvram_ap6255.txt dmesg | grep -Ei 'bcmdhd|dhd|4345|ap6255|firmware|nvram|wlan|sdio' iw dev rfkill list tr -d '\0' </proc/device-tree/wireless-wlan/wifi_chip_type; echo dmesg | grep -Ei 'rfkill_wlan|bcmdhd|dhd|4345|ap6255|firmware|nvram|wlan' lsmod | grep -E 'bcmdhd|dhd_static|rfkill' iw dev rfkill list modinfo bcmdhd_sdio cat /etc/modprobe.d/bcmdhd-easy-eai-nano.conf dmesg | grep -Ei 'bcmdhd|dhd|43430|43438|ap6212|firmware|nvram|wlan' iw dev rfkill list

With the aid of Claude.Ai .. v26.5.1 for Rock 5A running Armbian Linux 6.18.35-current-rockchip64 Starting Point is the Radxa DTS needed to add an include ... #include <dt-bindings/soc/rockchip,vop2.h> Modified this section. Changed the compatible string, added the power-supply key and fixed the active area (width and height) dsi0_panel: panel@0 { status = "okay"; compatible = "panel-dsi-simple"; reg = <0>; backlight = <&dsi0_backlight>; power-supply = <&vcc_lcd_mipi0>; vdd-supply = <&vcc_lcd_mipi0>; vccio-supply = <&vcc_1v8_s0>; reset-gpios = <&gpio3 RK_PC1 GPIO_ACTIVE_HIGH>; pinctrl-names = "default"; pinctrl-0 = <&dsi0_lcd_rst_gpio>; prepare-delay-ms = <120>; reset-delay-ms = <120>; init-delay-ms = <120>; enable-delay-ms = <100>; disable-delay-ms = <120>; unprepare-delay-ms = <120>; width-mm = <135>; height-mm = <217>; Modified this section (renamed the endpoint) &mipi_dcphy0 { status = "okay"; }; &route_dsi0 { status = "okay"; connect = <&vp3_out_dsi0>; }; &dsi0_in_vp2 { status = "disabled"; }; &dsi0_in_vp3 { status = "okay"; }; to simply &mipidcphy0 { status = "okay"; }; Added this section / endpoint &vp3 { #address-cells = <1>; #size-cells = <0>; vp3_out_dsi0: endpoint@ROCKCHIP_VOP2_EP_MIPI0 { reg = <ROCKCHIP_VOP2_EP_MIPI0>; remote-endpoint = <&dsi0_in_vp3>; }; }; And then completely redid the i2c touch controller section to be &i2c5 { status = "okay"; pinctrl-names = "default"; pinctrl-0 = <&i2c5m2_xfer>; clock-frequency = <400000>; #address-cells = <1>; #size-cells = <0>; gt9xx: gt9271@14 { status = "okay"; compatible = "goodix,gt9271"; reg = <0x14>; pinctrl-names = "default"; pinctrl-0 = <&gt9xx_gpio>; interrupt-parent = <&gpio3>; interrupts = <RK_PC6 IRQ_TYPE_EDGE_FALLING>; irq-gpios = <&gpio3 RK_PC6 GPIO_ACTIVE_HIGH>; reset-gpios = <&gpio3 RK_PC5 GPIO_ACTIVE_HIGH>; touchscreen-size-x = <1200>; touchscreen-size-y = <1920>; AVDD28-supply = <&vcc_tp>; VDDIO-supply = <&vcc_tp>; }; Final DTS is attached. Worked for 6.18.53. I had Claude write a bash script to pull everything and make the required changes and compile the device tree and can make it available, if needed. rock-5a-radxa-display-10fhd.dts

@Guido Giuntoli You are a candidate to test the new feature. https://github.com/armbian/build/pull/10113

I successfully got the Radxa Display10FHD display working this weekend on Armbian 26.5.1 (Gnome) after extensive Claude AI help in fixing default Radxa DTS. I'll do a separate post / topic for that but it involved refactoring some of the endpoints, adding a missing header and fixing the touchscreen driver name. I used Claude and it was really helpful.