Re: suddenly, i can't boot barebox on my beagle xM anymore

[Sascha Hauer <s.hauer@pengutronix.de>]

Hi Robert,


On Sat, Dec 01, 2012 at 04:18:08PM -0500, 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.

I just rechecked, current master works fine for me on my beagle (no xM
though). Just a guess, have you used the barebox-flash-image link
instead of barebox.bin? Since the image is compressed now it becomes
important to use the link (which points to the compressed image).

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

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