Hqnicolas

PR: included fd6551 https://github.com/armbian/build/pull/8666

h96-m9s-rk3576_defconfig rk3576-h96-m9s.dts rk3576-h96-m9s1.dts rc.local h96-m9.config rk3576-h96-m9s.dts h96-m9.tvb Compile-configuration.zip

Since it's an external driver, @Vincenzoernst1 you will still need to do all the process: Edit /boot/armbianEnv.txt to load the overlay user_overlays=tm16xx sudo apt install linux-headers-$(uname -r) # if it works, thats nice #if it doesn't you're cocked. Kernel module and display service Option 1: build and install in a single command Builds then installs module and service git clone https://github.com/jefflessard/tm16xx-display.git cd tm16xx-display make install Option 2: step by step commands make clean make module sudo make module-install sudo make service-install Check your display configuration display-service -c 3 phase display check Check that all leds are ON Check the order of digits and segment mapping (you should see "1234") Check each led name (ex: LAN icon is ON while "LAN" text is shown on the digits) I will include this section into a pull request: /dts-v1/; /plugin/; #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/leds/common.h> #include <dt-bindings/pinctrl/rockchip.h> &{/} { i2c-display { compatible = "i2c-gpio"; sda-gpios = <&gpio0 RK_PB4 (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)>; scl-gpios = <&gpio0 RK_PB3 (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)>; i2c-gpio,delay-us = <5>; #address-cells = <1>; #size-cells = <0>; display@24 { compatible = "fdhisi,fd6551"; reg = <0x24>; digits { #address-cells = <1>; #size-cells = <0>; digit@0 { reg = <0>; segments = <1 3>, <1 1>, <1 2>, <1 6>, <1 4>, <1 5>, <1 0>; }; digit@1 { reg = <1>; segments = <2 3>, <2 1>, <2 2>, <2 6>, <2 4>, <2 5>, <2 0>; }; digit@2 { reg = <2>; segments = <3 3>, <3 1>, <3 2>, <3 6>, <3 4>, <3 5>, <3 0>; }; digit@3 { reg = <3>; segments = <4 3>, <4 1>, <4 2>, <4 6>, <4 4>, <4 5>, <4 0>; }; }; leds { #address-cells = <2>; #size-cells = <0>; led@0,0 { reg = <0 0>; function = LED_FUNCTION_ALARM; }; led@0,1 { reg = <0 1>; function = LED_FUNCTION_USB; }; led@0,3 { reg = <0 3>; function = "play"; }; led@0,2 { reg = <0 2>; function = "pause"; }; led@0,4 { reg = <0 4>; function = "colon"; }; led@0,5 { reg = <0 5>; function = LED_FUNCTION_LAN; }; led@0,6 { reg = <0 6>; function = LED_FUNCTION_WLAN; }; }; }; }; };

This is an H96Max Factory default work around, no TV box device really turn off, it's the way the factory deal with the "remote control" power on function, the device is always waiting for a IR remote control to trigger. You can find a way around it on the pmic section from DTS. Thats a problem caused by BOM of materials in the factory, they start to use a new wifi card because of chip shortages. You can work around it using this method

You will need to flash an android "Update image" first, into EMMC, to go back to factory defaults. https://wiki.youyeetoo.com/en/YY3568/unpack https://drive.google.com/drive/folders/11BrqafnkEyFaM-D0gaPFhrmnRM47JAEU MaskRom mode upgrade firmware First of all, make sure that you have entered the MaskRom upgrade mode, and then perform the following firmware upgrade operations. Upgrade firmware in loader mode Open the AndroidTool tool, the board enters the upgrade mode, and a LOADER device will be found on the AndroidTool. Then perform the following upgrade firmware operation.

