1 1

Orange Pi Zero Plus2 H5: Install to eMMC bricked device

Recommended Posts

I am using the OPIZp2:H5 for a small-volume retro-AppleII hobby project called VidHD which emulates an NTSC CRT on a modern 1080p HDMI TV.




Out of 500x OPIZp2:H5 boards used for this project, we are seeing intermittent emmc boot failures on about 10% of them. On some boards, the emmc boot rarely fails (works 80%-90% of the time), while on other boards the emmc boot fails nearly every time. All these boards boot correctly 100% of the time from micro SD card.


I am using mainline linux 4.20.8 with uboot 2019.01, built with buildroot.


uboot 2019.01 is configured to disable networking and display/DE2. Disabling uboot video was recommended by Jernej because several boards had intermittent (presumably race-condition) failures in the linux HDMI DDC/EDID setup when uboot had already initialized HDMI. Some boards had frequent HDMI failures, some had few/none. Jernej was not able to reproduce the intermittent HDMI failure, but with so many boards, I have been able to test those boards which have high failure rates.


Disabling uboot video has made linux HDMI DDC init work correctly every time, but it appears to have exposed or exacerbated the uboot emmc issue.


Using a serial port to observe the boot log, uboot starts from emmc, loads the SPL, then fails to load the kernel. I have not yet investigated further.


Log from emmc boot failure:


U-Boot SPL 2019.01 (Feb 14 2019 - 13:45:37 -0800)

DRAM: 512 MiB

Trying to boot from MMC2



Log from emmc boot success (same board on the next power cycle):


U-Boot SPL 2019.01 (Feb 14 2019 - 13:45:37 -0800)

DRAM: 512 MiB

Trying to boot from MMC2



U-Boot 2019.01 (Feb 14 2019 - 13:45:37 -0800) Allwinner Technology


DRAM:  512 MiB


Loading Environment from FAT... *** Warning - bad CRC, using default environment


Net:   No ethernet found.

starting USB...

No controllers found

Hit any key to stop autoboot:  0 

switch to partitions #0, OK

mmc1(part 0) is current device

Scanning mmc 1:1...

Found U-Boot script /boot.scr

942 bytes read in 0 ms

## Executing script at 4fc00000



I will look at the emmc part number to see if that correlates with the boot failures.


Edit: Almost all the boards that are failing to boot have emmc parts which end in GETF. There are a couple boards with a Samsung emmc ending in WEPD-B031. The Samsung emmcs are failing more often than the newer GETF ones, but both types work fine on some boards while other boards have high failure rates.


Edit2: Below is my buildroot patch which disables uboot video & networking:


--- a/configs/orangepi_zero_plus2_defconfig 2018-10-02 10:49:28.790123474 -0700

+++ b/configs/orangepi_zero_plus2_defconfig 2018-10-02 10:49:28.790123474 -0700

@@ -14,3 +14,17 @@





+# VidHD
















Share this post

Link to post
Share on other sites
On 1/28/2019 at 6:37 PM, rmoriz said:

Yesterday evening I also tried the oldest Armbian releasess I was able to find:





nand-sata-install in that versions does not work either.


Has someone of you actually managed to get a full eMMC based installation working with nand-sata-install on the Orange Pi Zero Plus2 H5?

I have same the problem. My Orange Pi Zero Plus2 H5 (date 20190116) install to eMMC and cannot boot if remove sdcard :(.

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

1 1