Hi Maxime
On 17/07/23 18:19, Maxime Ripard wrote:
Hi,
On Fri, Jul 14, 2023 at 07:20:47PM +0530, Neha Malcom Francis wrote:
This series aims to eliminate the use of additional custom repositories such as k3-image-gen (K3 Image Generation) repo and core-secdev-k3 (K3 Security Development Tools) that was plumbed into the U-Boot build flow to generate boot images for TI K3 platform devices. And instead, we move towards using binman that aligns better with the community standard build flow.
This series uses binman for all K3 platforms supported on U-Boot currently; both HS (High Security, both SE and FS) and GP (General Purpose) devices.
Background on using k3-image-gen:
- TI K3 devices require a SYSFW (System Firmware) image consisting
of a signed system firmware image and board configuration binaries, this is needed to bring up system firmware during U-Boot R5 SPL startup.
- Board configuration data contain board-specific information
such as resource management, power management and security.
Background on using core-secdev-k3:
- Contains resources to sign x509 certificates for HS devices
Series intends to use binman to take over the packaging and signing for the R5 bootloader images tiboot3.bin (and sysfw.itb, for non-combined boot flow) instead of k3-image-gen.
Series also packages the A72/A53 bootloader images (tispl.bin and u-boot.img) using ATF, OPTEE and DM (Device Manager)
Tested-by: Maxime Ripard mripard@kernel.org
Thanks for testing!
It took a while to figure out that the tiboot3.bin file was for the HS-FS variant now, while I was using a GP board.
Depends on the board, based on the commonly available boards tiboot3.bin is symlinked to either GP or HS-FS.
Maybe we should clarify that in the doc?
But yes, I will factor this into the docs.
Maxime