Been trying added a uboot script to my fitImage ( in hardknott) Looks like the routine fiitmage_emit_section_boot_scrip Has not updated it syntax for node name or hash node Still using’@’ instead of ‘

In Hardknott, trying to enabled signed uboot containers for signed fitimage The interaction between the uboot-sign.bbclass and the imx-boot.bb is not working MACHINE=imx8qxq-mek UBOOT_SIGN_ENABLE= “1”

Hi, during our development process, many of our recipes use AUTOREV to get latest bits Under warrior ( bitbake 1.42?) , we are seeing failures with the follow structure ( from recipes not even used by

I been trying to use bootchart2 and have it daisy chain into the orginal /sbin/init But looks like the /sbin/bootchartd.bootchart2 attempts to restore the PATH from OLDPATH export PATH=$OLDPATH exec $

This is what I have, $ cat etc/fstab # stock fstab - you probably want to override this with a machine specific one /dev/root / auto ro 1 0 proc /proc proc defaults 0 0 devpts /dev/pts devpts mode=062

I am build an image with read-only-rootfs When enabled, during startup I get a [FAILED] Failed to start Create Volatile Files and Directories. See 'systemctl status systemd-tmpfiles-setup.service' for

I am new to this area. I have been using morty to build my image and moved over to pyro now my automount is resulting in a /run/media/sda1 which is empty where , under the morty build, I see my files

With the pyro drop , when I use an -c populate_sdk, It appears that TOOLCHAIN_TARGET_TASK is not being honored. I have a TOOLCHAIN_TARGET_TASK_append = " gtest" With morty, gtest is included in -c pop

Thanks Ross, my TOOLCHAIN_TARGET_TASK_append = " hals hals-doc" does have the ‘space’, so that is not the issue. ( when I forgot it, got errors which had the ‘hal’ on the previous package, i.e gtestha

Hi Paul Thanks, I am new in this area, so could be miss-understanding some of these: What I would like to occur, when local.conf has: IMAGE_INSTALL_append = "hals" TOOLCHAIN_TARGET_TASK_append = "hals

Appreciate your suggestions. The ipk's are there $ find tmp/deploy/ipk/ -name hals* tmp/deploy/ipk/cortexa9hf-neon/hals-tests_5.0.0-r0_cortexa9hf-neon.ipk tmp/deploy/ipk/cortexa9hf-neon/hals_5.0.0-r0_

Hi 1) I had just successfully built an image with all the recipes ( hals, hals-doc) [and yes, there these are non-empty] 2) I had then successfully built image with -c populate_sdk 3) The bitbake imag

I am getting errors with morty and -c populate_sdk_ext when I have recipes which inherit bin_package These recipes work fine with Krogoth and it’s populate_sdk_ext Note: package is not empty, Use to i

I have some simple recipes which inherit bin_package Local has PACKAGE_CLASSES ?= "package_ipk" There are no issues with the krogoth release , can do -c populate_sdk and all is well with morty, same r

Thanks for the pointer. I am new to the linux/Yocto area , so if there is example, would greatly help. When you say it 'replaces', is this a the 'name' level? connman is not the same name as udhdc My

I am trying to remove the udhcp( client / server) components in busybox when I include ‘connman’ in my image. I have a busybox_%.bbappend which will SRC_URI_append = " file://no-uhdpc.cfg" no-uhdcpc.c