Date: Mon, 15 Mar 2021 14:59:56 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <29235.1615763811371292564@lists.yoctoproject.org>
Content-Type: multipart/alternative;
boundary="------------7849A9BCFF24CAE51EBDCEEF"
Content-Language: en-US
--------------7849A9BCFF24CAE51EBDCEEF
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
On 3/14/21 6:16 PM, p32 via lists.yoctoproject.org wrote:
> Thank you very much. I figured out that you can have Yocto create a
> suitable U-Boot wrapper as follows (from the image recipe):
> IMAGE_FSTYPES = "cpio.xz.u-boot"
>
> Now there is only one last issue that I wasn't able to solve yet: I
> would like Yocto to not only generate this U-Boot file but also add it
> to the boot partition of a wic.gz image. I tried to extend the image
> recipe as follows:
> IMAGE_FSTYPES = "cpio.xz.u-boot wic.gz"
> IMAGE_BOOT_FILES_append +=
> "${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.cpio.xz.u-boot"
>
> Unfortunately, there is a dependency issue here. BitBake schedules the
> do_image_wic task before the do_image_cpio task, which creates the
> u-boot file. I tried to fix it as follows (from the image recipe):
> do_image_wic[depends] = "my-image-recipe:do_image_cpio"
>
> While the dependency graph acknowledges this dependency, BitBake does
> not seem to care about it. Whatever I try, do_image_wic is always
> executed first and, obviously, does not succeed. I think the problem
> is comparable to the unsolved one outlined here:
> https://stackoverflow.com/questions/58954170/yocto-creating-a-dependency-for-wic-to-cpio-gz-image
>
> How can I instruct Yocto to execute do_image_cpio first?
You might try splitting it up with two images; one that makes your CPIO
and one that makes the wic image. Since the wic image (presumably?)
doesn't even have the rootfs specified, it probably doesn't even matter
what the image is (e.g. you could use core-image-minimal as a test, or
try to make some even slimmer empty image).
I think by doing that you could do something like:
IMAGE_BOOT_FILES += "my-cpio-image.cpio.xz.u-boot"
IMAGE_FILE_DEPENDS += "my-cpio-image"
Then:
bitbake core-image-minimal
Would sort of do what you are asking
I think they key is that you need a "root file system image" that is
*not* your CPIO because wic expects to be tied to one that it can write
to the .wic image, even if thats not actually what you are doing.
>
>
>
--------------7849A9BCFF24CAE51EBDCEEF
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
On 3/14/21 6:16 PM, p32 via
lists.yoctoproject.org wrote:
Thank you very much. I figured out that you can have Yocto create
a suitable U-Boot wrapper as follows (from the image recipe):
IMAGE_FSTYPES = "cpio.xz.u-boot"
Now there is only one last issue that I wasn't able to solve yet:
I would like Yocto to not only generate this U-Boot file but also
add it to the boot partition of a wic.gz image. I tried to extend
the image recipe as follows:
IMAGE_FSTYPES = "cpio.xz.u-boot wic.gz"
IMAGE_BOOT_FILES_append +=
"${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.cpio.xz.u-boot"
Unfortunately, there is a dependency issue here. BitBake schedules
the do_image_wic task before the do_image_cpio task, which creates
the u-boot file. I tried to fix it as follows (from the image
recipe):
do_image_wic[depends] = "my-image-recipe:do_image_cpio"
While the dependency graph acknowledges this dependency, BitBake
does not seem to care about it. Whatever I try, do_image_wic is
always executed first and, obviously, does not succeed. I think
the problem is comparable to the unsolved one outlined here:
https://stackoverflow.com/questions/58954170/yocto-creating-a-dependency-for-wic-to-cpio-gz-image
How can I instruct Yocto to execute do_image_cpio first?
You might try splitting it up with two images; one that makes
your CPIO and one that makes the wic image. Since the wic image
(presumably?) doesn't even have the rootfs specified, it probably
doesn't even matter what the image is (e.g. you could use
core-image-minimal as a test, or try to make some even slimmer
empty image).
I think by doing that you could do something like:
IMAGE_BOOT_FILES += "my-cpio-image.cpio.xz.u-boot"
IMAGE_FILE_DEPENDS += "my-cpio-image"
Then:
bitbake core-image-minimal
Would sort of do what you are asking
I think they key is that you need a "root file system image" that
is *not* your CPIO because wic expects to be tied to one that it
can write to the .wic image, even if thats not actually what you
are doing.
--------------7849A9BCFF24CAE51EBDCEEF--