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 [ISOLATED]
Date: Sun, 2 Dec 2012 04:24:22 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.02.1212020418020.6898@oneiric> (raw)
In-Reply-To: <alpine.DEB.2.02.1212011733350.24134@oneiric>
i've isolated the commit that introduces the apparent booting
problem on my xM:
$ git show 154496f
commit 154496f736db54123c3f6daaba18809fab54ed9b
Merge: 05d251f bd6d12b
Author: Sascha Hauer <s.hauer@pengutronix.de>
Date: Fri Nov 16 14:02:49 2012 +0100
Merge branch 'for-next/omap'
$
if i build MLO and barebox.bin with that commit, booting produces:
barebox 2012.11.0-00237-g154496f #1 Sat Dec 1 18:43:27 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
87ffff0f (size 4 MB)
stack space: 0x4020f000 -> 0x4020fc00 (size 3 kB)
booting from MMC1
... and hangs ...
if, however, i build from the parent commit 05d251f, then i'm back
to a full boot to barebox:
barebox 2012.11.0-00230-g05d251f #2 Sun Dec 2 04:04:37 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)!
gpmc_nand gpmc_nand0: probe failed: No such device or address
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: 0
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@Texas Instrument's Beagle:/
so something in that omap merge is causing this.
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
next prev parent reply other threads:[~2012-12-02 9:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-01 21:18 suddenly, i can't boot barebox on my beagle xM anymore Robert P. J. Day
2012-12-01 22:36 ` Robert P. J. Day
2012-12-02 9:24 ` Robert P. J. Day [this message]
2012-12-03 8:19 ` suddenly, i can't boot barebox on my beagle xM anymore [ISOLATED] 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.1212020418020.6898@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