Hqnicolas

For this 16xx displays we need to ask @Jean-Francois Lessard he was in contact with this drivers for a while. 
these 16xx displays will be included in the mainline 6.18 drivers as tm16xx_i2c

make sure to adjust your device according to this repository to benefit from the update
https://github.com/jefflessard/tm16xx-display

leave a link for other users like @John Taylor to continue your work, also @fedes_gl could give a hand

Scroll back and read all my posts from April 11 onwards (page 17).  On Radxa's github there are Wifi/BT drivers for AIC8800.  They are at version 4 now :
 
https://github.com/radxa-pkg/aic8800/releases/tag/4.0%2Bgit20250410.b99ca8b6-3
 
Also to fix BT :
 
sudo crontab -e
then add the line :
@reboot sudo hciattach -s 1500000 /dev/ttyS1 any 1500000 flow nosleep
 
then reboot the H96.

I've successfully booted Armbian from USB following the tutorial above, and I've managed to write Armbian from the USB drive to the eMMC. Now I want to create an Armbian firmware that can be directly flashed to the H96 M9/S eMMC using RKDevTool.exe, but I'm not very smart - even simple things take me a very long time to figure out. If any of you have this, please share it. If I manage to figure it out, I'll also share my findings.

This case is a clone of X88PRO:
 
 
However i use HK1 rom because regular x88pro lack of many features like saf  and without this dolphin-emu and others dont allow use external devices

another thing added in HK1 rom is cpu thermals, cpu load and memory load in status bar

but use this rom make frontal screen in tvbox dont work
 
 
In my case armbian works using information from this themes:
 
 
 
armbian used is based on station-m2 image from here:
 
https://www.armbian.com/station-m2/

https://github.com/armbian/community
 
 
HDMI - works (need to check hot plugging)
HDMI sound - works
USB 2.0 - works
USB 3.0 - works (using now usb 3.0 hub with power adapter)
LAN - Works
WLAN - Works
SD-Card booting and detection - works
RKDevTool installing and loading images on/from eMMC - works
GPU - works
Hardware video acceleration (except for browsers) - works
Dualboot if you flash new bootloader (SD-Card boot high priority) - works
 
Loader* from vontar work ok for use sd boot
 
*For use this follow steps in vontar guide, work ok in dual boot (armbian on sd and android in emmc)
 
sd used is a microdata 64gb from aliexpress (work ok):
 
https://es.aliexpress.com/item/1005007142224952.html
 
 
rk3566-box-demo.dtb dont recognize usb keyboard but using rk3566-box-demo_x96x6_24_custom.dtb from x96 x6 theme work correctly and hub work on usb 2.0 and on usb 3.0 too

also in usb 3.0 port have a 500GB HDD Laptop USB Drive 
 
In other things can install xfce desktop, lightdm,  xorg, chromium, firefox, nm (for lan), xarchiver, dolphin appimage

also can enable panvk using this:

VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/panfrost_icd.aarch64.json PAN_I_WANT_A_BROKEN_VULKAN_DRIVER=1
 
from here:
 
 
 
Add some images of tvbox, i make a mod (i dont have experience with tools) for add a fan, results are very impressive this tvbox at max stay around 79 to 80 degrees but now with fan stay around 35 to 45 degrees
 

 
 

 
 

 
 

 
 
Images from system
 

 
 

 
 
Dolphin-emu 2506
 

 

 

Author: @WINEDS 

How to Build Armbian with Maxio Ethernet Support for H96 V56 (2025 Model)
 
If you own the H96 V56 (2025 model) TV box and want to run Armbian with full Gigabit Ethernet support, you might have noticed that the stock kernel doesn't always support the Maxio Ethernet chip out of the box.
In this guide, we’ll walk through the most accessible method to build a custom Armbian image with the necessary kernel modules using Windows Subsystem for Linux (WSL).
 
Refer to https://docs.armbian.com/Developer-Guide_Build-Preparation/ and note hardware requirements then in a Windows Powershell console select Ubuntu (using down arrow in title bar) and type to update the system:
 
