[Orange Pi Zero Plus2 H5: Install to eMMC bricked device]

Ah, just to record another oddity regarding wifi:

 

iw scan failed to detect my 2.4 GHz WiFi running using channel 13 however it listed networks of the shops 30m away (line of sight) ruling out defect antenna or broken driver. 

Regular domain was correctly set to my location (DE)  (manually with `iw` and by setting in  /etc/default/crda). Maybe I missed something? (Using channel 13 is prohibted in the US afaik)

 

I changed the channel on my AP to 10 and the device connected without further issues. (this was before I decided to install everything to eMMC.)

 

[Orange Pi Zero Plus2 H5: Install to eMMC bricked device]

When I attach a display via HDMI and provide the sd card, Armbian boots successfully and stays up for at least 5 minutes. So maybe my 3.3V TTL-UART-USB or not having an HDMI output is part of the problem?

 

The logs seem to  "miss" the part between "Starting the Kernel" and "[ 44.234023] reboot: Restarting system" which does not make sense.

If the kernel cmdline does not configure serial output, then why the "Restarting system" appears?

 

Anyway, when a HDMI display is connected, I can see the full boot process which looks flawless. (when I start without an SD card, the HDMI screen stays dark)

 

Power supply: Yes, I know. The board is designed to be powered by micro USB which I do using a power supply that worked successfully with RP3B and RP0W before (yes, doesn't mean anything), even under heavy load (compiling kernel modules).

I've also attached a reasonable accurate power meter and the consumption is only around 1.3-2W and the power adapter is rated for at least 1A (5W). I'll try it with "a better" one this weekend and keep you informed.

 

 

[Orange Pi Zero Plus2 H5: Install to eMMC bricked device]

Hi,

 

after successfully booting the "Armbian_5.69_Orangepizeroplus2-h5_Ubuntu_bionic_next_4.19.13.img" image from a SD-card I decided to use "armbian-config" to copy/install Armbian to the onboard eMMC. The operation finished without an error but the devices now hangs/loops on boot. I've a TTL UART so here is the output:

 

U-Boot SPL 2018.05-armbian (Jan 09 2019 - 22:59:13 +0100)
DRAM: 512 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.0(debug):a9f803b
NOTICE:  BL31: Built : 20:16:26, Jan  7 2019
NOTICE:  BL31: Detected Allwinner H5 SoC (1718)
NOTICE:  BL31: Found U-Boot DTB at 0x407ecc8, model: OrangePi Zero Plus2
INFO:    ARM GICv2 driver initialized
INFO:    Configuring SPC Controller
NOTICE:  BL31: PMIC: Defaulting to PortL GPIO according to H5 reference design.
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9


U-Boot 2018.05-armbian (Jan 09 2019 - 22:59:13 +0100) Allwinner Technology

CPU:   Allwinner H5 (SUN50I)
Model: OrangePi Zero Plus2
DRAM:  512 MiB
MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
Loading Environment from EXT4... ** File not found /boot/boot.env **

** Unable to read "/boot/boot.env" from mmc0:1 **
Failed (-5)
In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
230454 bytes read in 35 ms (6.3 MiB/s)
starting USB...
No controllers found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3042 bytes read in 39 ms (76.2 KiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
143 bytes read in 31 ms (3.9 KiB/s)
28541 bytes read in 84 ms (331.1 KiB/s)
504 bytes read in 104 ms (3.9 KiB/s)
Applying kernel provided DT overlay sun50i-h5-usbhost2.dtbo
504 bytes read in 105 ms (3.9 KiB/s)
Applying kernel provided DT overlay sun50i-h5-usbhost3.dtbo
4155 bytes read in 81 ms (49.8 KiB/s)
Applying kernel provided DT fixup script (sun50i-h5-fixup.scr)
## Executing script at 44000000
8781919 bytes read in 480 ms (17.4 MiB/s)
14243848 bytes read in 744 ms (18.3 MiB/s)
## Loading init Ramdisk from Legacy Image at 4fe00000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    8781855 Bytes = 8.4 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
   Loading Ramdisk to 4979f000, end 49fff01f ... OK
   reserving fdt memory region: addr=4fa00000 size=6d000
   Loading Device Tree to 000000004972f000, end 000000004979efff ... OK

Starting kernel ...

[   44.234023] reboot: Restarting system

 

As you can see this takes ~44 seconds and then loops. I've also re-written the image to the SD-Card but this didn't change anything.

 

When booting the device without an SD-Card, the following is looping rapidly without an interruption:

Resetting CPU ...

resetting ...
"Synchronous Abort" handler, esr 0x5e000000
elr: 0000000000011ce4 lr : 000000004fdfa850
x 0: 0000000084000009 x 1: 000000004fdfa870
x 2: 0000000000016894 x 3: 000000004fdfa890
x 4: 0000000000013f20 x 5: 000000004fdfaa90
x 6: 00000000ffffffc8 x 7: 000000000000000a
x 8: 0000000000000044 x 9: 000103d600000000
x10: 9419820400000000 x11: 000000000000000c
x12: 4008173a0007fffe x13: 02052020a1fe8800
x14: 0c440182d8408000 x15: 00020100c4640000
x16: 100420254a2c0844 x17: 0c03fc400001a946
x18: 000000004fdffe80 x19: 000000004fdfaab0
x20: 00000000ffffffc8 x21: 000000004fdfeb70
x22: 000000000001717b x23: 000000000001717b
x24: 000000004fdfeb30 x25: 000000004fdfec70
x26: 000000004fdfeb31 x27: 0000000000000030
x28: 5e0f02892c9e0465 x29: 000000004fdfa830

 

With pressing space I can prevent autoboot and I'm getting the U-Boot shell. Sadly I have no idea what to do. Is there an easy way to revert to SD-Card booting at least?

 

Thanks!

 

Roland