I do notice that one of my Zero is having issue to boot from time to time. It can load boot.scr but fail when trying to load initrd/kernel. ls mmc 0:1 works fine in U-Boot. A workaround I saw people using was let it sit without power for a few minutes before plug in. I tried it a few times and it seems to work.
So I figured out my issue. I was indeed booting off from the leftover bootloader from our Android image. Iāll update documentations to reflect that. I donāt see a download link for that bootloader so Iāll get it uploaded tomorrow, along with how to flashing it without downloading flashing the whole Android image.
Normally we do it by taking a backup of the vendor uboot and reflashing it back.
You can find the command here
This is the install-emmc script I use and it works fine on other amlogic devices which I had tested but on radxa zero it have problem with emmc driver I suppose as it would timeout for some reason.
So this is something you run once you boot off microSD right? I think it is still gonna be handy to have the U-Boot file so people can install directly to eMMC.
Just did 2 runs and it worked fine for me. The only issue I had was that I need to run date -s 2022-01-01 first, otherwise tar will spam the console with future timestamp warning.
# Linux Host, Zero in mass storage bootrom
## Wipe mmcblk0 and install vendor U-Boot
sudo dd if=/dev/zero of=/dev/sdX bs=128M status=progress && \
sudo dd if=android-bootloader.img of=/dev/sdX bs=512 seek=1 && \
sync
# Now go to Zero's vendor U-Boot console
# WARNING
# If you have 3 devices instead of 2 listed by the command below,
# you are using upstream U-Boot.
# Change all `mmc dev 1 X` command to `mmc dev 2 X`
mmc list
## Wipe mmcblk0boot0
mmc dev 1 1
mmc erase 0 2000
## Wipe mmcblk0boot1
mmc dev 1 2
mmc erase 0 2000
reset
# Now boot into microSD to install
Edit: I might speak too soon. 2nd install completed without error but I canāt boot into eMMC. Might have something to do with how I flashed bootloader. However, the script itself gave no error for me.
I think an extra option like --warning=no-timestamp to suppress this message will be very helpful.
I wasnāt expecting the script to do that. I was talking about the timeout issue you were having. Right now I feel like you are having hardware issue, but Iāll need the error message to check with our hardware engineer.