sudo apt update sudo apt upgrade  
Prerequisites
A Windows PC with WSL (Ubuntu) installed. The specific patch file (my_v2_patch.patch) and DTB file (my_board_df.dtb) mentioned in the documentation. Patience (the build process can take a few hours). Step 1: Prepare Your Environment
First, ensure your WSL instance has enough resources. Go to your WSL settings (typically via a .wslconfig file or the settings menu) and allocate about 75% of your CPU cores and RAM to ensure the build doesn't crash.
Open your Ubuntu terminal in Windows PowerShell and update your system:
sudo apt update
sudo apt upgrade
 
Step 2: Get the Armbian Build System
Clone the official Armbian build repository and enter the directory:
 
git clone [https://github.com/armbian/build](https://github.com/armbian/build) cd build
 
Step 3: Apply the Kernel Patch
You need to patch the kernel to support the specific hardware. Create the directory tree for the patch:
 
mkdir -p ./userpatches/kernel/archive/rockchip64-6.12
 
Using Windows File Explorer, copy your my_v2_patch.patch file into this newly created directory (rockchip64-6.12).
 
Step 4: Run the Build Command
Now, kick off the compilation process. We will build a Gnome desktop image based on the Noble release. Run the following command (copy and paste this as one line):
 
./compile.sh build BOARD=h96-tvbox-3566 BRANCH=current BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED=browsers DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base KERNEL_CONFIGURE=yes RELEASE=noble
 
Step 5: Configure the Kernel (Crucial Step)
After the build runs for a while, the blue Kernel Configuration menu will appear. This is where you enable the Ethernet driver.
Use the arrow keys to navigate to Device Drivers.
 

Select Network device support. Select PHY Device support and Infrastructure. Scroll down to find MAXIO PHYs. Press the Space bar until you see an <M> next to it (this modularizes the feature). Once selected, use the Tab key to select Exit and keep selecting Exit until you leave the configuration menu. Select "Yes" when asked to save the kernel configuration. Step 6: Retrieve Your Image
The build will continue (potentially for a few hours). Once finished, your new image file will be located in:
output/images
 

 
 
Step 7: Post-Installation Setup
Flash the image to your SD card/eMMC and boot the device. To get the Ethernet working, you need to update the Device Tree Blob (DTB).
Copy the file my_board_df.dtb to /boot/dtb/rockchip/ on the device. Edit the boot environment file: sudo nano /boot/armbianEnv.txt Change the fdtfile line to point to your new DTB: fdtfile=rockchip/my_board_df.dtb
 
Press Ctrl+X, then Y to save.
Reboot your H96 V56, and you should now enjoy full Gigabit Ethernet speeds!
my_board_df.dtb

@王类 here are instructions to build an armbian image with maxio kernel module.  It applies to current LTS kernel version 6.12.58.  Its mostly cut and paste and uses windows so I hope you can try this!
 
@maka I'll keep working on your suggestions.  Many thanks!
 
 
my_board_df.dtb
maxio_install.pdf

ok same error.   The maxio module works with this snippet though :
 
 
mdio {
            compatible = "snps,dwmac-mdio";
            #address-cells = <0x01>;
            #size-cells = <0x00>;
            phandle = <0xee>;
            ethernet-phy@0 {
                compatible = "ethernet-phy-id7b74.4411", "ethernet-phy-ieee802.3-c22"
                reg = <0x00>;
                status = "okay";
                phandle = <0x51>;
            };
        };
 

That's nice,
I don't have this new board BOM, be free to add the variant, I think board variants are included using a .dtso file
 
 
for armbian i think we cannot include tirth party drivers, but any changes to .dts could be included into a .dtso file
 
 
that's a way to enable this variant into mainline armbian

You can ask for other users to publish they ROM images, but, the ideal way is to compile your own images, since this is a custom driver, I think it's a safe way to go. 
You can share some pictures images from the board, so we can confirm your WiFi board and lan chip.
 

this link is private, please change it to public,
 
 

 

Please open the case and post images of your board so we can see what Ethernet chip you have.
 

In this case ethernet chip is realtek so it should be supported by armbian kernel?  So problem is to find or make a modern DTS for this board?  

The manufacturer changed the BOM list of materials to lower the product's cost, and now you have a different version with different Wi-Fi and LAN controllers.

@WINEDS have some fixes: 

Files
Link 
Link 
Link
 
 
 
 
 
DIffWifiLanCards.zip maxio.c my_rk3566-h96-tvbox3.dtb my_rk3566-h96-tvbox3.dts my_v1_patch.patch README Release Note.txt v1_patch.patch

Some manufactures change the wifi and lan controllers to keep prices down on new BOM of materials:
@WINEDS got experience with thos problems
https://forum.armbian.com/topic/28895-efforts-to-develop-firmware-for-h96-max-v56-rk3566-8g64g/page/16/#comment-210825
https://forum.armbian.com/topic/28895-efforts-to-develop-firmware-for-h96-max-v56-rk3566-8g64g/#findComment-217289
https://forum.armbian.com/topic/28895-efforts-to-develop-firmware-for-h96-max-v56-rk3566-8g64g/#findComment-216154
 

# 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. 
 

Success! 
 
It's still showing that first error, but using  meson-gxbb-wetek-play2.dtb it was able to boot up and configure.
Wifi works also.
 
You guys are amazing! Thanks for all your inputs. 

The rk3588 soc has a fixed boot order which is spi, emmc, microsd, other I think. So if there is a boot loader found on spi it will ignore other options and try to boot from that. 
While Armbian uboot binaries on spi are instructed to check if there is a microsd card inserted and boot from that, vendors can (ab)use this circumstance to make it harder for other operation systems being used because tools like rkdevtool are necessary to get rid of it. If the spi is pre-flashed with crap, I guess that's why the step is necessary.

Apparently, there are more versions of the box. One has two stars on the nameplate and "V 1.4" printed on the PCB.
Although WiFi works on version 1.2, if  does not work on this version
V1.4 has a different Wi-Fi chip: EA6521.
dmesg | grep 'SDIO'  gives:
 [    9.621165] mmc2: new ultra high speed SDR104 SDIO card at address 8800

After this test, you might try a boot just with forcing the mode, without edid:
extraargs=video=HDMI-A-1:1920x1080@60 drm.debug=0x4  

@jock this is the user-overlay patch I am using to enable both leds on the board. The "working" led is as usual a couple of alternating leds of red/blue. The led-ir is a standalone blue, I have triggered one to the "timer" and the other to "activity" , both running.
I can confirm bluetooth, IR remote receiver are also working. Bluetooth needs BCM.hd (I have used BCM43342.hcd).
For the wifi 2/5G the correct overlay is rk3318-box-wlan-ap6334.
HDMI, despite apparently is initialized correctly and answering to all commands still gives a black screen. 
 
rk3318-box-led-overlay-ledA.dtso.txt

You need to imagine it as a chip, the entire board; each change to the board alters the description of the "chip" you're referring to. Search for your board model on the forum. I don't own any boards using RK3399, but I believe you can find several users mentioning the board on the forum. for YY3568 board, the factory already have all information https://wiki.youyeetoo.com/en/YY3568/sdCardSystem

You describe my everyday 

so, did you try to flash the original Android image with RkDevTools?
https://drive.google.com/file/d/14HWcHYHDrgUBFWholrDCKUWDPHw1r4F1/view

@guenter

Test Image: Armbian-unofficial_25.11.0-trunk_H96-tvbox-3566_bookworm_edge_6.16.10_gnome_desktop.xz

data for H96 Max RK3566 Box:
No external drivers, no external app, just pure mainline.....
https://github.com/armbian/build/pull/8708 

Success!
 
Yesterday late in the evening I managed to boot from usb. What I did was burn Armbian-unofficial_24.11.0-trunk_Armsom-sige5_noble_vendor_6.1.75_minimal to a USB drive, replace the dtb with the one from Android and boot with the commands "usb start" and "run bootcmd_usb0".
 
I couldn't get ROC's image nor Multiboot (with the replaced dtb) to boot this way.
 

 
EDIT: Installed it to eMMC and ran sbc-bench - results https://0x0.st/Xvsr.bin
 
 
When I plug in the HDMI, it crashes Will have to investigate.
dwhdmi-rockchip 27da0000.hdmi: i2c read err!