diff options
| author | Ye.Li <B37916@freescale.com> | 2014-10-30 17:54:08 +0800 |
|---|---|---|
| committer | Stefano Babic <sbabic@denx.de> | 2014-11-03 10:33:01 +0100 |
| commit | de97980478db4378719a529deb8e203e33bf6f66 (patch) | |
| tree | 21a3401750a985766e476cec72090849d6561bb2 /arch/nds32 | |
| parent | d12159b63b0e0fe4842afedf84b4a497f2323b8b (diff) | |
| download | u-boot-imx-de97980478db4378719a529deb8e203e33bf6f66.zip u-boot-imx-de97980478db4378719a529deb8e203e33bf6f66.tar.gz u-boot-imx-de97980478db4378719a529deb8e203e33bf6f66.tar.bz2 | |
imximage: Fix the bootdata.size calculation
In system boot chapter of i.MX6 reference manual, the "Image Vector Table"
figure shows the bootdata.start points to the beginning of the destination
memory. It means the bootdata.size should contain the IVT offset part,
but the calculation in imximage tool does not have.
We found this issue when booting from QuadSPI NOR on i.MX6SX. The u-boot
runs into abnormal (crash or stop) after booting. After checked the destination
memory where the image is loaded to, there are hundreds of bytes at
the image end are not loaded into memory. Since there is a 4096 bytes
round in the calculation, for the booting devices using smaller IVT offset,
such as SD and SPI booting, they are not easy to reproduce.
Signed-off-by: Ye.Li <B37916@freescale.com>
Diffstat (limited to 'arch/nds32')
0 files changed, 0 insertions, 0 deletions