[Buildroot] [PATCH v4 0/7] Support building a second Barebox config (incl. BBB)

[Pieter Smith <pieter@boesman.nl>]

Hi Thomas,

On Thu, Apr 21, 2016 at 01:29:05PM +0200, Thomas Petazzoni wrote:
> Hello,
> 
> On Thu, 21 Apr 2016 12:55:12 +0200, Yegor Yefremov wrote:
> 
> > >> Have made basic tests, i.e. changing configuration for barebox and
> > >> barebox-2 and running make to see, if proper barebox was compiled.
> > >> Everything is working the way it was in v4 from this point of view.
> > >
> > > Thanks! Did you flash a bare SD card or the internal eMMC with boot.vfat and
> > > rootfs.ext4 as part of the tests?
> > 
> > If I copy your images (MLO, barebox.bin) directly to the FAT
> > partition, everything starts as expected. But I dd boot.vfat, the
> > system doesn't boot and shows only CCCCC, though I have no problems
> > mounting the first partition in Linux.
> > 
> > sudo dd if=/tmp/boot.vfat of=/dev/sdd1 bs=1M
> 
> So this means that the Barebox build is OK, and only the genimage part
> is causing problems. But this doesn't prevent from merging the barebox
> aspects of the series (patches 1 to 6), which are really the important
> part. The last patch is really more a defconfig proving that it works,
> I am not even sure that in practice we want to merge a defconfig for
> BeagleBone that is just different from beaglebone_defconfig in the fact
> that it uses Barebox instead of U-Boot. Peter?

I agree that the barebox aspects are more important. I would however like to
have the defconfig merged as the first example of how to apply this. It
provides a consistent set targeting a readily available board. With the help of
Yegor I have managed to work the kinks out of the defconfig. The patch has also
been reworked it based on Arnouts valuable input. So there is no need to delay
the series.

All that is left is the suggested BR2_TARGET_BAREBOX_BUILT_IMAGE_FILE ->
BR2_TARGET_BAREBOX_IMAGE_FILE rename and a final master rebase, then I can
post.

> Peter, I think you looked at using genimage on AM335x, what were your
> conclusion? On OMAP3, there were some very strict geometry restrictions
> in the romcode, but I don't remember if your conclusion is that they
> also apply to AM335x or not.

Flashing the boot.vfat separately seems to run afoul of such geometry
restrictions. Using genimage to generate a full sdcard.img however works well
on the BBB. I therefore did not spend more time on the issue because it works
now. Do you see any need to dig deeper, or can the patch be merged based on a
working sdcard.img?

> Thomas
> -- 
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com

- Pieter