Efforts to develop firmware for H96 MAX M9 RK3576 TV Box 8G/128G

[Hqnicolas]

@cmuki

try to run https://forum.armbian.com/topic/40483-efforts-to-develop-firmware-for-h96-max-m9-rk3576-tv-box-8g128g/#findComment-202914
your benchmark shows the rknpu
Status of performance related governors found below /sys (w/o cpufreq): * dmc: dmc_ondemand / 528 MHz (rknpu_ondemand dmc_ondemand userspace powersave performance simple_ondemand / 528 1068 1560 2112) * 27700000.npu: rknpu_ondemand / 300 MHz (rknpu_ondemand dmc_ondemand userspace powersave performance simple_ondemand / 300 400 500 600 700 800 900 1000)

 

[Tusemanu]

26.11.2024 в 14:38, Hqnicolas сказал:

your benchmark shows the rknpu

Hello.

Those. Is RKNPU working correctly?

Have you tried VPU, GPU, does it work?

[Hqnicolas]

On 12/3/2024 at 9:52 AM, Tusemanu said:

Those. Is RKNPU working correctly?

Have you tried VPU, GPU, does it work?

for tv-box it's all at your own risk

anything you find in this thread should always be considered non-functional or unreleased
do not buy any tv-box, buy only official boards from manufacturers https://www.armbian.com/partners/

[kevchi]

Hi all. Any idea how to root the device?

[tnt]

has anyone managed to save the changed u-boot environment? it seems that uboot.img is a binary u-boot file that stores the environment variables that are set during compilation.

Edited December 22, 2024 by tnt
add remark

[Hqnicolas]

On 12/22/2024 at 9:24 AM, tnt said:

has anyone managed to save the changed u-boot environment?

 

You don't need to save the u-boot env, it's included in your armbian build.
@tnt don't trust any image from factory or other forum users, just build your own images.

 

On 9/13/2024 at 4:51 PM, hzdm said:

I was able to fix the reset button in U-boot.
I got the uboot.dtb file from the Android firmware.
To add it to the build - you need to replace the armsom-sige5-rk3576_defconfig file in the build/patch/u-boot/legacy/u-boot-armsom-rk3576/defconfig/ directory

 

armsom-sige5-rk3576_defconfig

Edited January 2 by Hqnicolas

[Hqnicolas]

On 12/21/2024 at 7:11 AM, kevchi said:

Hi all. Any idea how to root the device?

this is an Linux development community,
Here is an tutorial for android users: https://youtu.be/1vpepaQ-VQQ

 

[Freeze]

Hello.

Thanks for your work, fine result.

 

i've tested desktop image and..

1) For begginers, before executing the command "rkdeveloptool db...", make sure that the board is in operation mode => maskrom
 

rkdeveloptool list

rkdeveloptool rd 3

 

#and after that h96 ready to:

rkdeveloptool db RK3576_MiniLoaderAll.bin

rkdeveloptool wl 0x0 Armbian-unofficial_24.8.0-trunk_H96-m9_noble_vendor_6.1.75_gnome_desktop.img

==========================

2) Disable hibernate, i catched it on SSH session (pic 1)

 

helped me

 

gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type nothing

 

 

3) HDMI

i use virtual monitor for stable work, without real monitor

 

#in terminal

sudo nano /usr/share/X11/xorg.conf.d/10-quirks.conf

 

add it on end of file and save. Switch off hdmi from h96 and restart.

 

Section "Monitor"
  Identifier "Monitor0"
  HorizSync 28.0-80.0
  VertRefresh 48.0-75.0
  # https://arachnoid.com/modelines/
  # 1920x1080 @ 60.00 Hz (GTF) hsync: 67.08 kHz; pclk: 172.80 MHz
  Modeline "1920x1080_60.00" 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -HSync +Vsync
EndSection
Section "Device"
  Identifier "Card0"
  Driver "dummy"
  VideoRam 256000
EndSection
Section "Screen"
  DefaultDepth 24
  Identifier "Screen0"
  Device "Card0"
  Monitor "Monitor0"
  SubSection "Display"
    Depth 24
    Modes "1920x1080_60.00"
  EndSubSection
EndSection

 

On other PCs, only the virtual display works. In this case, both can work. It doesn't have to be that way, but it's useful in this case.

 

======================================

 

One question.

I soldered sd slot on h96, but cant see disk on terminal, lsblk  shows just mmcblk2.

is it poorly soldered or do I need to do something else?

 

 

[tnt]

02.01.2025 в 15:40, Hqnicolas сказал:

You don't need to save the u-boot env, it's included in your armbian build.
@tnt don't trust any image from factory or other forum users, just build your own images.

I am considering the possibility of implementing the dual boot feature, for example emmc (android), usb/sd armbian.

[Freeze]

 

