Forum Discussion
New ContributorU-boot errors when using SecureBoot with Arria10
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.
ContributorHi Christian and Baptiste,
Once the HPS is in an authenticated SPL, all further authentication is expected to be done by U-boot standard libraries and has never been dependent on Altera code. Please see this U-Boot article on FIT signature verification: U-Boot FIT Signature Verification — Das U-Boot unknown version documentation .
The process is:
- The Arria 10 ROM handles authentication of SPL
- SPL uses built-in libraries to authenticate U-boot & uboot DT
- U-boot uses those same libraries to authenticate the kernel & linux DT
Regards,
Sue
New ContributorHi 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.
