FIP BL33 offset

Autumn — Thu, 15 Dec 2022 22:45:25 GMT

When running the creating the FIP, it outputs the following information:

EL3 Runtime Firmware BL31: offset=0x88, size=0xA62D, cmdline="--soc-fw"

Non-Trusted Firmware BL33: offset=0xA6B5, size=0xA9CE4, cmdline="--nt-fw"

How is the BL33 offset (0xA6B5) determined? When I used the fip.bin output it does not work. But when I used another fin.bin with a different offset it worked for me.

Thanks.

Re: FIP BL33 offset

mrudangshelat-13 — Thu, 22 Dec 2022 11:45:09 GMT

Hi @Autumn,

I hope you are doing well.

The firmware Image Package(FIP) binary contains the below-mentioned components.
At base, FIP contains ToC header and entry formats

1. BL31: Secure runtime firmware
2. BL32: Trusted OS, for example, OP-TEE (optional)
3. BL33: U-Boot/UEFI image

Here, Uboot is stored right after Runtime Firmware BL31(0x88(BL31 offset ) + 0xA62D( BL31 size) = 0xA6B5 ), if OP-TEE support is not added.

Please make sure that you have followed the steps mentioned in chapter 5 of the Layerscape Software Development Kit User Guide.

Please mention the steps that you have followed to compile the FIP binary and Processor part number for further debugging.

Thanks & Regards,

Layerscape中的主题 FIP BL33 offset

FIP BL33 offset

Re: FIP BL33 offset