* How to include fitImage-initramfs in rootfs image
@ 2019-01-24 7:09 Richard Leitner
2019-01-24 7:31 ` Robert Yang
0 siblings, 1 reply; 10+ messages in thread
From: Richard Leitner @ 2019-01-24 7:09 UTC (permalink / raw)
To: openembedded-core
Hi,
I'm currently facing issues on how to include a fitImage with
devicetrees and a INITRAMFS_IMAGE in my rootfs image.
My config is something like:
KERNEL_IMAGETYPE = "fitImage"
KERNEL_CLASSES = "kernel-fitimage"
KERNEL_DEVICETREE = "a.dtb b.dtb c.dtb"
INITRAMFS_IMAGE = "initramfs-mine"
To include the "normal" fitImage without the initramfs in the rootfs the
following works:
IMAGE_INSTALL_append += " kernel-image"
When digging around a little bit I found that the
fitImage-initramfs-mine is deployed to tmp/deploy/images but there's no
package including that file.
Therefore I'm unable to include it via IMAGE_INSTALL.
Am I missing something?
Is anybody of you aware of a solution?
Does kernel-fitimage and kernel.bbclass offer this at all?
Any help would be greatly appreciated! Thanks!
regards;Richard.L
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: How to include fitImage-initramfs in rootfs image
2019-01-24 7:31 ` Robert Yang
@ 2019-01-24 7:29 ` Richard Leitner
2019-01-24 10:33 ` André Draszik
2019-01-24 7:52 ` Robert Yang
1 sibling, 1 reply; 10+ messages in thread
From: Richard Leitner @ 2019-01-24 7:29 UTC (permalink / raw)
To: openembedded-core
On 24/01/2019 08:31, 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.
>>
>> My config is something like:
>>
>> KERNEL_IMAGETYPE = "fitImage"
>> KERNEL_CLASSES = "kernel-fitimage"
>> KERNEL_DEVICETREE = "a.dtb b.dtb c.dtb"
>> INITRAMFS_IMAGE = "initramfs-mine"
>>
>> To include the "normal" fitImage without the initramfs in the rootfs
>> the following works:
>>
>> IMAGE_INSTALL_append += " kernel-image"
>>
>>
>> When digging around a little bit I found that the
>> fitImage-initramfs-mine is
>> deployed to tmp/deploy/images but there's no package including that file.
>
> fitImage-initramfs-mine is an image, so it is not in any package, it is
> handled by kernel.bbclass, you can check it for more info.
Ok. I saw how it's generated in the kernel-fitimage.bbclass and
kernel.bbclass... But is there any "clean" way of adding it to my rootfs
image like the fitImage?
>
> // Robert
>
>>
>> Therefore I'm unable to include it via IMAGE_INSTALL.
>>
>> Am I missing something?
>> Is anybody of you aware of a solution?
>> Does kernel-fitimage and kernel.bbclass offer this at all?
>>
>> Any help would be greatly appreciated! Thanks!
>>
>> regards;Richard.L
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: How to include fitImage-initramfs in rootfs image
2019-01-24 7:09 How to include fitImage-initramfs in rootfs image Richard Leitner
@ 2019-01-24 7:31 ` Robert Yang
2019-01-24 7:29 ` Richard Leitner
2019-01-24 7:52 ` Robert Yang
0 siblings, 2 replies; 10+ messages in thread
From: Robert Yang @ 2019-01-24 7:31 UTC (permalink / raw)
To: Richard Leitner, openembedded-core
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.
>
> My config is something like:
>
> KERNEL_IMAGETYPE = "fitImage"
> KERNEL_CLASSES = "kernel-fitimage"
> KERNEL_DEVICETREE = "a.dtb b.dtb c.dtb"
> INITRAMFS_IMAGE = "initramfs-mine"
>
> To include the "normal" fitImage without the initramfs in the rootfs the
> following works:
>
> IMAGE_INSTALL_append += " kernel-image"
>
>
> When digging around a little bit I found that the fitImage-initramfs-mine is
> deployed to tmp/deploy/images but there's no package including that file.
fitImage-initramfs-mine is an image, so it is not in any package, it is
handled by kernel.bbclass, you can check it for more info.
// Robert
>
> Therefore I'm unable to include it via IMAGE_INSTALL.
>
> Am I missing something?
> Is anybody of you aware of a solution?
> Does kernel-fitimage and kernel.bbclass offer this at all?
>
> Any help would be greatly appreciated! Thanks!
>
> regards;Richard.L
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: How to include fitImage-initramfs in rootfs image
2019-01-24 7:31 ` Robert Yang
2019-01-24 7:29 ` Richard Leitner
@ 2019-01-24 7:52 ` Robert Yang
2019-01-24 7:56 ` Richard Leitner
2019-01-24 10:29 ` André Draszik
1 sibling, 2 replies; 10+ messages in thread
From: Robert Yang @ 2019-01-24 7:52 UTC (permalink / raw)
To: Richard Leitner, openembedded-core
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"
// Robert
>>
>> My config is something like:
>>
>> KERNEL_IMAGETYPE = "fitImage"
>> KERNEL_CLASSES = "kernel-fitimage"
>> KERNEL_DEVICETREE = "a.dtb b.dtb c.dtb"
>> INITRAMFS_IMAGE = "initramfs-mine"
>>
>> To include the "normal" fitImage without the initramfs in the rootfs the
>> following works:
>>
>> IMAGE_INSTALL_append += " kernel-image"
>>
>>
>> When digging around a little bit I found that the fitImage-initramfs-mine is
>> deployed to tmp/deploy/images but there's no package including that file.
>
> fitImage-initramfs-mine is an image, so it is not in any package, it is
> handled by kernel.bbclass, you can check it for more info.
>
> // Robert
>
>>
>> Therefore I'm unable to include it via IMAGE_INSTALL.
>>
>> Am I missing something?
>> Is anybody of you aware of a solution?
>> Does kernel-fitimage and kernel.bbclass offer this at all?
>>
>> Any help would be greatly appreciated! Thanks!
>>
>> regards;Richard.L
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: How to include fitImage-initramfs in rootfs image
2019-01-24 7:52 ` Robert Yang
@ 2019-01-24 7:56 ` Richard Leitner
2019-01-24 8:15 ` Robert Yang
2019-01-24 10:29 ` André Draszik
1 sibling, 1 reply; 10+ messages in thread
From: Richard Leitner @ 2019-01-24 7:56 UTC (permalink / raw)
To: openembedded-core
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.
>
> // Robert
>
>
>>>
>>> My config is something like:
>>>
>>> KERNEL_IMAGETYPE = "fitImage"
>>> KERNEL_CLASSES = "kernel-fitimage"
>>> KERNEL_DEVICETREE = "a.dtb b.dtb c.dtb"
>>> INITRAMFS_IMAGE = "initramfs-mine"
>>>
>>> To include the "normal" fitImage without the initramfs in the rootfs
>>> the following works:
>>>
>>> IMAGE_INSTALL_append += " kernel-image"
>>>
>>>
>>> When digging around a little bit I found that the
>>> fitImage-initramfs-mine is
>>> deployed to tmp/deploy/images but there's no package including that
>>> file.
>>
>> fitImage-initramfs-mine is an image, so it is not in any package, it is
>> handled by kernel.bbclass, you can check it for more info.
>>
>> // Robert
>>
>>>
>>> Therefore I'm unable to include it via IMAGE_INSTALL.
>>>
>>> Am I missing something?
>>> Is anybody of you aware of a solution?
>>> Does kernel-fitimage and kernel.bbclass offer this at all?
>>>
>>> Any help would be greatly appreciated! Thanks!
>>>
>>> regards;Richard.L
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: How to include fitImage-initramfs in rootfs image
2019-01-24 7:56 ` Richard Leitner
@ 2019-01-24 8:15 ` Robert Yang
2019-01-24 9:58 ` Richard Leitner
2019-02-20 8:37 ` Richard Leitner
0 siblings, 2 replies; 10+ messages in thread
From: Robert Yang @ 2019-01-24 8:15 UTC (permalink / raw)
To: Richard Leitner, openembedded-core
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>
// Robert
>
>>
>> // Robert
>>
>>
>>>>
>>>> My config is something like:
>>>>
>>>> KERNEL_IMAGETYPE = "fitImage"
>>>> KERNEL_CLASSES = "kernel-fitimage"
>>>> KERNEL_DEVICETREE = "a.dtb b.dtb c.dtb"
>>>> INITRAMFS_IMAGE = "initramfs-mine"
>>>>
>>>> To include the "normal" fitImage without the initramfs in the rootfs the
>>>> following works:
>>>>
>>>> IMAGE_INSTALL_append += " kernel-image"
>>>>
>>>>
>>>> When digging around a little bit I found that the fitImage-initramfs-mine is
>>>> deployed to tmp/deploy/images but there's no package including that file.
>>>
>>> fitImage-initramfs-mine is an image, so it is not in any package, it is
>>> handled by kernel.bbclass, you can check it for more info.
>>>
>>> // Robert
>>>
>>>>
>>>> Therefore I'm unable to include it via IMAGE_INSTALL.
>>>>
>>>> Am I missing something?
>>>> Is anybody of you aware of a solution?
>>>> Does kernel-fitimage and kernel.bbclass offer this at all?
>>>>
>>>> Any help would be greatly appreciated! Thanks!
>>>>
>>>> regards;Richard.L
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: How to include fitImage-initramfs in rootfs image
2019-01-24 8:15 ` Robert Yang
@ 2019-01-24 9:58 ` Richard Leitner
2019-02-20 8:37 ` Richard Leitner
1 sibling, 0 replies; 10+ messages in thread
From: Richard Leitner @ 2019-01-24 9:58 UTC (permalink / raw)
To: openembedded-core
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: How to include fitImage-initramfs in rootfs image
2019-01-24 7:52 ` Robert Yang
2019-01-24 7:56 ` Richard Leitner
@ 2019-01-24 10:29 ` André Draszik
1 sibling, 0 replies; 10+ messages in thread
From: André Draszik @ 2019-01-24 10:29 UTC (permalink / raw)
To: openembedded-core
On Thu, 2019-01-24 at 15:52 +0800, 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"
I'm n not sure bundling the initramfs with the kernel is the best approach
when using a fitImage. After all, the purpose of the FIT is to describe to
U-Boot the individual components and their location already.
Cheers,
Andre'
>
> // Robert
>
>
> > > My config is something like:
> > >
> > > KERNEL_IMAGETYPE = "fitImage"
> > > KERNEL_CLASSES = "kernel-fitimage"
> > > KERNEL_DEVICETREE = "a.dtb b.dtb c.dtb"
> > > INITRAMFS_IMAGE = "initramfs-mine"
> > >
> > > To include the "normal" fitImage without the initramfs in the rootfs
> > > the
> > > following works:
> > >
> > > IMAGE_INSTALL_append += " kernel-image"
> > >
> > >
> > > When digging around a little bit I found that the fitImage-initramfs-
> > > mine is
> > > deployed to tmp/deploy/images but there's no package including that
> > > file.
> >
> > fitImage-initramfs-mine is an image, so it is not in any package, it is
> > handled by kernel.bbclass, you can check it for more info.
> >
> > // Robert
> >
> > > Therefore I'm unable to include it via IMAGE_INSTALL.
> > >
> > > Am I missing something?
> > > Is anybody of you aware of a solution?
> > > Does kernel-fitimage and kernel.bbclass offer this at all?
> > >
> > > Any help would be greatly appreciated! Thanks!
> > >
> > > regards;Richard.L
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: How to include fitImage-initramfs in rootfs image
2019-01-24 7:29 ` Richard Leitner
@ 2019-01-24 10:33 ` André Draszik
0 siblings, 0 replies; 10+ messages in thread
From: André Draszik @ 2019-01-24 10:33 UTC (permalink / raw)
To: openembedded-core
On Thu, 2019-01-24 at 08:29 +0100, Richard Leitner wrote:
>
> On 24/01/2019 08:31, 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.
> > >
> > > My config is something like:
> > >
> > > KERNEL_IMAGETYPE = "fitImage"
> > > KERNEL_CLASSES = "kernel-fitimage"
> > > KERNEL_DEVICETREE = "a.dtb b.dtb c.dtb"
> > > INITRAMFS_IMAGE = "initramfs-mine"
> > >
> > > To include the "normal" fitImage without the initramfs in the rootfs
> > > the following works:
> > >
> > > IMAGE_INSTALL_append += " kernel-image"
> > >
> > >
> > > When digging around a little bit I found that the
> > > fitImage-initramfs-mine is
> > > deployed to tmp/deploy/images but there's no package including that
> > > file.
> >
> > fitImage-initramfs-mine is an image, so it is not in any package, it is
> > handled by kernel.bbclass, you can check it for more info.
>
> Ok. I saw how it's generated in the kernel-fitimage.bbclass and
> kernel.bbclass... But is there any "clean" way of adding it to my rootfs
> image like the fitImage?
I usually just add the fitImage manually in a ROOTFS_POSTINSTALL_COMMAND,
either via a specific project's bbclass that all actual images inherit, or
directly in the actual image recipe.
Cheers,
Andre'
>
> > // Robert
> >
> > > Therefore I'm unable to include it via IMAGE_INSTALL.
> > >
> > > Am I missing something?
> > > Is anybody of you aware of a solution?
> > > Does kernel-fitimage and kernel.bbclass offer this at all?
> > >
> > > Any help would be greatly appreciated! Thanks!
> > >
> > > regards;Richard.L
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: How to include fitImage-initramfs in rootfs image
2019-01-24 8:15 ` Robert Yang
2019-01-24 9:58 ` Richard Leitner
@ 2019-02-20 8:37 ` Richard Leitner
1 sibling, 0 replies; 10+ messages in thread
From: Richard Leitner @ 2019-02-20 8:37 UTC (permalink / raw)
To: Robert Yang, openembedded-core
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:
>>>> 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:
The INITRAMFS_IMAGE_NAME is set correctly.
>
> $ bitbake virtual/kernel <your image> -ccleansstate
> $ bitbake <your image>
Nonetheless unfortunately the image still includes the fitImage without
initramfs... Any further ideas?
Thank you!
>
> // Robert
regards;Richard.L
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2019-02-20 8:37 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-01-24 7:09 How to include fitImage-initramfs in rootfs image Richard Leitner
2019-01-24 7:31 ` Robert Yang
2019-01-24 7:29 ` Richard Leitner
2019-01-24 10:33 ` André Draszik
2019-01-24 7:52 ` Robert Yang
2019-01-24 7:56 ` Richard Leitner
2019-01-24 8:15 ` Robert Yang
2019-01-24 9:58 ` Richard Leitner
2019-02-20 8:37 ` Richard Leitner
2019-01-24 10:29 ` André Draszik
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.