mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: suddenly, i can't boot barebox on my beagle xM anymore
Date: Sat, 1 Dec 2012 17:36:29 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1212011733350.24134@oneiric> (raw)
In-Reply-To: <alpine.DEB.2.02.1212011607040.13954@oneiric>

On Sat, 1 Dec 2012, Robert P. J. Day wrote:

>
>   a bit embarrassed but, all of a sudden, what used to work just fine
> in terms of building and booting barebox on my beagleboard xM (rev C)
> doesn't work anymore.
>
>   not that long ago, i documented how easy this was here:
>
> http://www.crashcourse.ca/wiki/index.php/BeagleBoard-xM#Barebox_for_the_xM
>
> absolutely nothing out of the ordinary as i remember it.  so, when
> this worked, the boot looked like what you see here:
>
> http://www.crashcourse.ca/wiki/index.php/BeagleBoard-xM#Booting_to_Barebox_on_your_xM_--_it_actually_works
>
> now, the boot process produces:
>
> barebox 2012.11.0-00305-g159109f #1 Sat Dec 1 15:51:00 EST 2012
>
>
> Board: Texas Instrument's Beagle
> NAND type unknown: ff,ff
> No NAND device found (-19)!
> gpmc_nand gpmc_nand0: probe failed: error 6
> 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
>
> ... and hangs, suggesting that the MLO file is fine, but it's
> barebox.bin that simply fails.
>
>   am i missing something painfully obvious?

  for completeness (and what i of course should have done earlier if i
hadn't been drinking chardonnay all afternoon) was test with an
earlier version of barebox.  so i checked out tag v2012.10.0, and i'm
back to a booting version of barebox on my xM, represented by what you
see here:

http://www.crashcourse.ca/wiki/index.php/BeagleBoard-xM#Booting_to_Barebox_on_your_xM_--_it_actually_works

  will investigate further ...

rday

-- 

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

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

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2012-12-01 22:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-01 21:18 Robert P. J. Day
2012-12-01 22:36 ` Robert P. J. Day [this message]
2012-12-02  9:24   ` suddenly, i can't boot barebox on my beagle xM anymore [ISOLATED] Robert P. J. Day
2012-12-03  8:19     ` Jan Lübbe
2012-12-03  8:31       ` Robert P. J. Day
2012-12-03  8:44         ` Jan Lübbe
2012-12-03  8:48           ` Robert P. J. Day
2012-12-03  8:55           ` Robert P. J. Day
2012-12-03  9:46 ` suddenly, i can't boot barebox on my beagle xM anymore Sascha Hauer
2012-12-03  9:50   ` Robert P. J. Day
2012-12-03  9:56     ` Sascha Hauer
2012-12-03 10:01       ` Robert P. J. Day
2012-12-03 10:04         ` Sascha Hauer
2012-12-03 10:07           ` Robert P. J. Day
2012-12-03 12:02           ` Robert P. J. Day

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.02.1212011733350.24134@oneiric \
    --to=rpjday@crashcourse.ca \
    --cc=barebox@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox