From: Fabien Lahoudere <fabien.lahoudere@collabora.co.uk>
To: yocto@yoctoproject.org
Subject: Re: FIT Image boot issue
Date: Wed, 05 Apr 2017 11:07:20 +0200 [thread overview]
Message-ID: <1491383240.25991.19.camel@collabora.co.uk> (raw)
In-Reply-To: <DB6PR0601MB26633CE38C3512324CDF630BCF0B0@DB6PR0601MB2663.eurprd06.prod.outlook.com>
Hi,
Did you try if it works out of yocto?
I use those lines to generate FitImage from a kernel tree:
source ../poky/build/tmp/environment-setup-cortexa8hf-neon-helix-linux-gnueabi
make ARCH=arm CROSS_COMPILE=arm-helix-linux-gnueabi- -j16 zImage ???.dtb ???.dtb
arm-helix-linux-gnueabi-objcopy -O binary -R .note -R .comment -S arch/arm/boot/compressed/vmlinux
linux.bin
mkimage -f ???.its fitImage
Fabien
On Tue, 2017-04-04 at 14:08 +0000, Gujulan Elango, Hari Prasath (H.) wrote:
> Hello all,
>
> We are using FIT image in an ARM 64 bit target based instead of separate Linux binary(Image.bin)
> and DTB. We are using a copy of the kernel fit image bbclass provided by poky in our custom
> machine layer to build the fit image. We observe that the bootloader is not able to load the
> device tree from the RAM. We are using Yocto project 2.1 and kernel version 4.9
>
> Additionally, we observe that the fit image size varies across builds. We are observing two
> different image sizes viz 6855936 and 6855932 bytes. Of these two, the fit image with size 6855932
> bytes boot properly while the image with size 6855936 doesn't boot. Most often the image with
> 6855932 bytes is generated as build output. Out of 5 to 7 builds (approximately), the image with
> size 6855936 bytes that causes the boot issue is generated once.
>
> We had modified our custom machine conf file and the kernel-fitimage.bbclass provided by poky
> layer for adding fit Image support . I have attached the modified fitimage bbclass file,our custom
> machine layer conf file ,its file generated and the error log during boot for your reference.
>
> Regards,
> Hari Prasath
>
next prev parent reply other threads:[~2017-04-05 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 14:08 FIT Image boot issue Gujulan Elango, Hari Prasath (H.)
2017-04-05 9:07 ` Fabien Lahoudere [this message]
2017-04-05 4:54 Gujulan Elango, Hari Prasath (H.)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1491383240.25991.19.camel@collabora.co.uk \
--to=fabien.lahoudere@collabora.co.uk \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.