From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Boulais, Marc-Andre" <maboulais@rheinmetall.ca>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: Generate MLO for phytec-phycore-omap4460
Date: Fri, 6 Feb 2015 14:29:20 +0100 [thread overview]
Message-ID: <20150206132920.GN12209@pengutronix.de> (raw)
In-Reply-To: <29A2697B0516A946B1023D5E798DFCF67BAB7263@mail-ying>
On Fri, Feb 06, 2015 at 12:56:31PM +0000, Boulais, Marc-Andre wrote:
> Good morning,
> I am currently trying to build the MLO for the omap4460 on a Phytec Phycore board. In order to build it, I do the following procedure, but I get this size error at the end:
>
> > make ARCH=arm CROSS_COMPILE=... phytec-phycore-omap4460-xload_defconfig
> > make
> ....
> LD barebox
> SYSMAP System.map
> OBJCOPY barebox.bin
> CHKSIZE barebox.bin
> barebox.bin size 53168 > of the maximum size 49152
> make: *** [barebox.bin] Error 1
>
> Curiously enough, the MLO is bigger than the 2nd stage barebox.bin I would generate with the config phytec-phycore-omap4460_defconfig.
> In the documentation (boards/omap.rst), there is mention of a "barebox.bin.ift" file that corresponds to the MLO. However I don't have this file...only barebox and barebox.bin.
> Is my build procedure correct ?
It's everything correct on your side, it's only that the config became
too big over time. So for now you have to disable either MMC or mtd
support in the config, depending on where you want to boot from.
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
prev parent reply other threads:[~2015-02-06 13:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 12:56 Boulais, Marc-Andre
2015-02-06 13:29 ` Sascha Hauer [this message]
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=20150206132920.GN12209@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=maboulais@rheinmetall.ca \
/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