summaryrefslogtreecommitdiff
path: root/scripts
diff options
context:
space:
mode:
authorBeleswar Padhi <[email protected]>2026-01-12 15:41:02 +0530
committerTom Rini <[email protected]>2026-01-20 10:18:43 -0600
commit85f586035d75132b2b60d5e593e1c0049f5d126a (patch)
treef3922b6400ce99f2e69f6a3bf0817f74c4963233 /scripts
parenta4dc1c3b7d563ac823bf351a656100c3fb2d6424 (diff)
ARM: OMAP2+: Pad SPL binary to 8-byte alignment before DTB
The OMAP2 SPL linker script (also used for K3 platforms) currently uses a 4-byte alignment directive after the __u_boot_list section. This alignment directive only advances the location counter without padding the actual binary output. When objcopy extracts u-boot-spl-nodtb.bin, it includes only actual data, stopping at the last byte of __u_boot_list (e.g., 0x41c359fc), not an aligned address (e.g., 0x41c35a00). So, when the FIT image containing device trees is concatenated to the SPL binary, it gets appended at this unaligned file size, causing libfdt validation failure. To fix this, move the alignment directive into the __u_boot_list section itself and make it 8-byte aligned as per DT spec. This forces the linker to include padding as part of the section data, ensuring objcopy includes the padding bytes in the binary and the appended FIT image starts at an 8-byte aligned boundary. Reported-by: Anshul Dalal <[email protected]> Closes: https://lore.kernel.org/u-boot/[email protected] Fixes: 0535e46d55d7 ("scripts/dtc: Update to upstream version v1.7.2-35-g52f07dcca47c") Signed-off-by: Beleswar Padhi <[email protected]>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions