From: Sascha Hauer <s.hauer@pengutronix.de>
To: John Parker <John.Parker@lucyautomation.co.uk>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: FW: Barebox on Karo TX25
Date: Wed, 27 Nov 2013 22:01:16 +0100 [thread overview]
Message-ID: <20131127210115.GZ24559@pengutronix.de> (raw)
In-Reply-To: <EAF1F21DA385DA4797F21C5DCAEF6BAC467D346765@AUTOSERVER1.auto.local>
On Wed, Nov 27, 2013 at 03:49:49PM +0000, John Parker wrote:
> Hi
>
> I have a barebox prompt running from RAM!!
>
> What next?
Setup a tftp server, edit /env/network/eth0 to your liking using
'edit /env/network/eth0', do a 'saveenv' to safe your settings.
Test your network with:
cp /mnt/tftp/barebox.bin /barebox.bin
If that works you can do:
erase /dev/nand0.barebox.bb
cp /barebox.bin /dev/nand0.barebox.bb
(Note: you have to use barebox-flash-image as generated by the
compilation, not the imx-image you generated for USB boot)
That should be it. After a reset your board should come up with barebox.
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:[~2013-11-27 21:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 11:28 John Parker
2013-11-27 12:56 ` [PATCH 1/2] ARM: imx: karo tx25: Add config file for imx-image Sascha Hauer
2013-11-27 12:56 ` [PATCH 2/2] scripts: imx-image: Add i.MX25 support Sascha Hauer
2013-11-27 14:49 ` [PATCH 1/2] ARM: imx: karo tx25: Add config file for imx-image John Parker
2013-11-27 13:02 ` FW: Barebox on Karo TX25 Sascha Hauer
2013-11-27 13:18 ` John Parker
2013-11-27 15:49 ` John Parker
2013-11-27 21:01 ` Sascha Hauer [this message]
2013-11-28 16:13 ` John Parker
2013-11-28 16:22 ` Baruch Siach
2013-11-29 8:16 ` John Parker
2013-11-29 9:46 ` Sascha Hauer
2013-11-29 10:27 ` John Parker
2013-11-29 10:41 ` John Parker
2013-12-02 9:13 ` John Parker
2013-12-03 9:26 ` Sascha Hauer
2013-12-03 19:01 ` Jean-Christophe PLAGNIOL-VILLARD
2013-12-05 15:24 ` Sascha Hauer
2013-12-05 16:48 ` Jean-Christophe PLAGNIOL-VILLARD
2013-12-19 14:14 ` John Parker
2013-11-27 19:45 ` John Parker
2013-11-27 20:15 ` Eric Bénard
2013-11-27 20:54 ` Sascha Hauer
2013-11-28 4:16 ` Alexander Aring
2013-11-28 7:20 ` Sascha Hauer
2013-11-28 7:37 ` Alexander Aring
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=20131127210115.GZ24559@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=John.Parker@lucyautomation.co.uk \
--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