[U-Boot] [PATCH] imximage: Fix the bootdata.size calculation

[Li Ye-B37916 <b37916@freescale.com>]

Hi Stefano,

On 10/22/2014 4:14 PM, Stefano Babic wrote:
> Hi Ye,
>
> On 22/10/2014 09:38, Li Ye-B37916 wrote:
>
>> You can look into the "Figure 8-21. Image Vector Table" in the system boot chapter of i.MX6Q manual. The bootdata.start points
>> to the beginning of the destination memory, which means the bootdata.size should have IVT offset included.
> Well, ok, this is an interpretation....
>
>>  We also have checked
>> the boot rom codes for this.
> ok - this is the most important thing. Is it the same for all MX6 and
> MX53 ?

Yes. This is same for all MX6 and MX53.

>
>> We found this issue when booting from QSPI NOR on i.MX6SX. The u-boot runs into abnormal (crash or stop) after booting.  We checked the
>> destination memory where the image is loaded to, and found hundreds of bytes at the image end are not loaded into memory. Since there
>> is a 4096 bytes round in the calculation, so the image size decides if the issue can be reproduced. It is not easy to see the issue by SD boot.
> ok - the only thing that it looks weird is that the issue happens now
> and not with a MX6Q(D) booting from SPI-NOR. There are several boards
> booting from SPI, but I have not heard about such as problems.
>
> Best regards,
> Stefano Babic
>
>
There are some reasons:
1. The SPI-NOR IVT offset is 0x400, but QSPI-NOR IVT offset is 0x1000.  Because of the 0x1000 round, the possibility of showing the issue on SPI-NOR is less than QSPI-NOR.  Even for QSPI-NOR, we only
reproduce it on some image with particular size .

2. The IVT_offset was once included in the calculation before this patch "2013-08-31     Stefano Babic    tools: imx_header should not include flash_offset".

3. At the end of the image, most of data are zero.

Best regards,
Ye Li