Hqnicolas

Great Idea!! @Tusemanu you mean uefi images, you can make it work like this example it's not easy to find a "bios" or "uefi" translation layer for rk3576 @Tusemanu your proposal would only be possible with UEFI boot, without UEFI boot your OS can't estimate which pin goes where inside the board.

@hzdm My country looks like North Korea today, no way to import any goods, even starlink was sacrificed by the government. Just Another box, reset button for rk3566 also stop working with mainline bootloader 2024.7. the dtb need to enable correct pmic pins on uboot. the uboot DTB file isn't correct for this box. uboot.dtb pmic { interrupt-parent = "from android pinout" interrupts = "from android pinout" } @amazingfate was working on Video acceleration for RK3566 very likely that his work will also reach the rk3576 chips If you notice, this is one of the first works with rk3576, you are well ahead of the other devices. the potential was here "H.265, H.264, VP9, AV1 4K@60fps" This is also an bootloader workaround You can find Armson Sige 5 things and BPI-M5 uboot to fix this H96 max RK3576 bootloader Armsom sige 5 = banana pi BPI-M5 Firefly EC-R3576PC = Firefly ROC rk3576 PC

my smartphone used to be too, but we are here together to make things better and leave android behind if you didn't like the idea of opening your topic on XDA developers you can open it on the 4pda forum talks about android, here we don't really use android at armbian the topic is always linux

hello @hendrithy the topic here are exclusive to linux development I believe you want to talk about android and DocumentsUI application a good place for you to find your answers in this android field is xda Foruns I don't use Android, My cell Phone Runs Alpine Linux

this is why it's easy to make a DTS for linux instead of debug android dts on it. try to use the dts conversion method and work within the mainline standard for linux, things are easier to work with because inside the mainline is where everyone is compiling the kernel config this is inside image boot folder armbian text file

Good news, now you know your wifi controller: AP6275P take your DTS file Disable the HT5010 Disable mtd_vendor_storage Disable hdmi sound disable phy0 disable 'drm-cubic-lut@0' and all android related memory stuff recompile to dtb and try again....

congratulations! bring the compile commands to the public for other users to reproduce

I think you can use the vendor kernel 6.1 with Android 14 DTS the diffefence only happend for mainline linux Can you share some benchmarks for chromium for video decoding? also install glmark2-es2-wayland and run it try to compile the Joshua 6.1 it uses github CI/CD method to compile online here is my example how i did it: to enable rk3566 h96 you can edit this file to make it work on your box

translate it from android to linux format: change the armson sige5 vendor DTS for the following:

You will need a custom uboot to make it I don't know if the factory make the android bootloader USB friendly That's why we are here that's why you need a custom DTS, Android DTB = Kernel 4.19 ≠ Mainline DTB = Kernel 6+ I want to train an LLM to do this DTS translation it's too boring You will need to create files like this using armson siege5 as rk3576 base config and this dts overlays as a start point

@cmuki Please be carefull Mekotronics R57 uses LPDDR5 and UFS flash this loader has different settings than your box you need to backup the mini loader from your box. ask for the original firmware on the factory: +86 17840901693 +86 13242412680 vivian@h96tvbox.com sales10@h96tvbox.com you can extract it from the @mvpwar backup with imgrepackerRK

You will use the same u-boot from roc-rk3576-pc https://gitlab.com/firefly-linux/manifests/-/tree/master/rk3576?ref_type=heads https://gitlab.com/firefly-linux/manifests/-/blob/master/rk3576_linux_bsp_next.xml?ref_type=heads Looking through entire web to find these files: Rk3576-firefly-demo.dtsi roc-rk3566-pc.dts And EC-R3576PC FD Nothing found, looks like somebody make the pooh bear hangry

