From: Sascha Hauer <s.hauer@pengutronix.de>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: NOR flash writing
Date: Tue, 29 Jul 2014 08:21:42 +0200 [thread overview]
Message-ID: <20140729062142.GC23235@pengutronix.de> (raw)
In-Reply-To: <20140728182814.d80c510749ed1851aaddafb8@gmail.com>
On Mon, Jul 28, 2014 at 06:28:14PM +0400, Antony Pavlov wrote:
> Hi All!
>
> I have barebox running on a board with SPI flash chip.
> I can write to the SPI flash chip using /dev/nor0 interface.
> Before writing data to the /dev/nor0 device I have to erase it explicitly with 'erase /dev/nor0' command.
>
> How I can write to /dev/nor0 in a more transparent way. E.g. if I want to update only several bytes
> on /dev/nor0 then I use 'mw -d /dev/nor0 ...' command and barebox automatically reads appropriate
> flash sector into RAM, modify it, erase NOR flash device sector and write new sector content into NOR flash device.
There's no convenient way for this, you have to do it manually:
- read a block to a file using memcpy
- modify it using mw
- erase flash block
- copy back using memcpy
I can't think up a good API to combine this into a single command.
I mean for simple modifications some more intelligent read/modify/write
command would work, but normally if you have more than one modification
to do then you don't want to erase your flash with each modification.
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:[~2014-07-29 6:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 14:28 Antony Pavlov
2014-07-29 6:21 ` 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=20140729062142.GC23235@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=antonynpavlov@gmail.com \
--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