Custom .bbappend file not recognized when modifying linux-toradex for Colibri VF61

I tried to follow the instructions from the Webinar On-Demand: Part 2 (Advanced) - Building Embedded Linux Images with the Yocto Project and created a new layer “meta-ldms”

(tree output)

meta-ldms/  
|── conf  
│   ├── layer.conf  
│   └── machine  
│       └── colibri-vf-ldms.conf  
├── COPYING.MIT  
├── README  
├── recipes-bsp  
│   └── u-boot  
│       ├── u-boot-toradex  
│       │   └── 0001-change-standard-dtb-file-to-ldms.patch  
│       └── u-boot-toradex_git.bbappend  
├── recipes-example  
│   └── example  
│       └── example.bb  
└── recipes-kernel  
    └── linux  
        ├── linux-toradex-4.4  
        │   ├── 0001-add-ldms-specific-devicetree.patch  
        │   ├── 0001-calibrate.c-Added-some-printk-statements.patch  
        │   ├── 0001-include-ldms-devicetree-in-Makefile.patch  
        │   └── defconfig  
        └── linux-toradex_4.4.bbappend  

I copied "linux-toradex_4.4.bbappend from ./oe-core/layers/meta-toradex-nxp/recipes-kernel/linux/linux-toradex_4.4.bbappend and added some patch files to SRC_URI.

include conf/tdx_version.conf  

FILESEXTRAPATHS_prepend := "${THISDIR}/linux-toradex-4.4:"  
LOCALVERSION = "-${TDX_VER_ITEM}"  
SRCREV = "a126a5e5dc2fcc5cb36af14c89b440cc8e3bab30"  
SRCBRANCH = "toradex_vf_4.4"  
PR = "2.8b1-ldms"  
#SRCREV_use-head-next = "${AUTOREV}"  
#SRCBRANCH_use-head-next = "toradex_vf_4.4-next"  
SRC_URI += " \  
        file:///0001-calibrate.c-Added-some-printk-statements.patch \  
        file:///0001-add-ldms-specific-devicetree.patch \  
        file:///0001-include-ldms-devicetree-in-Makefile.patch \  
        file:///defconfig \  
" 
COMPATIBLE_MACHINE = "(colibri-vf-ldms)  

my colibri-vf-ldms.conf looks like this.

MACHINEOVERRIDES =. "vf:vf50:vf60:"  
  
include conf/machine/include/imx-base.inc  
include conf/machine/include/tune-cortexa5.inc  

PREFERRED_PROVIDER_virtual/kernel ?= "linux-toradex"  
KERNEL_IMAGETYPE = "zImage"  
KERNEL_DEVICETREE += "vf500-colibri-eval-v3.dtb vf610-colibri-eval-v3.dtb \  
                      vf500-colibri-ldms.dtb vf610-colibri-ldms.dtb \  
                      vf500-colibri-aster.dtb vf610-colibri-aster.dtb"  

# U-Boot of our newer release read the Kernel and device tree from static UBI volumes,  
# hence no need to deploy the kernel binary in the image itself  
RDEPENDS_kernel-base = ""  

PREFERRED_PROVIDER_u-boot ?= "u-boot-toradex"  
PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot-toradex"  
PREFERRED_PROVIDER_virtual/kernel-module-mcc ?= "kernel-module-mcc-toradex"  
PREFERRED_PROVIDER_virtual/kernel-module-mcc-dev ?= "kernel-module-mcc-toradex"  
PREFERRED_VERSION_mqxboot ?= "1.%"  

# U-Boot NAND binary includes 0x400 padding required for NAND boot  
UBOOT_BINARY ?= "u-boot-nand.imx"  
UBOOT_MAKE_TARGET = "u-boot-nand.imx"  
UBOOT_MACHINE ?= "colibri_vf_defconfig"  

IMAGE_FSTYPES = "wic.gz tar.xz ubifs"  
# wic support  
WKS_FILE = "sdimage-bootpart.wks"  
WIC_CREATE_EXTRA_ARGS_append = " --no-fstab-update"  

# Enable free --space-fixup (-F) by default, this allows DFU updates  
MKUBIFS_ARGS = " -c 8112 -e 124KiB -m 2KiB -F"  
UBINIZE_ARGS = " -p 128KiB -m 2048 -s 2048"  
UBI_VOLNAME = "rootfs"  

SERIAL_CONSOLE ?= "115200 ttyLP0"  

MACHINE_FEATURES += "usbgadget usbhost vfat alsa touchscreen"  

~

When I do “bitbake virtual/kernel” my machine configuration (colibri-vf-ldms) is used correctly, however the linux-toradex_4.4.bbappend file is not used from my layer. Instead, the /oe-core/layers/meta-toradex-nxp/ layer is used.

My layer shows up in
bitbake-layers show-layers,
but not in
bitbake-layers show-appends | grep -A 5 linux-toradex

Any hints?

Best regards,
Torsten Coym

Hi,

What is the priority of your layer (defined in layer.conf in conf folder of your layer)?

Hi

Did you add the additional paths to *bb/*bbappend files in your conf/layer.conf? I.e.:

BBFILES += “${LAYERDIR}/recipes-//.bb ${LAYERDIR}/recipes-//.bbappend”

Max

Hi,
I set the following in ./meta-ldms/conf/layer.conf:

BBFILE_PRIORITY_ldms-layer = “95”

The priority of “95” also shows up in bitbake-layers show-layers

Thanks Max! That did the trick!

I used
bitbake-layers create-layer

and this generated the following lines in meta-ldms/conf/layer.conf
# We have recipes-* directories, add to BBFILES
BBFILES += “${LAYERDIR}/recipes-//.bb \
${LAYERDIR}/recipes-
//.bbappend”

which is apparently a typo (two backslashes at the line end). Changing this line as you suggested made the .bbappend file visible for bitbake.

Torsten