imx-mkimage 6.1.36_2.1.0 includes this commit https://github.com/nxp-imx/imx-mkimage/commit/5a0faefc223e51e088433663b6e7d6fbce89bf59 which inserts an additional data structure in the generated image. The external data position passed to (the uboot) mkimage in board/freescale/common/imx/imx8-bootloader-prepare.sh needs to be adjusted accordingly, so '-p 0x5000' instead of '-p 0x3000'. You can see that same adjustment being made in the soc.mak file in the commit reference. I have only tested this on an i.MX8M Nano DDR4 EVK board, but expect it applies to all i.MX8M boards that use imx-mkimage to generate their bootloader image. This bug first appeared in the 2023.11 release.
Bumped `imx-mkimage` from `lf-5.10.72_2.2.0` to `lf-6.1.36-2.1.0` in commit: https://git.busybox.net/buildroot/commit/package/imx-mkimage?id=72de7890233026f020de4aba3e8e86c156e55773 introduces i.MX9 support. Now all i.MX8M? based targets are broken (boards using 'board/freescale/common/imx/imx8-bootloader-prepare.sh' to generate boot image).
The initial report by Martin Whitaker proposes a fix, but I don't fully understand what the fix is (and I anyway don't have any imx8 board to test it on). So can someone provide a patch?
Created attachment 9733 [details] Patch to fix this bug Here is a patch that works for me, tested on an IMX8MN platform.
(In reply to Martin Whitaker from comment #3) Can confirm that the patch fixes the issue for IMX8MM too.
Fixed by https://gitlab.com/buildroot.org/buildroot/-/commit/baaf7f738a76d363aed753888da0712c7c430976 thanks