Efforts to develop firmware for H96 MAX V56 RK3566 8G/64G

[maka]

What a rare thing I am. Maybe a trasgo, I don't know. Got chromium from apt and worked like a charm.

Edited November 18 by maka

[DreamDreams]

I installed u-boot to eMMC, but found that there is no saveenv command, does anybody know why? 

 

Tried to compile u-boot myself but when I run make command in u-boot source I got following error: 

Image 'simple-bin' is missing external blobs and is non-functional: rockchip-tpl atf-bl31

/binman/simple-bin/mkimage/rockchip-tpl (rockchip-tpl):
   An external TPL is required to initialize DRAM. Get the external TPL
   binary and build with ROCKCHIP_TPL=/path/to/ddr.bin. One possible source
   for the external TPL binary is https://github.com/rockchip-linux/rkbin.

/binman/simple-bin/fit/images/@atf-SEQ/atf-bl31 (atf-bl31):
   See the documentation for your board. You may need to build ARM Trusted
   Firmware and build with BL31=/path/to/bl31.bin

Image 'simple-bin' is missing optional external blobs but is still functional: tee-os

/binman/simple-bin/fit/images/@tee-SEQ/tee-os (tee-os):
   See the documentation for your board. You may need to build Open Portable
   Trusted Execution Environment (OP-TEE) and build with TEE=/path/to/tee.bin

Image 'simple-bin-spi' is missing external blobs and is non-functional: rockchip-tpl

/binman/simple-bin-spi/mkimage/rockchip-tpl (rockchip-tpl):
   An external TPL is required to initialize DRAM. Get the external TPL
   binary and build with ROCKCHIP_TPL=/path/to/ddr.bin. One possible source
   for the external TPL binary is https://github.com/rockchip-linux/rkbin.

Some images are invalid
make: *** [Makefile:1126: .binman_stamp] Error 103

 

I got following binary files in the folder:

u-boot-dtb.bin  u-boot-nodtb.bin  u-boot-rockchip-spi.bin  u-boot-rockchip.bin  u-boot.bin

But none of them starts with bytes "RKNS" as in /usr/lib/linux-u-boot-edge-h96-tvbox-3566/u-boot-rockchip.bin . So I suspect that they are not the one I should burn to eMMC. 

[maka]

Where did you read the u-boot building?

 

export BL31=../trusted-firmware-a/build/rk3568/release/bl31/bl31.elf [or]export BL31=../rkbin/bin/rk35/rk3568_bl31_v1.34.elf

export ROCKCHIP_TPL=../rkbin/bin/rk35/rk3568_ddr_1560MHz_v1.13.bin

make evb-rk3568_defconfig

make CROSS_COMPILE=aarch64-linux-gnu-

 

You have not done first and second step. This is an example for another board, an sbc better than your box, and the files you have to use is unknown. Don't use this ones or maybe you get a brick. You have been warned.

Edited November 19 by maka

[DreamDreams]

46 minutes ago, maka said:

Where did you read the u-boot building?

 

export BL31=../trusted-firmware-a/build/rk3568/release/bl31/bl31.elf [or]export BL31=../rkbin/bin/rk35/rk3568_bl31_v1.34.elf

export ROCKCHIP_TPL=../rkbin/bin/rk35/rk3568_ddr_1560MHz_v1.13.bin

make evb-rk3568_defconfig make

CROSS_COMPILE=aarch64-linux-gnu-

 

You have not done first and second step. This is an example for another board, an sbc better than your box, and the files you have to use is unknown. Don't use this ones or maybe you get a brick. You have been warned.

You are right, I didn't do the first two steps. I got the base config from running "./compile.sh BOARD=h96-tvbox-3566 BRANCH=edge uboot-config". Then 'make menuconfig' and make. 

It's hard to find documentation for compile u-boot only. 

 

Will try your steps. But where do I find file rk3568_bl31_v1.34.elf and rk3568_ddr_1560MHz_v1.13.bin? I could find it in the source folder. 

