suddenly, i can't boot barebox on my beagle xM anymore [ISOLATED]

[Robert P. J. Day]

On Mon, 3 Dec 2012, Jan Lübbe wrote:

> On Mon, 2012-12-03 at 03:31 -0500, Robert P. J. Day wrote:
> > *sigh* ... i *think* i figured out what's happening.  in order to
> > play with barebox on my xM, until recently, i'd done nothing more than
> > create a single FAT partition on a micro SD card, put MLO and
> > barebox.bin on it, put it in my xM, and let it boot.  until that OMAP
> > merge, it worked fine.
> >
> >   as i read it, the new default environment for the xM *requires* a
> > second (ext3) partition or the boot process simply hangs, am i reading
> > that right?  if that's true, how can i adjust that so i can once again
> > just boot to barebox without having a kernel and root fs created yet?
>
> Only the kernel uses the second partition for its rootfs, barebox should
> get to the prompt where you can interrupt autoboot anyway.
>
> So figuring out the exact commit would be useful. The bisection should
> take only a few steps. Sascha build-checks every revision, so all the
> bisection steps should build fine.

  here's a copy-and-paste from one of my other sessions, where i build
MLO/barebox.bin using two consecutive commits:

===== start =====

barebox 2012.10.0-00286-g36969d3 #6 Sun Dec 2 05:31:40 EST 2012


Board: Texas Instrument's Beagle
I2C probe
i2c-omap i2c-omap0: bus 0 rev4.0 at 100 kHz
ehci ehci0: USB EHCI 1.00
NAND type unknown: ff,ff
No NAND device found (-19)!
omap-hsmmc omap-hsmmc0: registered as omap-hsmmc0
mci mci0: registered disk0
malloc space: 0x80c00000 -> 0x80ffffff (size  4 MB)
stack space:  0x80bf8000 -> 0x80c00000 (size 32 kB)
Open /dev/env0 No such file or directory
no valid environment found on /dev/env0. Using default environment
running /env/bin/init...

Hit any key to stop autoboot:  1
dhcp failed: Network is down
dhcp: Network is down
do_tftpb: /.tftp_tmp_path/zImage- -> /image
could not open /.tftp_tmp_path/zImage-: Network is down

barebox at Texas Instrument's Beagle:/

barebox 2012.10.0-00287-g5f2074b #7 Sun Dec 2 05:33:23 EST 2012


Board: Texas Instrument's Beagle
NAND type unknown: ff,ff
No NAND device found (-19)!
omap-hsmmc omap-hsmmc0: registered as omap-hsmmc0
mci mci0: registered disk0
malloc space: 0x87bfff10 -> 0x87ffff0f (size  4 MB)
stack space:  0x4020f000 -> 0x4020fc00 (size  3 kB)
booting from MMC1

===== end =====

  as you can see, commit 36969d3 has the old behaviour (allowing
booting), while the next commit 5f2074b which introduces the new
beagle environment causes the boot to hang at "booting from MMC1".

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================