[U-Boot] Unable to boot the new FIT image
Simon Glass
sjg at chromium.org
Wed Jun 4 04:58:55 CEST 2014
Hi Harsha,
On 3 June 2014 20:29, Harsha Kiran <harshakiran443 at gmail.com> wrote:
> Hi Simon,
>
> I was able to succesfully test the Secure u-boot on the beaglebone black
> from the u-boot-x86 Bone git.
> Thanks for all the help and it was a great beaglebone_vboot.txt file !
Good!
>
> I have some of minor things i would like to mention when i followed the
> procedure.
>
> 1) in the 7th step
>
> 7. Put U-Boot and the kernel onto the board
> -------------------------------------------
> The MLO information is missing..
In my case I already had this on the card. Do you have instructions
for what you followed?
>
>
> 2)
>
> I was not able to boot with kernel (image.lzo) in the FIT. it gave me the
> following error
> U-Boot# bootm 0x82000000
>
> ## Loading kernel from FIT Image at 82000000 ...
> Using 'conf at 1' configuration
> Verifying Hash Integrity ... OK
> Trying 'kernel at 1' kernel subimage
> Description: unavailable
> Created: 2014-06-04 1:28:38 UTC
> Type: Kernel Image
> Compression: lzo compressed
> Data Start: 0x820000a8
> Data Size: 8543704 Bytes = 8.1 MiB
>
> Architecture: ARM
> OS: Linux
> Load Address: 0x80008000
> Entry Point: 0x80008000
> Hash algo: sha1
> Hash value: 9504d8fefcec81c054e2d0fb4e9d9b6bcfb9b4b7
> Verifying Hash Integrity ... sha1+ OK
>
> ## Loading fdt from FIT Image at 82000000 ...
> Using 'conf at 1' configuration
> Trying 'fdt at 1' fdt subimage
> Description: beaglebone-black
> Created: 2014-06-04 1:28:38 UTC
>
> Type: Flat Device Tree
> Compression: uncompressed
> Data Start: 0x82825f68
> Data Size: 34352 Bytes = 33.5 KiB
>
> Architecture: ARM
> Hash algo: sha1
> Hash value: 4b14973cf0fe4a40dc420ed55d2441c6f51f586b
> Verifying Hash Integrity ... sha1+ OK
> Booting using the fdt blob at 0x82825f68
> Uncompressing Kernel Image ... LZO: uncompress or overwrite error -1 -
> must RESET board to recover
> resetting ...
>
> U-Boot SPL 2014.07-rc2 (Jun 03 2014 - 20:09:15)
> reading u-boot.img
> reading u-boot.img
>
> But when i switch it back to the zImage it worked good. I will check again
> on this.
It might be the maximum image size:
#define CONFIG_SYS_BOOTM_LEN (16 << 20)
Is it possible that your kernel is larger than 16MB? Or that you
forgot to compress it with lzop?
Regards,
Simon
More information about the U-Boot
mailing list