# Checksum error on grub-efi-bootaa64.efi

**URL:** <https://hub.mender.io/t/checksum-error-on-grub-efi-bootaa64-efi/7899>\
**Category:** General Discussions\
**Tags:** yocto\
**Created:** [July 18, 2025, 6:34pm UTC](https://hub.mender.io/t/checksum-error-on-grub-efi-bootaa64-efi/7899 "2025-07-18T18:34:19Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![DrAric](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/draric/32/2539_2.png) [@DrAric](https://hub.mender.io/u/DrAric)\
**Post date:** [July 18, 2025, 6:34pm UTC](https://hub.mender.io/t/checksum-error-on-grub-efi-bootaa64-efi/7899/1 "2025-07-18T18:34:19Z")

</div>

I’m working on an integration of Mender into a Yocto scarthgap build. I cloned the scarthgap branch, but when I build it, I get this error:

> WARNING: grub-efi-mender-precompiled-2.12-r0 do\_fetch: Checksum failure encountered with download of [https://downloads.mender.io/grub-mender-grubenv/grub-efi/2.12-grub-mender-grubenv-089c619e3b52b95fd14dc664cf4f6c243c840b94/aarch64/grub-efi-bootaa64.efi;md5sum=3cdc5695de01804044e3b5606a9dc889](https://downloads.mender.io/grub-mender-grubenv/grub-efi/2.12-grub-mender-grubenv-089c619e3b52b95fd14dc664cf4f6c243c840b94/aarch64/grub-efi-bootaa64.efi;md5sum=3cdc5695de01804044e3b5606a9dc889) - will attempt other sources if available

As the URL indicates the md5sum is expected to be 3cdc56… Sure enough, if I pull that file down with wget, the md5sum is 28d3fead8ae2… I’m getting a file that looks reasonable otherwise:

```auto
% md5sum grub-efi-bootaa64.efi
28d3fead8ae217a2a879e467b920a3a3 grub-efi-bootaa64.efi
% file grub-efi-bootaa64.efi 
grub-efi-bootaa64.efi: PE32+ executable (EFI application) Aarch64 (stripped to external PDB), for MS Windows

```

But I don’t want to trust an executable that may have been modified.

Has anyone else seen this?

Thanks,  
Aric.

---

<div class="post-metadata">

**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\
**Post date:** [July 20, 2025, 8:17am UTC](https://hub.mender.io/t/checksum-error-on-grub-efi-bootaa64-efi/7899/2 "2025-07-20T08:17:57Z")

</div>

Hi @DrAric,

Thanks for the report! Is this happening on an unmodified build, e.g. plain Yocto on `scarthgap` branch with `meta-mender`? Which board target? I agree that a changed hash should be carefully checked, so I’d like to reproduce it.

Greetz,  
Josef

---

<div class="post-metadata">

**Author:** ![DrAric](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/draric/32/2539_2.png) [@DrAric](https://hub.mender.io/u/DrAric)\
**Post date:** [July 21, 2025, 12:57pm UTC](https://hub.mender.io/t/checksum-error-on-grub-efi-bootaa64-efi/7899/3 "2025-07-21T12:57:30Z")

</div>

Hi, @TheYoctoJester.

I’m using a manifest that doesn’t come directly from Yocto. It comes from AMD (formerly Xilinx): [`https://github.com/Xilinx/yocto-manifests/tree/rel-v2025.1`](https://github.com/Xilinx/yocto-manifests/tree/rel-v2025.1)

I have also added a (thin-so-far) layer to support our hardware, and I’ve added the Mender layer from [`https://github.com/mendersoftware/meta-mender.git`](https://github.com/mendersoftware/meta-mender.git) using branch `scarthgap`. The URI for the failing checksum is defined in [this file](https://github.com/mendersoftware/meta-mender/blob/master/meta-mender-core/recipes-bsp/grub/grub-efi-mender-precompiled_2.12.bb).

It’s entirely possible I don’t have the build configured correctly yet for Mender. E.g., I think it’s strange that the failing file is related to GRUB EFI while I am building for an ARM processor that boots with U-Boot.

Thanks for the help!

---

<div class="post-metadata">

**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\
**Post date:** [July 21, 2025, 3:13pm UTC](https://hub.mender.io/t/checksum-error-on-grub-efi-bootaa64-efi/7899/4 "2025-07-21T15:13:58Z")

</div>

Hi @DrAric,

Ah okay, we’re getting there. I guess that you do not have specified any additional `MENDER_FEATURES` then? Not knowing your board and setup, I have to assume that it is using a boot flow which is essentially

```auto
some loader -> u-boot -> Linux

```

The Mender defaults are GRUB+UEFI, so maybe this `local.conf` addition already gets you started:

```auto
MENDER_FEATURES_ENABLE:append = " mender-uboot mender-image-sd "
MENDER_FEATURES_DISABLE:append = " mender-grub mender-image-uefi " 

```

Please note that this will probably will require a custom `u-boot` integration as described at [Manual U-Boot integration | Mender documentation](https://docs.mender.io/operating-system-updates-yocto-project/board-integration/bootloader-support/u-boot/manual-u-boot-integration).

Hope this gets you started, let me know if you have additional questions.

Greetz,  
Josef

---

<div class="post-metadata">

**Author:** ![DrAric](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/draric/32/2539_2.png) [@DrAric](https://hub.mender.io/u/DrAric)\
**Post date:** [July 22, 2025, 1:31pm UTC](https://hub.mender.io/t/checksum-error-on-grub-efi-bootaa64-efi/7899/5 "2025-07-22T13:31:54Z")

</div>

Thanks, @TheYoctoJester, this got me past the md5sum error, so I’ll be working on the U-Boot integration next.