[OE-core] How to include fitImage-initramfs in rootfs image

Richard Leitner richard.leitner at skidata.com
Thu Jan 24 09:58:19 UTC 2019


On 24/01/2019 09:15, Robert Yang wrote:
> 
> 
> On 1/24/19 3:56 PM, Richard Leitner wrote:
>>
>> On 24/01/2019 08:52, Robert Yang wrote:
>>>
>>>
>>> On 1/24/19 3:31 PM, Robert Yang wrote:
>>>> Hi Richard.L,
>>>>
>>>> On 1/24/19 3:09 PM, Richard Leitner wrote:
>>>>> Hi,
>>>>> I'm currently facing issues on how to include a fitImage with 
>>>>> devicetrees and a INITRAMFS_IMAGE in my rootfs image.
>>>
>>>
>>> I think that set both INITRAMFS_IMAGE and INITRAMFS_IMAGE_BUNDLE 
>>> should work,
>>> you have set INITRAMFS_IMAGE, so also set:
>>>
>>> INITRAMFS_IMAGE_BUNDLE = "1"
>>
>> That was also my first thought, but unfortunately this doesn't work. 
>> There's still one fitImage and one fitImage-initramfs-mine in the 
>> deploy dir and the one included in the rootfs image has the same 
>> checksum and size as the fitImage without the initramfs.
> 
> Try:
> 
> $ bitbake virtual/kernel -e >kernel.py
> 
> And check INITRAMFS_IMAGE_NAME in kernel.py, make sure it contains 
> initramfs-mine, and try:
> 
> $ bitbake virtual/kernel <your image> -ccleansstate
> $ bitbake <your image>
> 

Both fitImage's get built and deployed in tmp/deploy/images/.

But in tmp/work/../<image>/1.0-r0/rootfs/boot/ there's only the fitImage 
without the initramfs.

Apart from the tmp/deploy dir I "find" the fitImage-initramfs also in:

tmp/work/../linux/.../deploy-linux/
and
tmp/work/../linux/.../deploy-linux/linux-standard-build/arch/arm/boot/

Any more ideas?

regards;Richard.L


More information about the Openembedded-core mailing list