From: Sascha Hauer <s.hauer@pengutronix.de>
To: Jerry Kirk <jkirk865@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: Write Protect Error re-flashing /dev/nor0.barebox
Date: Wed, 26 Sep 2012 23:45:15 +0200 [thread overview]
Message-ID: <20120926214515.GT1322@pengutronix.de> (raw)
In-Reply-To: <loom.20120926T210129-125@post.gmane.org>
Hi Jerry,
On Wed, Sep 26, 2012 at 07:07:32PM +0000, Jerry Kirk wrote:
> We are updating from 2012-03 to 2012-09 and after flashing our SOM
> (Phytec PCM043 - imx35) we starting getting this error:
>
> barebox:/ erase /dev/nor0.barebox
>
> erase: Operation not permitted
>
> It worked the first time, when overwriting the 2012-03 image and booted, etc.
> We have tried a few intermediate Barebox versions and think it worked up to 2012-
> 07.
>
> Any ideas what we now need to do to be able to overwrite Barebox?
I think you are the victim of a bug fix ;)
You probably registered the partition readonly. (see the 'ro'
flag in the mtdparts variable). Since some releases barebox
actually honors this flag:
commit a4fde70067b6113fd9dc7a4295ebd3f55b756db6
Author: Jan Luebbe <jlu@pengutronix.de>
Date: Mon Jun 25 14:03:27 2012 +0200
fs/devfs.c: disallow write and erase if a partition is read-only
Signed-off-by: Jan Luebbe <jlu@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
--
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:[~2012-09-26 21:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 19:07 Jerry Kirk
2012-09-26 19:10 ` Jean-Christophe PLAGNIOL-VILLARD
2012-09-26 19:24 ` Jerry Kirk
2012-09-26 21:45 ` Sascha Hauer [this message]
2012-09-28 11:51 ` Jerry Kirk
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=20120926214515.GT1322@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=jkirk865@gmail.com \
/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