On Thu, Feb 05, 2026 at 12:20:27PM +0000, Dorde Stojicevic wrote:
> Hi guys,
>
> and thanks for your fast response.
>
> Sorry for the formatting issue, I am bound to our company Outlook, which
> hard-codes our signatures, so this one will not be possible to take out. I am
> not quite sure git send-email would work, for the same reason + corporate
> stuff....
>
> Anyhow, an update/clarification on the things going on here (I could/should
> have sent initially, sorry for that):
>
> 1) Lynx Toolchain compiles a FIT Image with the following structure:
> {
> Images{
> Kernel-1 {
> Data=Image;
> }
> Fdt-1 {
> Data=system.dtb;
> }
> }
> Configurations {
> Here kernel-1 and fdt-1 used as default conf-1
> }
> }
> 2) Data=Image does not have the Magic Code 0x644d5241
> 3) It is booting with U-Boot SPL 2020.04+g1ccc9d93576+p1 according to Lynx. I
> haven´t tested myself since we started with 2024.04, and we need it for some
> other features.
> 4) Then I investigated differences v2020.04 vs v2024.04, and found this part
> of code came in.
> 5) The finding is consistent with last error reported by U-Boot prior to
> reset "Bad Linux ARM64 Image magic!"
>
> 6) I 1st tried patching the Data=Image in Lynx FIT with the magic code, but
> it didn’t work.
> 7) once I patched bootm in U-Boot to skip this part and behaves as in
> v2020.04 (excluded all restructuring etc.) it booted the Lynx kernel
>
> Basically, v2024.04 correctly detects "Bad Linux ARM64 Image magic!", as none
> is there at the moment, but in order to boot Lynx Hypervisor as-is this
> backward compatibility to v2020.04 is needed.
>
> Does this shine more light on it?This is helpful, yes, thanks. Can you provide an "mkimage -l" of one of these failing to boot FIT images? -- Tom
signature.asc
Description: PGP signature
