From: "Allen Kennedy Jr." <allen@kennedystuff.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: [SOLVED] how to copy barebox to flash?
Date: Wed, 25 Sep 2013 16:46:58 -0500 [thread overview]
Message-ID: <CAO-21LP+01=O0KhkdgxNQ7PXKZTyzpWBCaYZQeTvQnGvZi3ESg@mail.gmail.com> (raw)
This was exactly what I was looking for!
thanks
On Wed, Sep 25, 2013 at 2:55 PM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> Hi Allen,
>
> On Wed, Sep 25, 2013 at 11:13:47AM -0500, Allen Kennedy Jr. wrote:
>> All,
>> How do I copy barebox to flash?
>> I have a flash device setup:
>> `---- imx_nand
>> `---- nand0
>> `---- 0x00000000-0x0fffffff: /dev/nand0
>> `---- 0x00000000-0x0001ffff: /dev/bootstrapper
>> `---- 0x00020000-0x0005ffff: /dev/barebox
>> `---- 0x00060000-0x0009ffff: /dev/env_raw
>> `---- 0x00100000-0x005fffff: /dev/kernel
>>
>> I used JTAG to load barebox into memory at 0xa0000000
>>
>> I just can't figure out how to copy it to flash... There is no DD command...
>> I tried this:
>> cp 0xa0000000 /dev/barebox 0x4000
>> got :
>> cp: target `0x4000' is not a directory
>
> What you're looking for is the memcpy command. It has options to copy
> memory to/from files. You need something like:
>
> memcpy -d /dev/barebox 0xa0000000 0 512k
>
> replace 512k with whatever filesize is appropriate.
>
> See 'help memcpy' or http://wiki.barebox.org/doku.php?id=commands:memcpy
> for more information.
>
>>
>> Seems barebox changed what 'cp' is from the old u-boot way.
>> and the nand command only does bad block handling...
>>
>> barebox-update seems to be a candidate, but the docs don't make sense
>> on how to use.
>
> Yes, that's the correct command, but it needs board support to be
> implemented. With the correct board support the update would go down to:
>
> barebox_update /mnt/tftp/barebox.bin
>
> (It needs a file though, you would have to generate this with memcpy if
> you want to use it together with a raw memory image.)
>
>> Also I was thinking something like md > /dev/nand, but the output of
>> MD is user readable.
>
> Unfortunately the barebox shell is not capable of doing output redirection.
>
> 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
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
reply other threads:[~2013-09-25 21:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAO-21LP+01=O0KhkdgxNQ7PXKZTyzpWBCaYZQeTvQnGvZi3ESg@mail.gmail.com' \
--to=allen@kennedystuff.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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