I am working on signing the firmware and preparing it for secure boot.
Suppose the development team provides me with a firmware image that already contains the FCB/FCFB, IVT, Boot Data, and other required boot components. My responsibility is only to sign the image and provide the signed firmware back to the development team.
I am using the CST (Code Signing Tool) to generate the signed firmware. I have created the csf.txt file and used cst.exe to generate csf.bin.
My question is: If I simply append csf.bin to the existing firmware image, will the firmware actually be considered signed?
My understanding is that the IVT contains a pointer to the CSF, so if I simply append csf.bin without updating the IVT to point to the CSF location, the ROM may not know where to find the CSF.
So, what is the correct procedure for signing an existing firmware image that already contains the FCB/FCFB, IVT, Boot Data, and other boot components?
I would like to understand the proper flow for generating the final signed firmware image that can be used for secure boot.