Hi Torsten, It’s difficult to provide a resolution without knowing the specifics of your setup. However, below pointer might help: If all images in the FIP are accessible but BL2 cannot load one of the images (specifically BL32), it suggests that BL32 memory parameters (entrypoint or image information) might not be correctly populated and hence BL2 is unable to obtain the necessary information about the BL32 image, such as its load address in RAM and its size. This information is typically provided by the platform. For example, on Arm platforms, this information is provided via the file: arm_bl2_mem_params_desc.chttps://git.trustedfirmware.org/TF-A/trusted-firmware-a/+/refs/heads/integration/plat/arm/common/aarch64/arm_bl2_mem_params_desc.c. I hope this helps. Thanks, Manish Badarkhe ________________________________ From: Labs, Torsten via TF-A tf-a@lists.trustedfirmware.org Sent: 16 July 2024 16:11 To: tf-a@lists.trustedfirmware.org tf-a@lists.trustedfirmware.org Subject: [TF-A] BL2 does find only 2 images
Hey all,
i tried to setup a fip.bin and add 3 images (bl31, bl32 and bl33).
./fiptool --verbose create --soc-fw bl31.bin --nt-fw bl33.bin --tos-fw bl32.bin fip.bin
When i check the generated fip.bin with fiptool info it shows me all my three images in the fip.bin
EL3 Runtime Firmware BL31: offset=0xB0, size=0x13644, cmdline="--soc-fw"
Secure Payload BL32 (Trusted OS): offset=0x136F4, size=0x18D864, cmdline="--tos-fw"
Non-Trusted Firmware BL33: offset=0x1A0F58, size=0x9692E, cmdline="--nt-fw"
But during bootup the BL2 finds only the image id =3 and image id=5 which is BL32 and BL33. Why he is not finding the bl32?
Thanks for youre short help.
Regards
Torsten