From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id 22CCB1061B3F for ; Tue, 31 Mar 2026 12:36:31 +0000 (UTC) Subject: Re: [yocto] error while adding device tree overlay for UART to the image #bitbake #linux To: "Crane" , yocto@lists.yoctoproject.org From: seyd.dany@gmail.com X-Originating-Location: Regensburg, Bavaria, DE (95.130.167.66) X-Originating-Platform: Windows Chrome 146 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Tue, 31 Mar 2026 05:36:22 -0700 References: <6kB9.1729694356995050356.znfv@lists.yoctoproject.org> In-Reply-To: <6kB9.1729694356995050356.znfv@lists.yoctoproject.org> Message-ID: <725242.1774960582612514995@lists.yoctoproject.org> Content-Type: multipart/alternative; boundary="qaJ0yrvtvQOhCdkXxlPs" List-Id: X-Webhook-Received: from 45-33-107-173.ip.linodeusercontent.com [45.33.107.173] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Tue, 31 Mar 2026 12:36:31 -0000 X-Groupsio-URL: https://lists.yoctoproject.org/g/yocto/message/66365 --qaJ0yrvtvQOhCdkXxlPs Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello Crane, I faced a similar issue when working with UART overlays on Raspberry Pi 5 u= sing Yocto (scarthgap + meta-raspberrypi). In my case, the problem was not the kernel build itself, but how the overla= ys were handled during image generation (wic stage). What worked for me was: 1. Instead of relying only on RPI_KERNEL_DEVICETREE_OVERLAYS, I explicitly = appended the overlay in my configuration: RPI_KERNEL_DEVICETREE_OVERLAYS:append =3D " \ overlays/uart0-pi5.dtbo \ " 2. Additionally, I created a bbappend in my custom layer to ensure the over= lay is properly referenced in config.txt: recipes-bsp/bootfiles/rpi-config_git.bbappend with the following content: do_deploy:append() { echo "dtoverlay=3Duart0-pi5" >> $CONFIG } This ensures that: - the dtbo is deployed correctly - and also picked up by the boot configuration It seems that the WIC error ("Malformed boot file entry") can happen if the= overlay is present in KERNEL_DEVICETREE but not properly handled or refere= nced during boot file generation. After this change, the image was generated without errors and the UART over= lay was applied correctly at boot. Hope this helps. Best regards, Danyal --qaJ0yrvtvQOhCdkXxlPs Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

Hello Crane,


I faced a similar iss= ue when working with UART overlays on Raspberry Pi 5 using Yocto (scarthgap= + meta-raspberrypi).

In my case, the problem was n= ot the kernel build itself, but how the overlays were handled during image = generation (wic stage).

What worked for me was:

1. Instead of relying only on RPI_KERNEL_DEVICETREE_OV= ERLAYS, I explicitly appended the overlay in my configuration:
=
RPI_KERNEL_DEVICETREE_OVERLAYS:append =3D " \
overlays/uart0-pi5.dtbo \
"

2. = Additionally, I created a bbappend in my custom layer to ensure the overlay= is properly referenced in config.txt:

recipes-bsp/= bootfiles/rpi-config_git.bbappend

with the followin= g content:

do_deploy:append() {
= echo "dtoverlay=3Duart0-pi5" >> $CONFIG
}
This ensures that:
- the dtbo is deployed = correctly
- and also picked up by the boot configuration<= /span>

It seems that the WIC error ("Malformed boot file e= ntry") can happen if the overlay is present in KERNEL_DEVICETREE but not pr= operly handled or referenced during boot file generation.

After this change, the image was generated without errors and the UA= RT overlay was applied correctly at boot.

Hope this= helps.

Best regards,
Danyal 
--qaJ0yrvtvQOhCdkXxlPs--