https://github.com/Joshua-Riek/linux-rockchip/blob/noble/arch/arm64/boot/dts/rockchip/rk3576-evb1-v10-linux.dts https://github.com/Joshua-Riek/linux-rockchip/blob/noble/arch/arm64/boot/dts/rockchip/rk3576-linux.dtsi https://github.com/Joshua-Riek/linux-rockchip/blob/noble/arch/arm64/boot/dts/rockchip/rk3576-evb1.dtsi https://github.com/Joshua-Riek/linux-rockchip/blob/noble/arch/arm64/boot/dts/rockchip/rk3576-linux.dtsi Overlay this files to create an dts

use armson siege5 as rk3576 base config https://wiki.t-firefly.com/en/ROC-RK3576-PC/linux_dts_manual.html some tools that can help you you can use this firmware as base to build your linux dts wifi drivers that can be usefull for rk3576 flashing tools for linux windows and macOS

Lets Start with an example: Leds: On Android DTS we have: and on Linux Rockchip: So we can do an Linux compatible with h96 M9 rk3576:

yes, to create a image you will need to use the rockdev maybe a newer version exist baseparameter have all information about the image file that you will need to configure rockdev how @mvpwar make a backup this process generate two files: File1: Linux_Pack_Firmware/rockdev/Image/update.img File2: Linux_Pack_Firmware/rockdev/update.img I generally use the File2 to flash my device on upgrade Firmware RKDevTool I think we need to ask redScorpio to an new decompiler This is the old for rk3566 to extract DTB file from this DTB image you will need imgutil example of usage how to mess with DTS files from android DTB 1.DTS 2.DTS thats all you need to compile a new DTS file for linux this device uses fragmented DTB file with overlay every DTB overlay the first 1.dts 2.dts 3.dts 4.dts 5.dts

So, keep a copy from this h96 armbian community, because in the future it may be useful, we left a period where the board was not working.

So, keep a copy from this h96 armbian community, because in the future it may be useful, we left a period where the board was not working.

let's try with linux with rkdeveloptool

@pessimism Did you keep those spare SD card readers?

I want to make it clear to everyone that now The H96 MAX Became Full supported by armbian Mainline 26/08/2024 Latest Release: https://github.com/armbian/community/releases/tag/24.11.0-trunk.25 desktop: https://github.com/armbian/community/releases/download/24.11.0-trunk.25/Armbian_community_24.11.0-trunk.25_H96-tvbox-3566_noble_current_6.6.47_gnome_desktop.img.xz Server: https://github.com/armbian/community/releases/download/24.11.0-trunk.25/Armbian_community_24.11.0-trunk.25_H96-tvbox-3566_bookworm_current_6.6.47_minimal.img.xz

I want to make it clear to everyone that now The H96 MAX Became Full supported by armbian Mainline 26/08/2024 Latest Release: https://github.com/armbian/community/releases/tag/24.11.0-trunk.25 desktop: https://github.com/armbian/community/releases/download/24.11.0-trunk.25/Armbian_community_24.11.0-trunk.25_H96-tvbox-3566_noble_current_6.6.47_gnome_desktop.img.xz Server: https://github.com/armbian/community/releases/download/24.11.0-trunk.25/Armbian_community_24.11.0-trunk.25_H96-tvbox-3566_bookworm_current_6.6.47_minimal.img.xz

You can use the Radxa Rock 2F as a base, remove all USB ports from DTS/DTB by commenting the code inside DTS text remove wifi/bluetooth by commenting the code inside DTS text check for the EMMC0 EMMC1 EMMC2 SDHCI device boot position compile the armbian for Radxa Rock 2F and test it

@Vincenzoernst1 I have no interest in fixing this I'm not going to keep polishing software since I already know how to get around the problem If you want, you can make a pull request creating an exclusive dts/dtb for the h96 max within uboot 2024/7 including the maskroom button I can help direct your efforts here

thinks changed in august 24.8.0 Trunk554 now the Mainline Uboot dont reconize the maskroom buttom, feel free to fix this erro on Uboot dtb/dts files.