Re: fitImage in not installed into the rootfs

Re: fitImage in not installed into the rootfs

[Abdellatif El Khlifi]

[-- Attachment #1: Type: text/plain, Size: 4037 bytes --]

Hi,

Please refer to the fitimage test module for FIT examples. More specifically, take a look on the test_initramfs_bundle function as an example of using initramfs bundles in the FIT image : https://github.com/openembedded/openembedded-core/blob/master/meta/lib/oeqa/selftest/cases/fitimage.py


Cheers
________________________________
From: Ilies CHERGUI <ilies.chergui@gmail.com>
Sent: 23 March 2021 21:05
To: Abdellatif El Khlifi <Abdellatif.ElKhlifi@arm.com>; openembedded-core@lists.openembedded.org <openembedded-core@lists.openembedded.org>
Cc: main+help@lists.yoctoproject.org <main+help@lists.yoctoproject.org>; richard.purdie@linuxfoundation.org <richard.purdie@linuxfoundation.org>; Ross Burton <Ross.Burton@arm.com>; nd <nd@arm.com>
Subject: Re: fitImage in not installed into the rootfs

Hi Abdellatif,

Thanks for your response.

I tried to search for some examples in the Yocto git repository but I didn't find an example concerning dealing with the FIT image with the latest implementation.

Could you please send me the link(s) where I can find the examples that you suggest.

Any help would be much appreciated.

Best regards,
Ilies

On Mon, 22 Mar 2021 at 12:13, Abdellatif El Khlifi <Abdellatif.ElKhlifi@arm.com<mailto:Abdellatif.ElKhlifi@arm.com>> wrote:
Hi,

It's fine that packages-split/kernel-image-fitimage is empty.

The fitImage is not expected to be in the rootfs. It's a container that includes the initramfs bundle (kernel + rootfs) and the kernel DTB. You can verify its content by inspecting the generated ITS file.

The fitImage can be included in the final image. The final image is the image to be copied to the storage device (flash, eMMC, sdcard ...).

At runtime, u-boot loads the fitImage from the storage device, copies the kernel/DTB to their specified addresses, then starts the kernel.

So, in your case just update the task that populates the final image by copying the fitImage binary to the partition where u-boot is expecting to find the fitImage. If your image is an sdcard image (ie: eMMC device) , the task name starts with IMAGE_CMD followed by the type you are specifying in IMAGE_FSTYPES. The task is implemented in a bbclass.

There are few examples in the Yocto Git repo.

Cheers
________________________________
From: Ilies CHERGUI <ilies.chergui@gmail.com<mailto:ilies.chergui@gmail.com>>
Sent: 21 March 2021 12:37
To: main+help@lists.yoctoproject.org<mailto:main%2Bhelp@lists.yoctoproject.org> <main+help@lists.yoctoproject.org<mailto:main%2Bhelp@lists.yoctoproject.org>>
Cc: richard.purdie@linuxfoundation.org<mailto:richard.purdie@linuxfoundation.org> <richard.purdie@linuxfoundation.org<mailto:richard.purdie@linuxfoundation.org>>; Abdellatif El Khlifi <Abdellatif.ElKhlifi@arm.com<mailto:Abdellatif.ElKhlifi@arm.com>>
Subject: fitImage in not installed into the rootfs

Hi everyone,

I'm using Poky with a master branch, I'm enabling the fitImage. Unfortunately, the fitImage is not packaged and not installed into the root file system.

Here is my updates in the conf/local.conf file:
KERNEL_CLASSES += "kernel-fitimage"
KERNEL_IMAGETYPE = "fitImage"
INITRAMFS_IMAGE_BUNDLE = "1"

The fitImage is well generated and deployed in the deploy directory but it is not installed into the root file system and it is not packaged. the directory kernel-image-fitimage under the packages-split of the linux work directory is empty.

Please see the attached picture ?

Am I missing something?
Any help would be much appreciated.

Best regards,
------------------------------------

M. Ilies CHERGUI

Senior Embedded Software Engineer

Mobile : +44 7309 350477

E-mail : ilies.chergui@gmail.com<mailto:ilies.chergui@gmail.com>

------------------------------------


--

------------------------------------

M. Ilies CHERGUI

Senior Embedded Software Engineer

Mobile : +44 7309 350477

E-mail : ilies.chergui@gmail.com<mailto:ilies.chergui@gmail.com>

------------------------------------

[-- Attachment #2: Type: text/html, Size: 11316 bytes --]