Dear barebox people, Happy New Year everybody :-) I used up until scarthgap https://github.com/menschel-d/meta-barebox
In our meta layer we have config in distro conf like this: ABREBOX_CONFIG:beaglebone-yocto = "omap_defconfig" BAREBOX_CONFIG:pn-barebox-pbl:beaglebone-yocto = "am335x_mlo_defconfig" BAREBOX_IMAGE_SRC:beaglebone-yocto = "images/barebox-am33xx-beaglebone.img" BAREBOX_IMAGE_SRC:pn-barebox-pbl:beaglebone-yocto = "images/barebox-am33xx-beaglebone-mlo.img" RDEPENDS:barebox:beaglebone-yocto += "barebox-pbl" COMPATIBLE_MACHINE:pn-barebox:beaglebone-yocto = "beaglebone-yocto" COMPATIBLE_MACHINE:pn-barebox-pbl:beaglebone-yocto = "beaglebone-yocto" PREFERRED_PROVIDER_virtual/bootloader = "barebox" And a append recipe mainly with patches creating our custom configuration. Now I learned, barebox went into openembedded-core, this is great news! I ditched the meta-barebox, tried my best, needed to remove alle configs regarding "-pbl" and compiled: ERROR: Nothing RPROVIDES 'barebox-pbl' (but /home/konsti/Melitta/scarthgap/meta/recipes-bsp/barebox/barebox.bb RDEPENDS on or otherwise requires it) Now I get several ~580kB img files in the deployment images directory, "ours" seems to be barebox-am33xx-beaglebone.img. File size is plausible for the ex barebox.bin and strings suggest our insidem2m stuff to boot/tftp/nfs landed up in it. Where is the MLO part? Is barebox-am33xx-beaglebone.img the 1:1 barebox.bin equivalent? We are used to create a partition table, first partition is vfat type 0x0c, MLO and barebox.bin are put there, works. Kind Regards Konstantin Kletschke -- INSIDE M2M GmbH Konstantin Kletschke Berenbosteler Straße 76 B 30823 Garbsen Telefon: +49 (0) 5137 90950136 Mobil: +49 (0) 151 15256238 Fax: +49 (0) 5137 9095010 [email protected] http://www.inside-m2m.de Geschäftsführung: Michael Emmert, Derek Uhlig HRB: 111204, AG Hannover
