Do you have unpacked the image file before writing it to the SD card? The image you can download has the extension
xz which is a compression method. I just used the following commands to successfully download, verify and boot the image (on a RPI4b):
Download the image:
Verify the image:
gpg --verify --keyring ./eos-image-keyring.gpg eos-eos4.0-arm64-rpi4.220406-202520.base.img.xz.asc eos-eos4.0-arm64-rpi4.220406-202520.base.img.xz
this will yield a message similar to the following one if the download has been successfull and is uncorrupted:
gpg: Signature made Wed Apr 6 22:53:33 2022 CEST
gpg: using RSA key CB500F7BC9233FAD32B4E7209E0C1250587A279C
gpg: Good signature from "Endless Image Signer 1 (EIS1) <firstname.lastname@example.org>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: CB50 0F7B C923 3FAD 32B4 E720 9E0C 1250 587A 279C
Uncompress the image:
xz -d eos-eos4.0-arm64-rpi4.220406-202520.base.img.xz
Write the image to the SD card:
I assume that your SD card has the device name
/dev/mmcblk0. As this name depends on your actual hardware configuration, please make sure to use the correct device name. You can list all your connected storage devices by running
sudo umount --force /dev/mmcblk0*
sudo wipefs --force --all /dev/mmcblk0
sudo dd if=eos-eos4.0-arm64-rpi4.220406-202520.base.img of=/dev/mmcblk0 bs=8192 conv=sync,noerror status=progress
The above commands will completely wipe all traces of any former data on the SD and then write the EOS image onto it. After all commands have been run, simply remove the card without any further steps from your computer. This will then boot successfully on a RPI4b.
If for any reason the above method does not work for you, make sure that your power supply has enough output current. The RPI4b is a little bit power hungry. Use at least a good one with 2 Amps continuous current output.
There are more methods for troubleshooting, but the next one would need to use a special USB-TTL adaptor cable to see the boot logs and i don’t assume that you have such a cable handy.