ALL-H3-CC-H5 goes straight into FEL mode

My new ALL-H3-CC-H5 doesn't boot from any of the available images from (micro) SD card, it always goes into FEL mode, regardless of an SD-card with a viable image being inserted or not. One in FEL mode I can detect it with sunxi-fel and load a self-compiled u-boot and from that u-boot  boot from the micro-SD card. I can also boot with a different H5-SoC board (OPI PC2) from the same SD-card.
Once booted I'm on:
root@libre-computer:/sys/bus/platform/drivers/sunxi-mmc# uname -a
Linux libre-computer 4.19.55+ #50 SMP PREEMPT Sun Jun 23 14:43:37 EDT 2019 aarch64 aarch64 aarch64 GNU/Linux
root@libre-computer:/sys/bus/platform/drivers/sunxi-mmc# cat /etc/os-release 
NAME="Ubuntu"
VERSION="16.04.6 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.6 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial


To see if it would boot from eMMC I purchased a 8GB eMMC card so I could write nam image to that (using the distro I booted from in FEL mode). However that idea was thwarted as I get lots of errors even when booting (from FEL+SD-card) with the eMMC attached:
[    3.935365] sunxi-mmc 1c11000.mmc: Linked as a consumer to regulator.5
[    3.977610] sunxi-mmc 1c11000.mmc: initialized, max. request size: 2048 KB, uses new timings mode
[  199.658761] sunxi-mmc 1c11000.mmc: Dropping the link to regulator.5
[  202.939842] sunxi-mmc 1c11000.mmc: Linked as a consumer to regulator.5
[  202.978671] sunxi-mmc 1c11000.mmc: initialized, max. request size: 2048 KB, uses new timings mode
[  203.144413] sunxi-mmc 1c11000.mmc: data error, sending stop command
[  203.150855] sunxi-mmc 1c11000.mmc: send stop command failed
[  203.156588] mmc1: switch to bus width 8 failed
[  203.159818] sunxi-mmc 1c11000.mmc: data error, sending stop command
[  203.166512] sunxi-mmc 1c11000.mmc: send stop command failed
[  203.173910] mmc1: switch to bus width 4 failed
[  203.174541] mmc1: new high speed MMC card at address 0001
[  203.181724] mmcblk1: mmc1:0001 H8G4a2 7.28 GiB 
[  203.182909] mmcblk1boot0: mmc1:0001 H8G4a2 partition 1 4.00 MiB
[  203.183954] mmcblk1boot1: mmc1:0001 H8G4a2 partition 2 4.00 MiB
[  203.186110] sunxi-mmc 1c11000.mmc: data error, sending stop command
[  203.194347] sunxi-mmc 1c11000.mmc: data error, sending stop command
[  203.200818] sunxi-mmc 1c11000.mmc: send stop command failed
[  203.208252] sunxi-mmc 1c11000.mmc: data error, sending stop command
[  203.214703] sunxi-mmc 1c11000.mmc: send stop command failed
[  203.221909] sunxi-mmc 1c11000.mmc: data error, sending stop command
[  203.228417] sunxi-mmc 1c11000.mmc: send stop command failed
[  203.234351] sunxi-mmc 1c11000.mmc: data error, sending stop command
[  203.240812] sunxi-mmc 1c11000.mmc: send stop command failed
[  203.332578] sunxi-mmc 1c11000.mmc: data error, sending stop command
[  203.339022] sunxi-mmc 1c11000.mmc: send stop command failed
[  203.346111] mmc1: switch to bus width 8 failed
[  203.346675] sunxi-mmc 1c11000.mmc: data error, sending stop command
[  203.353209] sunxi-mmc 1c11000.mmc: send stop command failed
[  203.360477] mmc1: switch to bus width 4 failed
etc etc

I'm powering the board via the microUSB port with a 5V 4Amp PSU.

Any hints/suggestions what I could to to get it to boot from SD-card or fix the eMMC issue?

Sign In or Register to comment.