Edited November 19 by DreamDreams

[DreamDreams]

I found the binary files. On my system they have different version. 

 

I successfully compiled and burn new u-boot to my board. But saveenv is still missing. 

 

# grep SAVEENV .config
CONFIG_CMD_SAVEENV=y
CONFIG_SAVEENV=y

 

U-Boot 2024.07-armbian-2024.07-S3f77-P0000-H3f52-Vc494-Bda0a-R448a (Nov 19 2024 - 15:22:24 +0800)

Model: Generic RK3566/RK3568
DRAM:  8 GiB (effective 7.7 GiB)
Core:  251 devices, 25 uclasses, devicetree: separate
MMC:   mmc@fe2b0000: 1, mmc@fe310000: 0
Loading Environment from nowhere... OK
In:    serial@fe660000
Out:   serial@fe660000
Err:   serial@fe660000
Model: Generic RK3566/RK3568
Net:   No ethernet found.
Hit any key to stop autoboot:  0 
Scanning for bootflows in all bootdevs
Seq  Method       State   Uclass    Part  Name                      Filename
---  -----------  ------  --------  ----  ------------------------  ----------------
Scanning global bootmeth 'efi_mgr':
Card did not respond to voltage select! : -110
No EFI system partition
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
  0  efi_mgr      ready   (none)       0  <NULL>                    
** Booting bootflow '<NULL>' with efi_mgr
Loading Boot0000 'mmc 0' failed
EFI boot manager: Cannot load any image
Boot failed (err=-14)
Scanning bootdev 'mmc@fe2b0000.bootdev':
Card did not respond to voltage select! : -110
Scanning bootdev 'mmc@fe310000.bootdev':
Unknown uclass 'nvme' in label
Unknown uclass 'scsi' in label
No USB controllers found
No ethernet found.
No ethernet found.
No more bootdevs
---  -----------  ------  --------  ----  ------------------------  ----------------
(1 bootflow, 1 valid)
=> 
=> 
=> 
=> 
=> <INTERRUPT>
=> 
=> saveenv
Unknown command 'saveenv' - try 'help'

 

[DreamDreams]

Got it working, the cause is that config CONFIG_ENV_IS_IN_MMC is not set. After setting this, saveenv appears. 

[DreamDreams]

Another question, how can I determine whter my memory is capable of 1560MHz or 1056MHz? 

 

Below is u-boot output when reset. 

=> reset
resetting ...
DDR 2d653b3476 typ 24/01/20-15:04:19,fwver: v1.21
ln
LP4/4x derate en, other dram:1x trefi
SRX
ddrconfig:7
LPDDR4X, 324MHz
BW=32 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=8 Size=8192MB
tdqss: cs0 dqs0: 72ps, dqs1: -72ps, dqs2: -48ps, dqs3: -144ps, 
tdqss: cs1 dqs0: 72ps, dqs1: -72ps, dqs2: -24ps, dqs3: -144ps,

 

[DreamDreams]

Now I'm very disapointed with this box. Comparing to my Firefly-rk3399, it has 2x memory, newer CPU/GPU, but performance is worse. 

 

glmark2-es2-wayland score: RK3399 1100, RK3566 500

ffmpeg -hwaccel drm -benchmark on same AVC/H264 video, RK3399 40X, RK3566 10X

 

And GUI smothiness is much worse than RK3399. I can feel the difference, and it is very obvious. 

Kernel version are both 6.12 mainline. 

[maka]

Nothing rare in your review. You are comparing a high price rk3399 with a low one rk3566. The last makes a good job because is well supported and can move a Desktop for little money. With LXQT works wonderfull.

[DreamDreams]

20 minutes ago, maka said:

Nothing rare in your review. You are comparing a high price rk3399 with a low one rk3566. The last makes a good job because is well supported and can move a Desktop for little money. With LXQT works wonderfull.

