Re: [U-Boot] [PATCH] boston: Pad binary in .mcs to a multiple of 16 bytes

On 18.01.2018 23:36, Paul Burton wrote: > When flashing U-Boot on a Boston board using Xilinx Vivado tools, the > final 0x00 byte which ends the .relocs section seems to be skipped & > left in flash as 0xff unless the data contained in the .mcs is padded > out to a 16 byte boundary. Without our

[U-Boot] [PATCH] boston: Pad binary in .mcs to a multiple of 16 bytes

When flashing U-Boot on a Boston board using Xilinx Vivado tools, the final 0x00 byte which ends the .relocs section seems to be skipped & left in flash as 0xff unless the data contained in the .mcs is padded out to a 16 byte boundary. Without our final zero byte relocation will fail with an error