After apt-get update  and upgrade DTB files was damaged :((

How its recovery, dont know

 

rkdeveloptool dont working

rkdeveloptool reboot-maskrom
Reset Device quit, creating comm object failed!

 

It's log from console interface(COM port)

 

Trying fit image at 0x4000 sector
## Verified-boot: 0
## Checking atf-1 0x40040000 ... sha256(1d13f803de...) + OK
## Checking uboot 0x40200000 ... sha256(ad96202f45...) + OK
## Checking fdt 0x4033dd80 ... sha256(6d0c8a3eca...) + OK
## Checking atf-2 0x400f0000 ... sha256(2f297c059b...) + OK
## Checking atf-3 0x3fe70000 ... sha256(9d9e1b461e...) + OK
## Checking optee 0x48400000 ... sha256(31c3421ab3...) + OK
Jumping to U-Boot(0x40200000) via ARM Trusted Firmware(0x40040000)
Total: 94.153/238.645 ms

INFO:    Preloader serial: 0
NOTICE:  BL31: v2.3():v2.3-749-g30018b771:derrick.huang, fwver: v1.04
NOTICE:  BL31: Built : 09:43:01, Apr 16 2024
INFO:    ext 32k is not detected
INFO:    ARM GICv2 driver initialized
INFO:    dfs DDR fsp_params[0].freq_mhz= 2112MHz
INFO:    dfs DDR fsp_params[1].freq_mhz= 528MHz
INFO:    dfs DDR fsp_params[2].freq_mhz= 1068MHz
INFO:    dfs DDR fsp_params[3].freq_mhz= 1560MHz
INFO:    Using opteed sec cpu_context!
INFO:    boot cpu mask: 1
INFO:    BL31: Initializing runtime services
INFO:    BL31: Initializing BL32
I/TC:
I/TC: OP-TEE version: 3.13.0-791-g185dc3c92 #hisping.lin (gcc version 10.2.1 20201103 (GNU Toolchain for the A-profile Architecture 10.2-2020.11 (arm-10.16))) #2 Tue Apr 16 11:05:25 CST 2024 aarch64, fwver: v1.01
I/TC: OP-TEE memory: TEEOS 0x200000 TA 0xc00000 SHM 0x200000
I/TC: Primary CPU initializing
I/TC: Primary CPU switching to normal world boot
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x40200000
INFO:    SPSR = 0x3c9

U-Boot 2017.09-armbian-2017.09-S57b8-P9d8d-H8c72-V8051-Bda0a-R448a (Sep 13 2024 - 04:56:59 +0000)

Model: Rockchip RK3576 Evaluation board
MPIDR: 0x0
PreSerial: 0, raw, 0x2ad40000
DRAM:  4 GiB
Sysmem: init
Relocation Offset: bda21000
Relocation fdt: fb9f9a70 - fb9fecf0
CR: M/C/I
Using default environment

DM: v2
mmc@2a310000: 1, mmc@2a330000: 0
Bootdev(atags): mmc 0
MMC0: HS400 Enhanced Strobe, 200Mhz
PartType: EFI
No misc partition
boot mode: None
FIT: No boot partition
Failed to load DTB, ret=-19
No valid DTB, ret=-22
Failed to get kernel dtb, ret=-22
Model: Rockchip RK3576 Evaluation board
download key pressed... entering download mode...
RKUSB: LUN 0, dev 0, hwpart 0, sector 0x0, count 0x3a3e000
\usb device is high-speed
\usb device is high-speed

[Hqnicolas]

32 minutes ago, Freeze said:

After apt-get update  and upgrade DTB files was damaged

@Freeze the answer is in your name....
 

sudo apt install armbian-config
sudo armbian-config
select # SYSTEM
select # FREEZE

 

[Hqnicolas]

2 hours ago, tnt said:

I am considering the possibility of implementing the dual boot feature, for example emmc (android), usb/sd armbian.

just solder an SD card reader.
it will works:
https://forum.armbian.com/topic/28895-efforts-to-develop-firmware-for-h96-max-v56-rk3566-8g64g/page/12/#findComment-196381
 

https://forum.armbian.com/topic/24091-efforts-to-develop-firmware-for-h96-max-v56-rk3566-4g32g/#findComment-165929

 

[Freeze]

Ok, but now, how i can recovery damage DTB files? I cant start armbian, just console is working

[Hqnicolas]

22 hours ago, Freeze said:

how i can recovery damage DTB files?

 

I don't know how you guys are burning the armbian images on this model

so, emmc internal memory is not accessible without rkDevTool burning system, you will need to reflash the armbian system.

This brings me an old warning, don't trust a TV box to store your files, always configure a cloud like gdrive, ms onedrive, nextcloud....

 

On 9/8/2024 at 4:17 AM, hzdm said:

Press the reset button. Turn on the power.

 

$rkdeveloptool db RK3576_MiniLoaderAll.bin
$rkdeveloptool wl 0x0 Armbian-unofficial_24.8.0-trunk_H96-m9_noble_vendor_6.1.75_gnome_desktop-test_1.img

 

I don't have this model of TV box, my country has closed it to external products, If you manage to recover, share it with others on the forum.

 

 

Edited January 6 by Hqnicolas

[tnt]

05.01.2025 в 14:52, Hqnicolas сказал:

just solder an SD card reader.

soldering the card reader case was not successful. Perhaps the controller or some other elements need to be unsoldered.

Edited 8 hours ago by tnt
Add photo

[Hqnicolas]

5 hours ago, tnt said:

soldering the card reader case was not successful. Perhaps the controller or some other elements need to be unsoldered.

It seems that this time they excluded the passive components from the board, look at the v56 board SD reader,
you will need to add 2 ceramic capacitors to the board i think.
and also check the Reader body 4 large GND pads if it's sodered.
no device is needed to use the SD reader you must have a TTL connected to the board to debug,
clear the EMMC with this method:

using the T95 Method

On android ROM

flash the Wipe_part on Boot partition
flash the Wipe_part on Recovery partition

Connect the power cord...

wait 1 second

and in a fraction of second, connect the sd-Card on device.....
if it doesn't boot, try again in a different timming 2 seconds after power.

Based on this example

 

Quote

 

Edited 2 hours ago by Hqnicolas