I have lots of HummingBoards 2 Edge with eMMC but now got a batch with the new SOM 1.5 and eMMC the original u-boot from next and stable branch (2013-10rc4) get stuck on SPL from time to time on the new SOMs so I'm trying the dev branch which has this new patch:

 

https://github.com/armbian/build/blob/master/patch/u-boot/u-boot-cubox-next/U-Boot-mx6cuboxi-add-support-for-detecting-Revision-1.5-SoMs.patch

 

Copying SPL and u-boot.img to eMMC and booting produce the following:

 

U-Boot SPL 2018.03-armbian (Jun 07 2018 - 16:06:14 -0400)
Trying to boot from MMC1 Card did not respond to voltage select!
spl: mmc init failed with error: -95
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

But if I have a SD card which has the old u-boot:

U-Boot SPL 2018.03-armbian (Jun 07 2018 - 16:06:14 -0400)
Trying to boot from MMC1

U-Boot 2013.10-rc4 (May 11 2018 - 13:06:31)
CPU: Freescale i.MX6DL rev1.3 at 792 MHz
Reset cause: POR
Board: MX6-HummingBoard2
DRAM: 1 GiB MMC: FSL_SDHC: 0, FSL_SDHC: 1
*** Warning - bad CRC, using default environment
In: serial Out: serial Err: serial
Net: FEC [PRIME]
Hit any key to stop autoboot: 0

HummingBoard2 U-Boot >

 

And everything goes fine. So it seems that the SPL tries MMC1 which I suppose is SD card so when no card is inserted it get stuck. But when booting from eMMC it does read SPL from eMMC but the new SPL try to read uboot from SD, So how can I force MMC2_2 (I guess this is eMMC) inside the code or see if the new SPL honours the HummingBoards jumpers.

 

TIA

Ok,

 

Patched 2013-10-rc4 to enable SPL_WATCHDOG and that workaround the stuck SPL every 1 of 5 boots.

 

And patched 2018-03-armbian (dev branch) to actually set USDHC3 pins on HummingBoard2 an enable it to actually have eMMC boot support from SPL seems to work, many reboots and no stuck SPL so far. Later will PR it.

 

Merged https://github.com/armbian/build/pull/1008 I can't test since I don't own a board with eMMC. Thanks.