From: Sascha Hauer <s.hauer@pengutronix.de>
To: Nur Hussein <hussein@unixcat.org>
Cc: barebox@lists.infradead.org
Subject: Re: Building and booting Barebox on Pandaboard
Date: Mon, 31 Mar 2014 17:09:20 +0200 [thread overview]
Message-ID: <20140331150920.GP17250@pengutronix.de> (raw)
In-Reply-To: <20140331130418.GA3113@radagast>
Hi,
On Mon, Mar 31, 2014 at 09:04:18PM +0800, Nur Hussein wrote:
> Dear all,
>
> I am using barebox-2014.03.0 to try to boot on a Pandaboard ES. I have followed the instructions in the docs:
>
> http://wiki.barebox.org/doku.php?id=boards:omap
>
> I could not however find a barebox.bin.ift file in the output, so I guessed and went with the barebox-flash-image linked file and named it MLO.
Yes, right. barebox-flash-image is the correct file to use. I updated
this in the wiki.
>
> It did not work. The Pandaboard ES did not boot.
Due to updates the panda_*defconfig configs currently do not build for
the panda board. Please either manually call a make menuconfig and set
the config back to panda:
System Type --->
OMAP Features --->
Select OMAP board (Texas Instrument's Panda Board) --->
Or apply the patch I just sent to the list:
ARM: Panda: Fix board selection in panda defconfig files
I'm not 100% sure the ES variant is supported. What was the difference
between the ES and the regular board again? Does the ES have a omap4460
whereas the regular board has a omap4430? If yes then the ES should be
supported.
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
next prev parent reply other threads:[~2014-03-31 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 13:04 Nur Hussein
2014-03-31 15:09 ` Sascha Hauer [this message]
2014-03-31 15:14 ` Nur Hussein
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=20140331150920.GP17250@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=hussein@unixcat.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