salas

@C127I just saw that @whywontitworkmessage and decided to try your image(0.3) directly in the sdcard ( emmc removed ) and that image does not boot. The UART is also stuck in starting kernel as mentioned by @whywontitwork, but I can get the HDMI output and the boot process drops to a initramfs shell because it can not find the root device. This is the console log. DDR 9fa84341ce typ 24/09/06-09:51:11,fwver: v1.18 ch0 ttot6 ch1 ttot6 ch2 ttot6 ch3 ttot6 ch0 ttot7 LPDDR5, 2400MHz channel[0] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB ch1 ttot7 channel[1] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB ch2 ttot7 channel[2] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB ch3 ttot7 channel[3] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB Manufacturer ID:0xff DQS rds:h1,l0 CH0 RX Vref:24.6%, TX Vref:22.0%,22.0% DQ rds:h5 h2 h1 h2 h1 h4 l0 h7, h1 h1 h3 h3 h1 h1 h7 l0 DQS rds:l0,h2 CH1 RX Vref:27.9%, TX Vref:21.0%,21.0% DQ rds:h4 l0 h2 h3 h6 l0 h7 l0, h7 h4 h4 h4 l1 h1 h6 h7 DQS rds:l0,h2 CH2 RX Vref:25.0%, TX Vref:21.0%,21.0% DQ rds:h1 l0 h2 l2 h1 h1 h5 h1, l1 h6 l1 h3 l2 h1 h1 h2 DQS rds:l0,h1 CH3 RX Vref:27.9%, TX Vref:20.0%,20.0% DQ rds:h3 h1 h2 h1 h4 h1 h1 h1, h4 h7 h2 h2 h3 h5 l0 h5 stride=0x2, ddr_config=0x6 hash ch_mask0-1 0x20 0x40, bank_mask0-3 0x0 0x2400 0x44800 0x89000, rank_mask0 0x2000 change to F1: 534MHz ch0 ttot6 ch1 ttot6 ch2 ttot6 ch3 ttot6 change to F2: 1320MHz ch0 ttot8 ch1 ttot8 ch2 ttot8 ch3 ttot8 change to F3: 1968MHz ch0 ttot6 ch1 ttot6 ch2 ttot6 ch3 ttot6 change to F0: 2400MHz ch0 ttot7 ch1 ttot7 ch2 ttot7 ch3 ttot7 out U-Boot SPL 2024.04-armbian-2024.04-S2504-Pa35d-H29de-Vbf83-Bb703-R448a (Jul 02 2025 - 19:31:47 +0000) Trying to boot from MMC1 ## Checking hash(es) for config config-1 ... OK ## Checking hash(es) for Image atf-1 ... sha256+ OK ## Checking hash(es) for Image u-boot ... sha256+ OK ## Checking hash(es) for Image fdt-1 ... sha256+ OK ## Checking hash(es) for Image atf-2 ... sha256+ OK ## Checking hash(es) for Image atf-3 ... sha256+ OK INFO: Preloader serial: 2 NOTICE: BL31: v2.3():v2.3-868-g040d2de11:derrick.huang, fwver: v1.48 NOTICE: BL31: Built : 15:02:44, Dec 19 2024 INFO: spec: 0x13 INFO: code: 0x88 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: bypass memory repair INFO: idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001 INFO: dfs DDR fsp_params[0].freq_mhz= 2400MHz INFO: dfs DDR fsp_params[1].freq_mhz= 534MHz INFO: dfs DDR fsp_params[2].freq_mhz= 1320MHz INFO: dfs DDR fsp_params[3].freq_mhz= 1968MHz 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 = 0xa00000 INFO: SPSR = 0x3c9 ns16550_serial serial@feb50000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 U-Boot 2024.04-armbian-2024.04-S2504-Pa35d-H29de-Vbf83-Bb703-R448a (Jul 02 2025 - 19:31:47 +0000) Model: Xunlong Orange Pi 5 Pro DRAM: 16 GiB (effective 15.7 GiB) Core: 323 devices, 30 uclasses, devicetree: separate MMC: mmc@fe2c0000: 0 Loading Environment from nowhere... OK In: serial@feb50000 Out: serial@feb50000 Err: serial@feb50000 Model: Xunlong Orange Pi 5 Pro rockchip_dnl_key_pressed: no saradc device found Net: eth0: ethernet@fe1c0000 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': 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@fe2c0000.bootdev': 1 script ready mmc 1 mmc@fe2c0000.bootdev.part /boot/boot.scr ** Booting bootflow 'mmc@fe2c0000.bootdev.part_1' with script Boot script loaded from mmc 0:1 200 bytes read in 4 ms (48.8 KiB/s) 15754859 bytes read in 1321 ms (11.4 MiB/s) 39287296 bytes read in 3289 ms (11.4 MiB/s) 162018 bytes read in 28 ms (5.5 MiB/s) Working FDT set to 12000000 Trying kaslrseed command... Info: Unknown command can be safely ignored since kaslrseed does not apply to all boards. Unknown command 'kaslrseed' - try 'help' ## Loading init Ramdisk from Legacy Image at 12180000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 15754795 Bytes = 15 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 12000000 Booting using the fdt blob at 0x12000000 Working FDT set to 12000000 Loading Ramdisk to ebf92000, end ece9862b ... OK Loading Device Tree to 00000000ebf02000, end 00000000ebf91fff ... OK Working FDT set to ebf02000 Starting kernel ... Setting loglevel=8 and verbose=8 shows this is console: [ 2.028301] dwmmc_rockchip fe2d0000.mmc: IDMAC supports 32-bit address mode. [ 2.029020] dwmmc_rockchip fe2d0000.mmc: Using internal DMA controller. [ 2.029624] dwmmc_rockchip fe2d0000.mmc: Version ID is 270a [ 2.030163] dwmmc_rockchip fe2d0000.mmc: DW MMC controller at irq 84,32 bit host data width,256 deep fifo [ 2.031384] dwmmc_rockchip fe2d0000.mmc: allocated mmc-pwrseq [ 2.031921] mmc_host mmc2: card is non-removable. [ 2.217056] dwmmc_rockchip fe2c0000.mmc: Busy; trying anyway [ 2.250531] mmc_host mmc2: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) [ 2.376463] mmc_host mmc2: Bus speed (slot 0) = 150000000Hz (slot req 150000000Hz, actual 150000000HZ div = 0) [ 2.409028] dwmmc_rockchip fe2d0000.mmc: Successfully tuned phase to 223 [ 2.423188] mmc2: new UHS-I speed SDR104 SDIO card at address 0001 [ 2.953845] mmc_host mmc0: Timeout sending command (cmd 0x202000 arg 0x0 status 0x80202000) [ 2.991412] mmc0: error -110 whilst initialising SD card [ 3.527479] dwmmc_rockchip fe2c0000.mmc: Busy; trying anyway [ 4.257059] mmc_host mmc0: Timeout sending command (cmd 0x202000 arg 0x0 status 0x80202000) [ 4.271710] mmc_host mmc0: Bus speed (slot 0) = 300000Hz (slot req 300000Hz, actual 300000HZ div = 0) [ 4.831481] dwmmc_rockchip fe2c0000.mmc: Busy; trying anyway [ 5.560980] mmc_host mmc0: Timeout sending command (cmd 0x202000 arg 0x0 status 0x80202000) [ 5.575632] mmc_host mmc0: Bus speed (slot 0) = 200000Hz (slot req 200000Hz, actual 200000HZ div = 0) [ 6.140278] dwmmc_rockchip fe2c0000.mmc: Busy; trying anyway [ 6.869893] mmc_host mmc0: Timeout sending command (cmd 0x202000 arg 0x0 status 0x80202000)

