Hqnicolas

Only Chinese will know, the M9s have sale restriction for other country then china I bet they saved on thermal dissipation m9s = Product weight: 166g m9s = Package weight: 470g M9s Video m9 = Product weight: 180g m9 = Packaging weight: 550g M9 Video @hy aska before test any image, make a full backup of your device....

@max-ermilov @hzdm @Tusemanu As the VPU was working on this kernel, if somebody want to test NPU, GPU and VPU integration, I recomend Frigate: https://docs.frigate.video/frigate/installation/#rockchip-platform Object detector: https://docs.frigate.video/configuration/object_detectors#rockchip-platform Video Processor: https://docs.frigate.video/configuration/hardware_acceleration#rockchip-platform

As @maka and @Vincenzoernst1 related, the VPU was working if somebody want to test NPU, GPU and VPU integration, I recomend Frigate: https://docs.frigate.video/frigate/installation/#rockchip-platform

@Vincenzoernst1 thanks for the advice, i made a Pull Request (PR) to enable kernel 6.9 Current and 6.11 Edge https://github.com/armbian/build/pull/7310/files now the community releases will build 6.9 and 6.11 for this box, Please test and keep a copy of it.

i think i'ts a 5V power brick. if you put 12v the regulator is burned, if you use the original 5v, check the power brick P2 Jack polarity and voltage. the original power brick it's not the most reliable

@maka can you update the h96 max scripts to reach this kernel version? we are stuck in 6.6.... since 6.8 I think i'ts impossible to boot.... @pocosparc I just see today what you did to the https://github.com/hqnicolas/ArmBoardBringUp/tree/main can you show your case? I haven't heard anything more about your openVFD project

Look at the 3566 development https://forum.armbian.com/topic/28895-efforts-to-develop-firmware-for-h96-max-v56-rk3566-8g64g/ You can bring the board to mainline By creating a folder like this based on @hzdm files up there in this topic https://github.com/hqnicolas/ArmBoardBringUp https://forum.armbian.com/topic/40483-efforts-to-develop-firmware-for-h96-max-m9-rk3576-tv-box-8g128g/?do=findComment&comment=200260

Did you compile kernel 6.9?

@hzdm share it with us! armsom-sige5-rk3576_defconfig armsom-sige5-rk3576_defconfig

the only bootable device for u-boot is SATA, SDCARD, EMMC or UFS2.0 by pci-e I have never seen boot from USB or LAN sata0 = "/sata@2a240000"; sata1 = "/sata@2a250000"; ufs = "/ufs@2a2d0000"; sdmmc = "/mmc@2a310000"; sdio = "/mmc@2a320000"; sdhci = "/mmc@2a330000"; what you can do to boot from external device? Solder an SD-CARD Reader

here in this topic we dont use rk817 probe, the devices not even have a metalic connector to feedback here we remove it because the output was optic audio @Werner can you take @ioncube to orangepi3b topic?

We left this method behind in 2022, Our focus here is To compile mainline Linux @hzdm did an armbian compilated with vendor kernel, that is better then reverse engineer another device kernel. but over time, the device will be stuck on a kernel that has little support, thus making the idea of compiling the mainline 6.8 kernel an ideal

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