From @fevangelou 1. Install the "rkdeveloptool" tool first, as instructed in: https://docs.radxa.com/en/zero/zero3/low-level-dev/rkdeveloptool?host-os=debian sudo apt-get update sudo apt-get install -y libudev-dev libusb-1.0-0-dev dh-autoreconf pkg-config libusb-1.0 build-essential git wget git clone https://github.com/rockchip-linux/rkdeveloptool cd rkdeveloptool autoreconf -i ./configure make -j $(nproc) sudo cp rkdeveloptool /usr/local/sbin/ At the time of writing, this installed version 1.32. If you installed "rkdeveloptool" from Ubuntu's repos, it would install version 1.0 which may work, but let's be on the safe side here... 2. Connect and boot the device to loader/maskrom mode 2.1 While pressing the reset button (back/right) with a pin, connect the USB 2.0 port (back/left) and the power cable. Gotta be careful here not to miss the reset button pressing while connecting the cables. 2.2 Use the rkdeveloptool tool to identify the device and the mode it is on ("loader" or "maskrom"). $ rkdeveloptool ld ...should show the connected device if point 2.1 was successful - e.g. on my 8GB RAM device it printed this: DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=304 Loader Or after I had already flashed Armbian, it would show: DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=304 Maskrom (If you installed "rkdeveloptool" from Ubuntu's repo, the command is "rkdeveloptool list" if I recall correctly - every other "rkdeveloptool" command following though is the same) Now grab the latest release of Armbian for this device. At the time of writing it was: https://github.com/armbian/community/releases/download/25.11.0-trunk.106/Armbian_community_25.11.0-trunk.106_H96-tvbox-3566_bookworm_current_6.12.44_minimal.img.xz (the name of the device is on the filename) Extract the included .img file with (sudo apt install xz-tools): $ unxz Armbian_community_25.11.0-trunk.106_H96-tvbox-3566_bookworm_current_6.12.44_minimal.img.xz 2.2.1 If in "loader" mode (see the last part of the command's output above), simply flash Armbian directly. E.g. $ sudo rkdeveloptool wl 0x0 Armbian_community_25.11.0-trunk.106_H96-tvbox-3566_bookworm_current_6.12.44_minimal.img (if you attempt to flash the attached bootloaders, you'll get a "device not supported" error - Armbian already contains a bootloader) 2.2.2 If in "maskrom" mode (e.g. if you are re-flashing Armbian), flash the bootloader first: # For the 8GB RAM device use the attached (in this post) H96-MAX-8gb-MiniLoaderAll.bin file $ sudo rkdeveloptool db H96-MAX-8gb-MiniLoaderAll.bin # For the 4GB RAM device use the attached (in this post) H96-MAX-4gb-MiniLoaderAll.bin file $ sudo rkdeveloptool db H96-MAX-4gb-MiniLoaderAll.bin ...and then re-flash Armbian as you did the first time: $ sudo rkdeveloptool wl 0x0 Armbian_community_25.11.0-trunk.106_H96-tvbox-3566_bookworm_current_6.12.44_minimal.img 2.3 Reboot the device with: $ sudo rkdeveloptool rd Done! If all goes well, once you reboot the device you will be asked to set a root password and optionally a sudo user. Rebooting afterwards you should now be greeted with: _ _ _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ __ ___ _ __ _ __ _ _ _ _ (_) |_ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ / _/ _ \ ' \| ' \ || | ' \| | _| || | /_/ \_\_| |_|_|_|_.__/_\__,_|_||_|_\__\___/_|_|_|_|_|_\_,_|_||_|_|\__|\_, | |___| |__/ v25.11 rolling for h96-tvbox-3566 running Armbian Linux 6.12.44-current-rockchip64 Packages: Debian stable (bookworm), possible distro upgrade (trixie) Updates: Kernel upgrade enabled and 2 packages available for upgrade Support: for advanced users (rolling release) IPv4: (LAN) 192.168.1.10 (WAN) 1.2.3.4 Performance: Load: 3% Uptime: 2 min Memory usage: 2% of 7.50G CPU temp: 40°C Usage of /: 3% of 57G Commands: Configuration : armbian-config Upgrade : armbian-upgrade Monitoring : htop Last login: Sat Aug 30 12:47:54 2025 Key points: - If you do this the first time, it's obviously a matter of just flashing the latest Armbian image directly. - You don't need to open the device or compile Armbian.

For Linux CP2102 doesn't work at 1.5 megabaud or 1500000 baud. for linux I discovered the CH341A I2C programmer. I just set it to TTL by a jumper and use it as 1.5 megabaud TTL UART 1500000 baud

ADVANTECH EPC-R4680?

I bring the board up to use it on metal and Low level development, I use pci-e for jtag but I never considered the possibility of using an nvme there In my opinion, if you have a board that is running with internal emmc and sdcard you can provide an adjustment for pci-e NVME, It is a small adjustment, related to just one functionality of the board. I hope I'm not the only one with this board in my hands

S928X-K present in expensive devices like: VS10 Z9X ZIDOO Z9X 8K Zidoo Z3000 PRO-8K ZIDOO Z30 PRO-8K I think you could ask for the factory to support armbian http://forum.zidoo.tv/index.php http://forum.zidoo.tv/index.php?threads/beta-version-v6-4-06-for-z9x-z10-pro-z1000-pro-uhd3000-neo-s-neo-x-release.93680/page-18

the manufacturer hates us, that's it There is no method, they are all hobbyist experiments

@maka into this file: https://github.com/hqnicolas/ubuntu-rockchip-joshua/blob/main/config/suites/noble.sh it makes refference to the kernel repo: https://github.com/hqnicolas/linux-rockchip that contains the dts file: https://github.com/hqnicolas/linux-rockchip/blob/arm64--dts--rockchip--add-rk3566-h96max-v56/arch/arm64/boot/dts/rockchip/rk3566-h96max-v56.dts That have the USB setup: &usb2phy0 { status = "okay"; }; &usb2phy1 { status = "disabled"; }; &usb_host0_ehci { status = "disabled"; }; &usb_host0_ohci { status = "disabled"; }; &usb_host1_ehci { status = "disabled"; }; &usb_host1_ohci { status = "disabled"; }; &usbdrd_dwc3 { dr_mode = "host"; extcon = <&usb2phy0>; status = "okay"; }; &usbdrd30 { status = "okay"; }; &usbhost_dwc3 { status = "okay"; }; &usbhost30 { status = "okay"; }; &pinctrl { usb { vcc5v0_otg_en: vcc5v0-otg-en { rockchip,pins = <0 RK_PA5 RK_FUNC_GPIO &pcfg_pull_none>; }; }; There Are 3 Branches:

Never seen it, could be something that change this days

@mvpwar for RK3566 NPU you will need to use an armbian fork from Joshua Riek https://forum.armbian.com/topic/28895-efforts-to-develop-firmware-for-h96-max-v56-rk3566-8g64g/page/16/#findComment-211031 I think you will need to fork and rebuild it, the files got expired

I found this I hope it helps you @Luiz-SP

thanks @darcyg if you can, share it with us

Hello @mvpwar Download image Unzip

CP2102 are not capable of 1.5 megabaud in linux

did the 100mbps LAN make you work worse?

did you try it on windows? https://forum.armbian.com/topic/28895-efforts-to-develop-firmware-for-h96-max-v56-rk3566-8g64g/page/8/#findComment-187561

It could be a problem with the solder Buy a board from https://www.armbian.com/partners/