WINEDS

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

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.

@WINEDS@Hqnicolas Thank you for your help. I will try to see if it can run normally.

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

Hi all.
I just made a video where I show how to build your own Armbian images on Windows.
It used to be that you needed a virtualMachine running Linux but these days you can use WSL2.
Here the video :
Greetings, NicoD

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>;
            };
        };
 

yes.
 
Things that can be tried:
 
- DTS
 
phy-mode = "rgmii-id"; or phy-mode = "rgmii-rxid";
 
- UBOOT
 
CONFIG_PHY_REALTEK=y
CONFIG_DWC_ETH_QOS=y
CONFIG_DWC_ETH_QOS_ROCKCHIP=y
CONFIG_DM_PMIC=y
CONFIG_PMIC_RK8XX=y
CONFIG_REGULATOR_RK8XX=y
CONFIG_PWM_ROCKCHIP=y

Can you boot in a working ethernet and then reboot to this trial?

I know that told you the ID of your chip but also told you to switch to phy1 but you didn't. I think It is possible to use the generic driver but don't know if It will work. Changes in dtb must be accurate.

I see this on your dts:
 
ethernet-phy@1 {
                                 compatible = "ethernet-phy-id7b74.4411", "ethernet-phy-ieee802.3-c22";
                
But I think should be:
 
ethernet-phy@1 {
                               compatible = "ethernet-phy-ieee802.3-c22";
                                reg = <0x01>; 
 
And try to use the generic driver for ethernet.

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
 

Bluetooth is fixed with AIC8800 wifi module.  Credit to @pocosparc  
 
 
Changed DTS Bluetooth node as per at least change suggestion.  @pocosparc did you confirm optical SPDIF as working?  My port is not illuminated.
 

Hi @Hqnicolas
 
I am currently still doing some research as I found out that Bluetooth does not work and it has to do something with the UART1 line. I will first try to fetch the low-hanging fruits.
Meanwhile, I replaced the debian with ubuntu image for now and I extracted all of the firmware drivers from my backup dump from the super.img file. I am attaching them to this post and they are coming from the vendor/firmware part. I currently do not know if they need to be statically or dynamically linked with the kernel. If they help in any way, we can include them in the armbian Linux. Link
 
I have a few questions for you as well. Do we have some sort of PCBA schematics and the HW setup with the external hardware: direct pins connections, what goes via muxes, etc.? This would speed things up. I requested this from the buyer, but the chances are really low that he will send anything back. 
What is the latest dts version? Do we have it in the form of mnemonics and not as bare pointers in byte values (&gpio instead of some 0x8e value)?
 
Now to the Bluetooth problem
I found somewhere in this forum that someone fixed the Bluetooth by changing the TX and RX pins in the dts. Link to git commit
 
Looking at what is currently in (I am using some rk3566-firefly-roc-pc.dts - there are multiple of them and changes are phandles for USB 2.0) and what is in the git and the version originally coming from this device show that there is a TX and RX swap in the file (maybe due to different PCB layouts and hoping that there is one bit that allows UART alternate function RX/TX swap - not sure as the datasheet for RK3566 is far from being useful).
 
So the file should be at least changed to:
bluetooth { compatible = "brcm,bcm43438-bt"; clocks = <0x8d 0x01>; clock-names = "lpo"; device-wake-gpios = <0x8e 0x10 0x00>; host-wake-gpios = <0x8e 0x11 0x00>; shutdown-gpios = <0x8e 0x0f 0x00>; pinctrl-names = "default"; pinctrl-0 = <0x8f 0x90 0x91>; vbat-supply = <0x24>; vddio-supply = <0x92>; status = "disabled"; };  
In the original dump file there is also UART8 messing around, but I am currently not sure what her role is. @Hqnicolas If you have everything setup on you side, can you quickly check this out? Or I will try to fiddle around with armbian-config and device tree entries and let's see where it gets me.

I think your driver is already in armbian, but your chip is not identified. To get it working you can identify it in the ethernet node this way:
 
mdio {
            compatible = "snps,dwmac-mdio";
            #address-cells = < 0x01 >;
            #size-cells = < 0x00 >;
            ethernet-phy@1 {
                compatible = "ethernet-phy-ieee802.3-c22"; ====> compatible = "ethernet-phy-id7b74.4411", "ethernet-phy-ieee802.3-c22";

https://kanyi.gm/how-to-install-and-enable-aic8800-chipset-wi-fi-driver-for-linux/
 
Some people have problems with this device
There’s no denying that the AIC8800 is a terrible component for a linux desktop/server. Its manufacturer has not made any effort to upstream the drivers. Either you live with no WLAN/BT or you live with DKMS package.

Thanks maka for replying.  Issue is resolved and Ethernet is working now.  I did not read the first email from Maxio tech properly and I was sent files for MAE0621A-Q3C rather than the MAE0621A-Q2C which I have.  Maxio tech kindly sent me files for MAE0621A-Q2C yesterday and I managed to compile it into the current kernel 6.12.24

The driver is well so the problem seems you are in the wrong ethernet phy. Change from phy0 to phy1 in the ethernet node.