@C127I forgot to ask. Is USB3 port working for you in your kernel ?

Sure. I am here to test it when you send. Next week I will be off for about 7 days, but we can test until that after that.

Actually the 0.4 was trying to boot from MMC1 and the 0.5 from MMC2. is this expected ?

@C127 Tested, same problem DDR 9fa84341ce typ 24/09/06-09:51:11,fwver: v1.18 ch0 ttot6 ch1 ttot6 ch2 ttot6 ch3 ttot6 ch0 ttot7 LPDDR5, 2400MHz channel[0] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB ch1 ttot7 channel[1] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB ch2 ttot7 channel[2] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB ch3 ttot7 channel[3] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB Manufacturer ID:0xff DQS rds:h1,l0 CH0 RX Vref:24.6%, TX Vref:23.0%,22.0% DQ rds:h5 h2 h1 h2 h1 h5 l0 h7, h1 h1 h3 h3 h1 h1 h7 l0 DQS rds:l0,h2 CH1 RX Vref:27.9%, TX Vref:21.0%,21.0% DQ rds:h5 l0 h2 h2 h6 l0 h7 l0, h7 h5 h4 h4 l1 h1 h6 h7 DQS rds:l0,h2 CH2 RX Vref:25.4%, TX Vref:22.0%,21.0% DQ rds:h1 l0 h2 l2 h1 h1 h5 h1, l1 h7 l2 h4 l2 h1 h1 h3 DQS rds:l0,h1 CH3 RX Vref:27.9%, TX Vref:21.0%,21.0% DQ rds:h3 h1 h1 h1 h4 h1 h1 h1, h5 h6 h2 h2 h3 h5 l0 h5 stride=0x2, ddr_config=0x6 hash ch_mask0-1 0x20 0x40, bank_mask0-3 0x0 0x2400 0x44800 0x89000, rank_mask0 0x2000 change to F1: 534MHz ch0 ttot6 ch1 ttot6 ch2 ttot6 ch3 ttot6 change to F2: 1320MHz ch0 ttot8 ch1 ttot8 ch2 ttot8 ch3 ttot8 change to F3: 1968MHz ch0 ttot6 ch1 ttot6 ch2 ttot6 ch3 ttot6 change to F0: 2400MHz ch0 ttot7 ch1 ttot7 ch2 ttot7 ch3 ttot7 out U-Boot SPL 2024.04-armbian-2024.04-S2504-Pdd14-H29de-Vbf83-Bb703-R448a (Jul 11 2025 - 23:38:46 +0000) Trying to boot from MMC2 Card did not respond to voltage select! : -110 spl: mmc init failed with error: -95 SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ###

