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
On Mon, 2021-03-15 at 17:01 +0100, Zoran wrote:
> > How can I instruct Yocto to execute do_image_cpio first?
>
> YOCTO people are entitled to answer that question. Aren't ya, INTEL folks???
>
> Actually, iNTEL (IOTG) is responsible for that (since YOCTO support is
> 90% from INTEL), and I assume
> Please be aware that this is a community mailing list for the Yocto
> Project, and we expect everyone to be as pleasant as possible
> I don't think the tone of your last email is appropriate for our
> mailing lists.
Unfortunately, Nicolas, you are barking under the wrong tree.
Please, go to
I can tell you... Ross!
Please, focus on The Problem. Could you, please???
Since, I, an independent entity, am trying to help the people!
OK? Since I do not care about political IOTG development, rather than
on overall (NOT INTEL) resolution of the problem?!
Do you understand the core of the
hey Zoran,
On Mon, Mar 15, 2021 at 5:01 PM Zoran wrote:
>
> > How can I instruct Yocto to execute do_image_cpio first?
>
> YOCTO people are entitled to answer that question. Aren't ya, INTEL folks???
>
> Actually, iNTEL (IOTG) is responsible for that (since YOCTO support is
> 90% from INTEL),
> How can I instruct Yocto to execute do_image_cpio first?
YOCTO people are entitled to answer that question. Aren't ya, INTEL folks???
Actually, iNTEL (IOTG) is responsible for that (since YOCTO support is
90% from INTEL), and I assume INTEL YOCTO people are entitled
answering that///
Thank
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
> 1. have Yocto generate an initramfs.cpio.xz.uboot file
> instead of just an initramfs.cpio.xz file and to
I assume this is not too hard to achieve. Somewhere in some bitbake
config file this should be added, but either me do not know that.
So, we'll both wait for this info, maybe some new
Thank you very much for your help on the second issue! I was unaware of the
fact that another mkimage call is necessary. After taking a look at the the
references you provided, I was able to boot the system from an initramfs.
However, my current approach requires two manual steps after running
BBB example:
https://www.yoctoproject.org/pipermail/yocto/2018-July/041696.html
The line:
DISTRO_FEATURES_append = " ram"
Should be:
DISTRO_FEATURES_append = " nfs"
BSP Traces for BBB (YOCTO Warrior):
Hello everyone,
I am currently using this (
https://source.codeaurora.org/external/imx/imx-manifest/tree/imx-5.4.3-2.0.0.xml?h=imx-linux-zeus
) Yocto-based build setup provided by NXP to create a custom Linux
distribution for one of the i.MX boards. My custom image is based on the
11 matches
Mail list logo
