Hi, Are you saying it worked before and now it does not anymore? Did you make changes to the device tree? Pretty much exactly what the message is saying: the kernel cannot find the root file system to

Thanks, Richard. That's what I thought it is. Essentially, the includes are, as expected, resolved at parse time of the recipes, which makes entirely sense. The include files themselves conditionally

I have been scratching my head over building openjdk-8 with multilib for an aarch64 system. Essentially, I want to use 32-bit OpenJDK on the 64-bit system. Theoretically adding to local.conf require c

Thanks, Khem. Yes, I am. I actually discovered what the problem was: I built my system for 64-bit but Broadcom's proprietary libraries are 32-bit. I switched the system to 32-bit and now gst-inspect s

I am trying to play back mp4 video (venerable Big Buck Bunny at this time) on RPi3. I added gstreamer1.0, gstreamer1.0-omx and the plugins to the image. libgstomx.so is installed in usr/lib/gstreamer-

I am trying to play back mp4 video (venerable Big Buck Bunny at this time) on RPi3. I added gstreamer1.0, gstreamer1.0-omx and the plugins to the image. libgstomx.so is installed in usr/lib/gstreamer-

Hi Byron, It's a dependency problem. The build system cannot find a recipe to build libdebuglog1. You either need to provide that or you don't install anything that requires libdebuglog1. :rjs

Pankaj, Can you please provide the entire error message? :rjs

#raspberrypi #yocto

Did you edit the recipe while a build was running? :rjs

Hi Damien, You do this with a shell function that is added to ROOTFS_POSTPROCESS_COMMAND. Here is a script that I use to create SSH keys: # Image post-processing to configure sshd # Setup ssh key logi

Thank you, Joshua. I might try your idea. I have noticed that it is tied to the rootfs as I tried to use ondisk/ondrive to create images for different partitions. But that did not work. Actually, the

eMMC devices commonly have three hardware partitions: two boot partitions and a user partition. I was looking for a convenient way to have wic build an image for the boot partition and one for the use

Ok, I found the answer to my own question. It's the typical extended partition issue. :rjs

I seem to be running into wic problems today... I have the following wks file: >>>>> part SPL --source rawcopy --sourceparams="file=SPL" --ondisk mmcblk --no-table --align 1 part u-boot --source rawco

Thanks, guys, I appreciate it. Doing it dynamically on first boot would probably work as it is a data partition and not the rootfs partition. I will give it a try. :rjs

I was looking for a way in a wks file to have wic grow the last partition to fill up the remainder of the disk. Of course wic does not know how large the disk is but that could be a parameter. The alt

Hi, There is no simply answer to your question. Most generally speaking any type of security, not just for computers and embedded systems, is a tradeoff between risk and cost. The fact that your appli

#selinux

Hi Stefan, I agree that it is odd that a recipe copies a file, in this case the bl31 bootloader image, from the deploy area to the recipe area. This bootloader binary is created by the imx-atf recipe.

#yocto

You have been invited to the following event. Yocto Project Technical Team Meeting When Monthly from 8am to 9am on the third Tuesday Pacific Time - Los Angeles Where Zoom Meeting: https://zoom.us/j/99

Hi Trevor, I am afraid the error message did not make it into your previous e-mail. :rjs