Post not related to 0.4! Since yesterday I've been doing a few tests on your kernel patch against mainline kernel 6.16-rc5. here what I found out. I am testing against Johsua's ubuntu because this is my goal ( newer kernel on that image ) 1) Kernel compile and works , but I get a few warnings on the dtbs compilation DTC arch/arm64/boot/dts/rockchip/rk3588s-orangepi-5-pro.dtb arch/arm64/boot/dts/rockchip/rk3588s-orangepi-5-pro.dts:235.3-13: Warning (reg_format): /mmc@fe2d0000/wifi@1:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1) arch/arm64/boot/dts/rockchip/rk3588s-orangepi-5-pro.dtb: Warning (pci_device_reg): Failed prerequisite 'reg_format' arch/arm64/boot/dts/rockchip/rk3588s-orangepi-5-pro.dtb: Warning (pci_device_bus_num): Failed prerequisite 'reg_format' arch/arm64/boot/dts/rockchip/rk3588s-orangepi-5-pro.dtb: Warning (i2c_bus_reg): Failed prerequisite 'reg_format' arch/arm64/boot/dts/rockchip/rk3588s-orangepi-5-pro.dtb: Warning (spi_bus_reg): Failed prerequisite 'reg_format' arch/arm64/boot/dts/rockchip/rk3588s-orangepi-5-pro.dts:233.17-241.4: Warning (avoid_default_addr_size): /mmc@fe2d0000/wifi@1: Relying on default #address-cells value arch/arm64/boot/dts/rockchip/rk3588s-orangepi-5-pro.dts:233.17-241.4: Warning (avoid_default_addr_size): /mmc@fe2d0000/wifi@1: Relying on default #size-cells value 2) Your patch works and makes the system bootable from the SDCARD. U-boot reads the /boot from the sdcard, since it can not find the EMMC, but after booting I can have to / on the EMMC and that works. 3) Curiously after the uboot handoff to the linux kernel, emmc is available but the sdcard fails to initialize emmc initialize just fine with the / [ 10.225763] mmc2: new HS400 Enhanced strobe MMC card at address 0001 [ 10.228424] mmcblk2: mmc2:0001 A3A564 233 GiB [ 10.233239] mmcblk2: p1 p2 [ 10.234373] mmcblk2boot0: mmc2:0001 A3A564 4.00 MiB [ 10.237884] mmcblk2boot1: mmc2:0001 A3A564 4.00 MiB So I basically have a working system but it requires the sdcard to boot and I can not mount the sdcard after boot root@pi5pro1:~# uname -r 6.16.0-rc5 root@pi5pro1:~# cat /etc/os-release PRETTY_NAME="Ubuntu 24.04.1 LTS" NAME="Ubuntu" VERSION_ID="24.04" VERSION="24.04.1 LTS (Noble Numbat)" VERSION_CODENAME=noble ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" UBUNTU_CODENAME=noble LOGO=ubuntu-logo

