Let me then first describe the issue I am having, which I think results from my misunderstanding then. I would like to package a UEFI bootloader (GRUB), bzImage and initramfs.cpio.gz into an FAT

Thanks Josef, Fabien and Rudolf, it's been great help to clarify it, very appreciated.

[ all: Let me share the replay I made in private to Ajit. ] Hi Ajith, Unfortunately because you do not provide much information about the "some error" you are seeing there is not much that can be

Thats *almost* correct. It builds an image from a *artifacts*. If it does, then your dependency architecture is probably broken. You have to understand that building an image might produce artifacts

This can not be exactly true, as this guide certainly does not include anything related to the imx8. So you are either still building for qemu (as it defaults to), or using seomthing additional that

On 28.11.2019 09:32, Aj Cit wrote: Isn't this warning message straightforward? What is your build environment? Are you using root in fact? -- Maciej PijanowskiEmbedded

Hello all, What is the intended approach of building images using WIC? Most image types (except .wic) build a (root or initial ram) filesystem from *packages*, then create the respective archive or

I've followed the instruction from the yocto project: https://www.yoctoproject.org/docs/3.0/brief-yoctoprojectqs/brief-yoctoprojectqs.html till the bitbake command. However, I'm getting the following

Please name the layers and their versions in use, the MACHINE setting that you are using, the bitbake command you are issuing and the error message. The latter please verbatim, not only the two most

Hello, I'm trying to build a Yocto image for NXP i.MX8M (4 core 64-bit A53s). I am getting some error when I execute the bitmake command. I'd appreciate if you could guide me with next steps. Any

Hello All, Intel and WR YP QA is planning for QA execution for YP build yocto-3.0.1.rc3. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1.

We forgot to mention that the deadline for the CFP is December 15th. Please get your topic in before the deadline. Also, look for early-bird tickets next week!

Hello, I need to use a TPM2 software stack for my project (tpm2-tools, tpm2-abrmd, tpm2-tss, etc.), where I am already using Yocto, meta-intel, meta-oe, meta-networking, etc. I see there are

Hi JH, The image root file system size is based on the actual content of the root file system. Besides ROOTFS_SIZE there are other variables that control how the root file system is

Mauro wrote... Switching to the ‘$(openssl …)’ form has worked, even using the ${ROOT_PASSWORD} variable. Thanks for your help! -Andy.

Hi If you want to reduce the size of your root filesystem, you have to remove software you don't need. IMAGE_ROOTFS_SIZE has no effect on the size of your image-rootfs.tar.gz. Putting a smaller size

Actually I'm using: EXTRA_USERS_PARAMS = " usermod -p '$(openssl passwd -6 myrootpassword)' root;" with success on warrior. Sorry, I forgot to mention that with password algorithms like the -6 we

tar.gz ist a content-based format, not a filesystem based one. So if the tarball is that big, then you certainly have all those things in your rootfs. Look at the manifest files to find out that goes

Hi, Does the Yocto rootfs image size is based on real contents included in the image-rootfs.tar.gz? When I build the image with very large size of applications and libraries such as boost, I have my

Mauro wrote... I tried this out on a build that I am working on for which I needed to add a root password and to create a non-root user with a password. If I use: EXTRA_USERS_PARAMS += "usermod -p