[Orange Pi One Plus] Not Booting LE 11.0 Nightly

MaartenJD · July 21, 2023 at 9:47 PM

When I (try to) boot LE11 (stable and latest nightly build), I get the following error on my screen:

*** Error in mount_flash: mount_common: Could not mount UUID=1507-1311 ***

### Starting debugging shell for boot step: mount_flash... type exit to quit ##

LE10 and LE12 booting normally from the same SD-cards.

Problem reproduces with LE11 on other/different SD-card, but messages from the serial console show boot process halting for different reasons at different points.

Some results below. Anybody any clues?

Booting LibreELEC-H6.arm-11.0-nightly-20230715-9a33cd2-orangepi-one-plus and monitoring the serial port gives some clues:

...

Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1...

...

Hit any key to stop autoboot: 0

switch to partitions #0, OK

mmc0 is current device

Scanning mmc 0:1...

Found /extlinux/extlinux.conf

Retrieving file: /extlinux/extlinux.conf

Ignoring unknown command: disk=UUID=1dbaf091-9f9b-458c-adf2-ac409022867d

1: LibreELEC

Retrieving file: /KERNEL

append: boot=UUID=1507-1311

Retrieving file: /sun50i-h6-orangepi-one-plus.dtb

...

[ 0.000000] Unknown kernel command line parameters "boot=UUID=1507-1311", will be passed to user space.

...

*** Error in mount_flash: mount_common: Could not mount UUID=1507-1311 ***

### Starting debugging shell for boot step: mount_flash... type exit to quit ###

Rebooting from the same image:

...

Loading Environment from FAT... ** Bad device specification mmc 0 **

System enters then in U-Boot-terminal. In there mmc cannot be started:

=> mmc list

mmc@4020000: 0

=> mmc info

=>

Restarting then results in:

U-Boot SPL 2022.10 (Jul 16 2023 - 11:07:20 +0000)

DRAM: 1024 MiB

Trying to boot from MMC1

NOTICE: BL31: v2.8(release):fedfb6b-dirty

NOTICE: BL31: Built : 09:52:28, Jul 16 2023

NOTICE: BL31: Detected Allwinner H6 SoC (1728)

NOTICE: BL31: Found U-Boot DTB at 0xa06f288, model: OrangePi One Plus

ERROR: PMIC: Found unknown PMIC 00

ERROR: RSB: read command: 0x103

ERROR:

MaartenJD · December 15, 2023 at 4:27 PM

See issue on GitHub

MaartenJD · April 28, 2024 at 2:17 PM

Issue continues to exist on Latest Beta Version (2024.04).

mikeneko007 · August 6, 2024 at 3:18 PM

We have identified a similar problem with OrangePI 3 LTE.
Seems to be a problem with AllwinerH6 and AXP805 RSB.
The code is in arm-trusted-firmware.
However, I have tried to change the speed, and it improves, but it still occurs.
When this occurs, various voltages cannot be changed.
I replaced the PMIC, but the situation did not improve.
Also, the AXP805 has an I2C communication method, which we tested on Linux, but it did not work.
When I plug and unplug the USB power supply with a fine-tuned sense, it sometimes works fine.
As far as I can see from the RSB waveform, it looks like there is a problem with the PMIC AXP805.
But I couldn't find a fix for this problem.
The arm-trusted-firmware also seems to be tied to Linux power management and rebooting, making Linux Reboot unstable.

MaartenJD · September 14, 2024 at 4:34 PM

Hello mikeneko007.

Good to see some activity in this post. See my posts on GitHub. I was inspired by this patch that uses I2C instead of RSB on a OrangePi-3-LTS. And this patch, that rolls back Armbian for OPI-One-Plus from RSB to I2C. I had some succes with it, that is successful boots but not reliably. Where in the code did you try some speed changes ; in the RSB-part? Booting an Armbian image works 100% fine, by the way. How to get this Armbian patch consistently in the Libreelec-code?

(allwinner: uboot: make consistent use of r_i2c across all stages from bootloader to kernel ; In sunxi-6.1 and sunxi-6.5 kernel we have a patch that changes r_rsb to r_i2c. But same change is not done for u-boot. Mixing use of r_rsb and r_i2c seems to cause issues if its also something handled in crust. Hence making it consistent across u-boot and kernel dts files").