@C127 0.4 output. Still no boot DDR 9fa84341ce typ 24/09/06-09:51:11,fwver: v1.18 ch0 ttot6 ch1 ttot6 ch2 ttot6 ch3 ttot6 ch0 ttot7 LPDDR5, 2400MHz channel[0] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB ch1 ttot7 channel[1] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB ch2 ttot7 channel[2] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB ch3 ttot7 channel[3] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB Manufacturer ID:0xff DQS rds:h1,l0 CH0 RX Vref:24.6%, TX Vref:21.0%,21.0% DQ rds:h4 h2 h1 h2 h1 h5 l0 h7, h1 h1 h3 h3 h1 h1 h7 l0 DQS rds:l0,h2 CH1 RX Vref:27.9%, TX Vref:21.0%,21.0% DQ rds:h4 l0 h2 h3 h7 l0 h7 l0, h6 h5 h4 h5 l1 h1 h6 h6 DQS rds:l0,h2 CH2 RX Vref:25.0%, TX Vref:21.0%,21.0% DQ rds:h1 l0 h2 l3 h1 h2 h5 h1, l1 h7 l1 h4 l2 h1 h1 h3 DQS rds:l0,h1 CH3 RX Vref:27.5%, TX Vref:21.0%,21.0% DQ rds:h3 h1 h2 h1 h4 h1 h1 h1, h5 h6 h2 h2 h4 h4 l0 h5 stride=0x2, ddr_config=0x6 hash ch_mask0-1 0x20 0x40, bank_mask0-3 0x0 0x2400 0x44800 0x89000, rank_mask0 0x2000 change to F1: 534MHz ch0 ttot6 ch1 ttot6 ch2 ttot6 ch3 ttot6 change to F2: 1320MHz ch0 ttot8 ch1 ttot8 ch2 ttot8 ch3 ttot8 change to F3: 1968MHz ch0 ttot6 ch1 ttot6 ch2 ttot6 ch3 ttot6 change to F0: 2400MHz ch0 ttot7 ch1 ttot7 ch2 ttot7 ch3 ttot7 out U-Boot SPL 2024.04-armbian-2024.04-S2504-P83ae-H29de-Vbf83-Bb703-R448a (Jul 03 2025 - 17:49:57 +0000) Trying to boot from MMC1 Card did not respond to voltage select! : -110 spl: mmc init failed with error: -95 SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ###

I will flash the new image now and let you know what happens,

I will gladly help you to test it. Just to let you know, on 0.3 apparently If i boot from the sdcard, after booting the emmc is available. So the kernel knows about it. just uboot does not ?

