Am 11.07.2016 um 06:23 schrieb Peter Robinson:
On Mon, Jul 11, 2016 at 4:57 AM, Andreas Färber afaerber@suse.de wrote:
P.S. The upstream arm-trusted-firmware fip_create tool doesn't know about --bl30 and --bl301 btw, anyone any insights?
If you find details on the upstream ATF support I'd love a link for more details
https://github.com/ARM-software/arm-trusted-firmware/tree/master/tools/fip_c...
I found a commit renaming BL3-0 to SCP_BL2, but no mention of BL3-0-1 beyond Hardkernel and this patchset.
https://github.com/ARM-software/arm-trusted-firmware/commit/f59821d51255f14e...
$ make -C u-boot-hardkernel fip_create $ ./u-boot-hardkernel/tools/fip_create/fip_create --dump fip.bin Firmware Image Package ToC: --------------------------- - SCP Firmware BL3-0: offset=0x4000, size=0x9E88 - SCP Firmware BL3-0-1: offset=0x10000, size=0x1758 - EL3 Runtime Firmware BL3-1: offset=0x14000, size=0x110D0 - Non-Trusted Firmware BL3-3: offset=0x28000, size=0x36AF6 ---------------------------
$ make -C arm-trusted-firmware fiptool $ ./arm-trusted-firmware/tools/fip_create/fip_create --dump fip.bin Firmware Image Package ToC: --------------------------- - SCP Firmware SCP_BL2: offset=0xD8, size=0x9E88 - Unknown entry: offset=0x9F60, size=0x1758 - EL3 Runtime Firmware BL31: offset=0xB6B8, size=0x110D0 - Non-Trusted Firmware BL33: offset=0x1C788, size=0x36AF6 ---------------------------
Note that the offsets for BL30[1] are shown differently.
Regards, Andreas