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.

Hi @Nick A — great work on these builds, I've been testing both your BSP (v0.6.4, kernel 6.6.98) and Mainline (V0.1, kernel 6.18.19) images on a Cubie A7Z with a custom carrier board. Both work well for general use. I've been trying to get a W5500 SPI-to-Ethernet chip working on SPI2 and ran into a consistent issue across both kernels that might be worth looking at. Issue: sunxi-spi-ng child device never gets probed The SPI2 controller itself initialises correctly on both kernels: sunxi-spi-ng 2542000.spi: probe success (Version 2.5.4) But the child device (spi2.0) never gets a driver bound to it. The w5100-spi driver is loaded, the modalias matches (spi:w5500), fw_devlink=off is set, yet: echo spi2.0 | tee /sys/bus/spi/drivers/w5100/bind → No such device echo spi2.0 | tee /sys/bus/spi/drivers_probe → accepted, no effect, zero dmesg output Dynamic debug enabled (module w5100 +p) → zero probe activity This reproduces on: Radxa BSP kernel 5.15.147-21-a733 (official r6 image) Your BSP build kernel 6.6.98 Your Mainline build kernel 6.18.19 All three use the same spi-sunxi-ng.ko / spi_sunxi_ng driver (same allwinner,sunxi-spi-v1.3 compatible string). Hardware confirmed good: the same W5500 chip on the same physical pins works perfectly when an ESP32-S3 is plugged in instead — DHCP, real network data, everything. Raw spidev access on the Radxa also reads correct W5500 registers. The bug is specifically in sunxi-spi-ng's child device registration preventing any driver from binding. Overlay used: dts /dts-v1/; /plugin/; &spi2 { status = "okay"; sunxi,spi-bus-mode = <1>; sunxi,spi-cs-mode = <0>; eth0: ethernet@0 { compatible = "wiznet,w5500"; reg = <0>; spi-max-frequency = <20000000>; }; }; Note: sunxi,spi-bus-mode = <0> is rejected at probe time with error -22 ("unsupport hw bus mode 0x0"), so <1> is the only accepted value. Has anyone else seen this? Is there a known workaround for getting SPI child devices to bind under sunxi-spi-ng on A733?