Re: Yocto migration meta-barebox -> walnascar

[Konstantin Kletschke <konstantin.kletschke@inside-m2m.de>]

On Tue, Jan 06, 2026 at 10:52:53AM +0100, Marco Felsch wrote:

> Which barebox version do you use?

It should be 2025.02.0.
I switched to walnascar and this should be the part used:
https://git.yoctoproject.org/poky/tree/meta/recipes-bsp/barebox?h=walnascar

> Ahmad added the support for a single barebox binary:
>  - https://lore.barebox.org/barebox/20250422052635.3423961-1-a.fatoum@pengutronix.de/
> 
> IIRC the purpose of the patchset was exactly to fulfill an easier Yocto
> integration since the beaglebone is one of the oe-core real test hw.

That's is very interesting.
What I did not get, yet:
So we can keep our partition scheme, the CPUs bootloader is searching
hardcoded for partition table -> first vfat -> MLO.
Then barebox-am33xx-beaglebone.img is put there as MLO?

> Since the single image approach targets only the SD/MMC boot, the
> standalone MLO image should be still possible.

 Can this be switched on/off somewere in the yocto framework so the old
 MLO/barebox.bin pair is genereated?

Regards
Konstantin