@kacf I’ve followed your steps (modified for the x86_64 architectures) and had no success with the resulting .EFI file. The only difference between our two build steps was that I didn’t use the --host option for ./configure and that the -p option for the grub-mkimage used /foobar (came from an example I found on the internet). But after copying the file to the boot partition of my “mender ready” Brix machine, it still ends up with a screen with the bar cursor in the upper left corner (so no command line or boot-through).
Is there a special way you place your generated boot file on the boot partition? Because up to now I’ve just been booting a USB stick based Ubuntu and copying the file from another USB stick to the boot partition (having copied the original BOOTX64.EFI file so that I can get back).
I’ve done some testing with copying back the original BOOTX64.EFI copy to see if that leads to a booting system, which it does, so the issue seems to be with the generated BOOTX64.EFI.
My build steps (on a Ubuntu 18.04 LTS VM in virtualbox) are:
./autogen.sh
./configure --target=x86_64 --with-platform=efi CPPFLAGS=-Wno-error=unused-value --host=amd64-linux-gnu
make clean
make
./grub-mkimage -d ./grub-core -o bootx64.efi -O x86_64-efi -p /efi/boot linux serial part_msdos part_gpt fat ntfs normal exfat iso9660 configfile search ls echo cat cpuid loadenv sleep reboot test hashsum loopback regexp read bsd probe ext2 gcry_sha256
Any obvious errors?