Is RK3399 more expansive? I was missled by my purchase price. And on paper, RK3399's Mali T860 is much weaker than RK3566's Mali G52. 

[DreamDreams]

I'd like to try Joshua Riek's image, but not sure how. @Hqnicolas, your link in previous post is 404 now. 

 

I tried to boot kernel linux-image-vendor-rk35xx with rk3566-h96-tvbox.dtb but got instant kernel panic. 

[maka]

Joshua ryek had to halt his project because of problems. I hope he is getting better know. His interest in rk3566 is   almost zero. Only help could change this.

 

RK3399's gpu Mali T860 MP4 is much more powerful than rk3566's Mali G52 2EE (MP1).

Edited November 21 by maka

[Hqnicolas]

On 11/21/2024 at 2:53 AM, DreamDreams said:

'd like to try Joshua Riek's image, but not sure how. @Hqnicolas, your link in previous post is 404 now. 

 

@DreamDreams

I remove it because the joshua project changed, and my patches become deprecated.....

you need to edit the patch file for orangepi3b to work with h96 max simple change the config for this: https://github.com/hqnicolas/ArmBoardBringUp

 

 

Clone the Joshua riek project on github.

 

remove patches from the .sh file that dont be compatible with h96max:
https://github.com/Joshua-Riek/ubuntu-rockchip/blob/main/config/boards/orangepi-3b.sh

 

take the dts file from armbian rk3566 h96 max and edit this patch below: 
https://github.com/Joshua-Riek/ubuntu-rockchip/blob/main/packages/u-boot-turing-rk3588/debian/patches/0005-board-rockchip-Add-Xunlong-Orange-Pi-3B.patch

 

now when you compile for Orange pi 3B it will compile for H96 max....

 

 

the trick for this 0005-board-rockchip-Add-Xunlong-Orange-Pi-3B.patch is that you need to count the number of lines that you are insert in the path and edit the line.
 

 

Quote

 arch/arm/dts/Makefile                       |   1 +
 arch/arm/dts/rk3566-orangepi-3b-u-boot.dtsi |  24 +
 arch/arm/dts/rk3566-orangepi-3b.dts         | 869 ++++++++++++++++++++
 configs/orangepi-3b-rk3566_defconfig        | 114 +++
 doc/board/rockchip/rockchip.rst             |   1 +
 5 files changed, 1009 insertions(+)

 

 

Quote

diff --git a/configs/orangepi-3b-rk3566_defconfig b/configs/orangepi-3b-rk3566_defconfig
new file mode 100644
index 00000000000..5557d983f31
--- /dev/null
+++ b/configs/orangepi-3b-rk3566_defconfig
@@ -0,0 +1,114 @@

 

you will need to enable / disable things on defconfig, use armbian defconfig as an exaple, (dont copy it) just compare and set it up

 

@DreamDreams after doing it you can feel like a real linux hacker because you will be.
 

Edited Saturday at 09:28 PM by Hqnicolas

[DreamDreams]

On 11/24/2024 at 5:08 AM, Hqnicolas said:

remove patches from the .sh file that dont be compatible with h96max:
https://github.com/Joshua-Riek/ubuntu-rockchip/blob/main/config/boards/orangepi-3b.sh

This shell script doesn't have any patch in it.

 

On 11/24/2024 at 5:08 AM, Hqnicolas said:

take the dts file from armbian rk3566 h96 max and edit this patch below: 
https://github.com/Joshua-Riek/ubuntu-rockchip/blob/main/packages/u-boot-turing-rk3588/debian/patches/0005-board-rockchip-Add-Xunlong-Orange-Pi-3B.patch

Do you mean this dts patch file?

@Hqnicolas

Edited 14 hours ago by DreamDreams

[DreamDreams]

Another question, do we have to use Joshua Riek's u-boot? Should u-boot from Aribian just work? 

 

And the steps you mentioned above only affects u-boot right? What about kernel config and dts/dtb?