fitImage align 8-byte for ARM64
Matthias Schoepfer
matthias.schoepfer at googlemail.com
Mon Jan 6 16:22:02 CET 2020
Hi Tom,
thanks for your reply. As far as I can understand this code, only if
fdt_high is set to 0xffffffffffffffff (which is the very case for
dragonboard410c) a not aligned mapping of the fdt can happen.
In this case, the address is images->ft_addr, which I *think* comes from
the fitImage creation?!
I wonder, whether just removing fdt_high is a valid solution...
Regards,
Matthias
On 1/6/20 3:20 PM, Tom Rini wrote:
> On Mon, Jan 06, 2020 at 01:47:25PM +0100, Matthias Schoepfer wrote:
>
>> Hi!
>>
>> I have had trouble booting a fitImage packed kernel for dragonboard410c,
>> which is an ARM64 platform. After days and days of debugging, I found that
>> the fdt is 4-byte aligned. But within the linux kernel,
>> Documentation/arm64/booting.txt says, fdt must be 8 byte aligned.
>>
>> If I change the alignment by means of fdt_high, the Kernel boots, otherwise,
>> it hangs.
>>
>> Is there an option to align the fitImage to 8-byte boundaries, and if not,
>> is it feasible to submit a patch or will this never have a chance to get
>> merged?!
>
> That's interesting. It sounds like you need to look at
> boot_relocate_fdt() perhaps? Thanks!
>
--
Dr.-Ing. Matthias Schöpfer
matthias.schoepfer at googlemail.com
More information about the U-Boot
mailing list