![]() It has been reported that link address range of previous booting stage (such as U-Boot SPL) can overlap the link address rage of FW_DYNAMIC. This means self-relocation in FW_DYNAMIC can potentially corrupt previous booting stage if any of the secondary HART enter FW_DYNAMIC before primary HART. To tackle this, we add preferred boot HART field (i.e boot_hart) in struct fw_dyanmic_info. We use this field to force secondary HARTs into relocation wait loop till preferred/primary boot HART enters FW_DYNAMIC completes self-relocation. If preferred boot HART is not available then we fall back to relocation lottery approach. Signed-off-by: Anup Patel <anup.patel@wdc.com> Reviewed-by: Atish Patra <atish.patra@wdc.com> |
||
---|---|---|
.. | ||
payloads | ||
external_deps.mk | ||
fw_base.S | ||
fw_base.ldS | ||
fw_dynamic.S | ||
fw_dynamic.elf.ldS | ||
fw_jump.S | ||
fw_jump.elf.ldS | ||
fw_payload.S | ||
fw_payload.elf.ldS | ||
objects.mk |