My development board is Orange Pi 5 Plus. I attempted to use the official system images: Opios-arch-aarch64-gnome-opi5plus-24.04-linux5.10.160 and Orangepi5plus_1.0.8_debian_bullseye_desktop_xfce_linux5.10.160. On both of these operating systems, I cloned the source tree from the orange-pi-5.10-rk35xx branch, then attempted to compile and install using the following commands:
make rockchip_linux_defconfig
make -j10
sudo make modules_install
sudo make install
sudo make dtbs_install INSTALL_DTBS_PATH=/boot/dtb/
sudo reboot
However, after rebooting, the screen failed to light up. The red LED on the development board remains on constantly, but the blue and green LEDs do not blink. I used a serial tool to check the uboot log and found that it hangs while loading the kernel, as shown in the log below.
DDR V1.13 <censored> cym 23/08/11-09:31:58
LPDDR4X, 2112MHz
channel[0] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=8 Size=4096MB
channel[1] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=8 Size=4096MB
channel[2] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=8 Size=4096MB
channel[3] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=8 Size=4096MB
Manufacturer ID:0x1
CH0 RX Vref:30.1%, TX Vref:21.8%,21.8%
CH1 RX Vref:28.9%, TX Vref:22.8%,21.8%
CH2 RX Vref:30.5%, TX Vref:21.8%,21.8%
CH3 RX Vref:28.9%, TX Vref:22.8%,22.8%
change to F1: 528MHz
change to F2: 1068MHz
change to F3: 1560MHz
change to F0: 2112MHz
out
U-Boot SPL board init
U-Boot SPL 2017.09-orangepi (Nov 10 2023 - 17:01:26)
Trying to boot from MMC1
spl: mmc init failed with error: -123
Trying to boot from MMC2
Trying fit image at 0x4000 sector
## Verified-boot: 0
## Checking atf-1 0x00040000 ... sha256(c902200be1...) + OK
## Checking uboot 0x00200000 ... sha256(cc96e7a49e...) + OK
## Checking fdt 0x00311da8 ... sha256(d2dda3ef7c...) + OK
## Checking atf-2 0xff100000 ... sha256(225d6bf071...) + OK
## Checking atf-3 0x000f0000 ... sha256(aa71013e72...) + OK
Jumping to U-Boot(0x00200000) via ARM Trusted Firmware(0x00040000)
Total: 510.44 ms
INFO: Preloader serial: 2
NOTICE: BL31: v2.3():v2.3-639-g87bcc5dfe:derrick.huang
NOTICE: BL31: Built : 18:06:16, Sep 9 2023
INFO: spec: 0x1
INFO: ext 32k is valid
INFO: ddr: stride-en 4CH
INFO: GICv3 without legacy support detected.
INFO: ARM GICv3 driver initialized in EL3
INFO: valid_cpu_msk=0xff bcore0_rst = 0x0, bcore1_rst = 0x0
INFO: l3 cache partition cfg-0
INFO: system boots from cpu-hwid-0
INFO: idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001
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: BL31: Initialising Exception Handling Framework
INFO: BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR: Error initializing runtime service opteed_fast
INFO: BL31: Preparing for EL3 exit to normal world
INFO: Entry point address = 0x200000
INFO: SPSR = 0x3c9
U-Boot 2017.09-orangepi (Nov 10 2023 - 17:01:26 +0800)
Model: RK3588 Orange Pi 5 Plus
PreSerial: 2, raw, 0xfeb50000
DRAM: 16 GiB
Sysmem: init
Relocation Offset: eda65000
Relocation fdt: eb9f9a78 - eb9fecd0
CR: M/C/I
Using default environment
no mmc device at slot 1
mmc@fe2c0000: 0, mmc@fe2e0000: 1 (eMMC)
Bootdev(atags): mmc 1
MMC1: HS200, 200Mhz
PartType: EFI
DM: v2
boot mode: None
Model: RK3588 Orange Pi 5 Plus
CLK: (sync kernel. arm: enter 1008000 KHz, init 1008000 KHz, kernel 0N/A)
b0pll 24000 KHz
b1pll 24000 KHz
lpll 24000 KHz
v0pll 24000 KHz
aupll 24000 KHz
cpll 1500000 KHz
gpll 1188000 KHz
npll 24000 KHz
ppll 1100000 KHz
aclk_center_root 702000 KHz
pclk_center_root 100000 KHz
hclk_center_root 396000 KHz
aclk_center_low_root 500000 KHz
aclk_top_root 750000 KHz
pclk_top_root 100000 KHz
aclk_low_top_root 396000 KHz
Net: No ethernet found.
Hit key to stop autoboot('CTRL+C'): 0
mmc@fe2c0000: 0
mmc@fe2e0000: 1 (eMMC)
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
Found U-Boot script /boot.scr
reading /boot.scr
3411 bytes read in 9 ms (370.1 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1
reading /orangepiEnv.txt
226 bytes read in 1 ms (220.7 KiB/s)
reading /uInitrd
14376199 bytes read in 79 ms (173.5 MiB/s)
reading /Image
35301888 bytes read in 193 ms (174.4 MiB/s)
reading /dtb/rockchip/rk3588-orangepi-5-plus.dtb
279329 bytes read in 3 ms (88.8 MiB/s)
reading /dtb/rockchip/overlay/rk3588-fixup.scr
2756 bytes read in 1 ms (2.6 MiB/s)
Applying kernel provided DT fixup script (rk3588-fixup.scr)
## Executing script at 09000000
Fdt Ramdisk skip relocation
## Loading init Ramdisk from Legacy Image at 0a200000 ...
Image Name: uInitrd
Image Type: AArch64 Linux RAMDisk Image (gzip compressed)
Data Size: 14376135 Bytes = 13.7 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 0x0a100000
Booting using the fdt blob at 0x0a100000
reserving fdt memory region: addr=a100000 size=aa000
'reserved-memory' cma: addr=10000000 size=10000000
'reserved-memory' ramoops@110000: addr=110000 size=f0000
Using Device Tree in place at 000000000a100000, end 000000000a1acfff
Adding bank: 0x00200000 - 0xf0000000 (size: 0xefe00000)
Adding bank: 0x100000000 - 0x3fc000000 (size: 0x2fc000000)
Adding bank: 0x3fc500000 - 0x3fff00000 (size: 0x03a00000)
Adding bank: 0x4f0000000 - 0x500000000 (size: 0x10000000)
Total: 605.735 ms
Starting kernel ...
I would appreciate a prompt resolution to this issue.
My development board is Orange Pi 5 Plus. I attempted to use the official system images:
Opios-arch-aarch64-gnome-opi5plus-24.04-linux5.10.160
andOrangepi5plus_1.0.8_debian_bullseye_desktop_xfce_linux5.10.160
. On both of these operating systems, I cloned the source tree from the orange-pi-5.10-rk35xx branch, then attempted to compile and install using the following commands:However, after rebooting, the screen failed to light up. The red LED on the development board remains on constantly, but the blue and green LEDs do not blink. I used a serial tool to check the uboot log and found that it hangs while loading the kernel, as shown in the log below.
I would appreciate a prompt resolution to this issue.