Forum Discussion
U-boot errors when using SecureBoot with Arria10
- 1 year ago
Hi Support team,
Good news, we found why the sign FIT of U-Boot failed. The FIT loading strategy changed since 2021.07.
In old U-Boots, FIT is load into the OCRAM then external binaries are loaded to RAM to 0x1000040.
In recent U-Boots, FIT included external binaries is fully loaded to RAM at 0x1000000, then U-Boot binary and Flat DTB are loaded to the load address (0x500000) mentionned in the FIT (it was not possible to keep the same address, in order to avoid overlap).
The jump to U-Boot failed because we forgot to change the load address of U-Boot in the U-Boot configuration. As a result, U-Boot was compiled to execute at an address different from the one to which it was copied.
So just by setting CONFIG_TEXT_BASE=0x00500000, compile and flash. then U-Boot 2024.04 correctly boot.
Thank you for your support. You can close this topic.
Hi,
Unfortunately I can't find a newer validated U-Boot version.
From the v2024.04 log, it was complaining "Can't get 'load' property from FIT 0x01000000", common causes could be the FIT image missing the load property for the fdt node, incorrect/corrupted FIT image or the boot script referencing the wrong FIT sub image.
Please try to inspect from these various aspects.
Thanks!