We have ported our module to the new 2019.04 U-boot and have seen that our u-boot will not boot from NAND when SECURE_BOOT is enabled. But it will boot from RAM using uuu tool.
Why is it now necessary to sign the U-boot with this new version?
In the previous version we used 2017.03 that was not necessary using the same configuration
Is the HAB events checked during boot and if that fails u-boot will not start?
Best regards,
--
Mike Engel
Solved! Go to Solution.
Hello,
Please let me know more details about the issue.
1.
The following U-boot release is used, correct?
2.
U-boot configuration: CONFIG_SECURE_BOOT=y
i.MX 6UL fuse SEC_CONFIG[1] =0 (open)
3.
Uboot does not boot from NAND and it boots if CONFIG_SECURE_BOOT=n
Have a great day,
Yuri.
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
Hello,
Please let me know more details about the issue.
1.
The following U-boot release is used, correct?
2.
U-boot configuration: CONFIG_SECURE_BOOT=y
i.MX 6UL fuse SEC_CONFIG[1] =0 (open)
3.
Uboot does not boot from NAND and it boots if CONFIG_SECURE_BOOT=n
Have a great day,
Yuri.
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.