@C127Boot from the sdcard boots, although with some minor things: 1) First boot spent 1 minute in "Starting kernel message" 2) ssh does not generate the host ssh keys on first boot. So no way to login using ssh until someone manually run ssh-keygen -A. I think this is more a armbian bug maybe. 3) I am gonna test a few extra things. The image looks great, although missing the emmc card boot

@C127I tried to boot your image on orangepi5pro emmc card. It wont boot. DDR 9fa84341ce typ 24/09/06-09:51:11,fwver: v1.18 ch0 ttot6 ch1 ttot6 ch2 ttot6 ch3 ttot6 ch0 ttot7 LPDDR5, 2400MHz channel[0] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB ch1 ttot7 channel[1] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB ch2 ttot7 channel[2] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB ch3 ttot7 channel[3] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB Manufacturer ID:0xff DQS rds:l0,l0 CH0 RX Vref:26.7%, TX Vref:21.0%,21.0% DQ rds:h3 h3 h2 h1 h4 h2 h2 h1, h1 h2 h3 h4 h1 h2 h2 h2 DQS rds:l0,h1 CH1 RX Vref:27.9%, TX Vref:20.0%,20.0% DQ rds:l0 h2 h2 h3 h5 h3 h3 h6, h4 h2 h2 h2 h2 h1 h4 l0 DQS rds:l0,l0 CH2 RX Vref:26.7%, TX Vref:20.0%,20.0% DQ rds:h3 l0 l0 l0 h4 h1 h7 h3, h1 l0 h1 l0 h2 h4 h1 h2 DQS rds:l0,h1 CH3 RX Vref:27.9%, TX Vref:22.0%,21.0% DQ rds:h4 h4 h7 h4 h2 h2 h4 h3, h3 h3 h6 h2 h3 h1 h3 h1 stride=0x2, ddr_config=0x6 hash ch_mask0-1 0x20 0x40, bank_mask0-3 0x0 0x2400 0x44800 0x89000, rank_mask0 0x2000 change to F1: 534MHz ch0 ttot6 ch1 ttot6 ch2 ttot6 ch3 ttot6 change to F2: 1320MHz ch0 ttot8 ch1 ttot8 ch2 ttot8 ch3 ttot8 change to F3: 1968MHz ch0 ttot6 ch1 ttot6 ch2 ttot6 ch3 ttot6 change to F0: 2400MHz ch0 ttot7 ch1 ttot7 ch2 ttot7 ch3 ttot7 out U-Boot SPL 2024.04-armbian-2024.04-S2504-P83ae-H29de-Vbf83-Bb703-R448a (Jul 03 2025 - 17:49:57 +0000) Trying to boot from MMC1 Card did not respond to voltage select! : -110 spl: mmc init failed with error: -95 SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ###

@C127 any chance to make a release that already has the ethernet driver compiled and working ?

I will only be able to test it after july 10th when i return back home but I will get back here as soon as I test it.

Hi @C127 Thanks for working on this board! I have a few questions though. Where can I get that driver from ? I did not really get this. My board has one single NVME slot for M.2 M cards. Isn't USB-C in this board only for power supply ? I use eMMC cards. I am gonna check if I can boot using your kernel and uboot. I just want to confirm you really mean orangepi 5 PRO variant. I wonder If i could use your kernel patch directly against the mainline 6.15 or 6.16 kernel. When your job gets more mature it would be nice to try to port upstream.

The orangepi-5-pro variant has no spi-flash afaik. I dont have a sdcard, I boot directly from emmc. I still have to get a better understanding on how this SBC boots. I have a few questions and maybe you can help me to understand. 1) If there is no spi-flash and emmc by default where is the default uboot stored ? Is there any default uboot? Somehow the board has to know where to try to boot from. 2) I can boot using emmc flashed with joshua's image. Am i correct to assume that someplace in the SBC there is a code to look for uboot in sdcard, then emmc, then nvme ? 3) EDK2-UEFI does not support orangepi-5-pro 4) Why the version of uboot matters? I always thought that uboot was there just to hand off the boot to the linux kernel and that was done. ( like grub does )