I think the content of IMAGE_BOOT_FILES would be right place to start looking into the issue. bitbake -e <yourimage> | grep -e "^IMAGE_BOOT_FILES=" might give more insights into this variable's

Nope, that should be enough to show that it has already been addressed upstream. By default, you'll get a v5.10-rc with -dev in master, so that confirms the fix. True that. And the time spent to

When I use `linux-yocto-dev` as the kernel provider, it works just fine (in fact, I can't seem to find the commit that *fixes* the problem there....), so I think 5.10 will be OK? Is there something

Hi Sateesh, Are you sure all layers are checked out at the same branch? (e.g. `dunfell` branch (or a branch with LAYERSERIESCOMPAT in conf/layer.conf with dunfell in it))? I suspect there was a

You're probably mixing incompatible branches of different layers - always use the same branch in all layers. at_least was added in oe-core/dunfell

If you want, I can also pick this up and merge it directly into linux-yocto and do a SRCREV bump. Have you tested against 5.10 ? I'm working through issues with it now, and it would be nice to fix

Hi Guys, I got expansion error during parsing. I want to fix this bug. can anybody know this issue please Update me. Traceback (most recent call last): File "Var <PIGZ>", line 1, in

Fixes the serial port output stopping mid way through the boot process by reverting the kernel commit that caused it. Signed-off-by: Joshua Watt <JPEWhacker@...> ---

I kept looking and I get the same error with the sdio overlay when I remove the sc16is752.

Dear all, When I try to add the overlay for the sc16is752-spi0 to my image, it fails at the task do_image_wic with the following error: I am using the kernel provided by meta-raspberrypi and add the

Hi, I'm trying to do HTTPS POST using curl with CA certificate, but I got an error as "curl_easy_perform() failed: Couldn't connect to server". The same code works on a Linux machine but not on my

Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-3.3_M1.rc2. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1.

Hello All, This is the full report for yocto-3.2.1.rc2: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults ======= Summary ======== No high

Hi Naveen, I investigated the arduino-101-ble problem and for me it's non trivial to fix. It's not related to the same missing variable that I spotted in the Nitrogen case, but rather there are some

From: Wojciech Zmuda <wojciech.zmuda@...> Machines not inheriting zephyr-qemuboot did not have IMGDEPLOYDIR variable set, which is required for building zephyr-kernel-test-all. The build was

From: Wojciech Zmuda <wojciech.zmuda@...> Implement do_flash_usb for boards supported by pyocd: MACHINE=xxx bitbake yyy -c flash_usb Pyocd support abundance of boards, however for now

From: Wojciech Zmuda <wojciech.zmuda@...> The board is based on Nordic nRF52832 Cortex-M4 chip. The support depends on Nordic HAL. It has been verified with zephyr-philosophers and

From: Wojciech Zmuda <wojciech.zmuda@...> Add include for Cortex-M4 tunes and nRF52832. The nRF config appends 'nordic' to MACHINEOVERRIDES, so the kernel recipe can include Nordic HAL when

From: Wojciech Zmuda <wojciech.zmuda@...> HAL for Nordic chipsets is one of Zephyr subprojects. It is downloaded by default by west. Clone the HAL repository so it can be used for building

From: Wojciech Zmuda <wojciech.zmuda@...> Hello, v2 -> v3: - fix accidentally broken QEMU builds. The build failed when do_deploy looked for .hex files that were generated for physical