From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] SPI flash protection
Date: Sun, 30 Jan 2011 10:36:17 +0100 [thread overview]
Message-ID: <4D453111.50107@free.fr> (raw)
In-Reply-To: <20110129170048.GE20942@kw.sim.vm.gnt>
Hi Simon :)
Le 29/01/2011 18:00, Simon Guinot a ?crit :
> Hi,
>
> I am looking to add U-Boot support for the LaCie Network Space v2 board.
>
> The SoC is a Kirkwood 88F6281_A0 and the boot device is a Macronix SPI
> flash (MX25L4005A). My problem is that the embedded stock U-Boot (1.1.4
> version patched by Marvell and LaCie) enable write protection for the
> SPI flash. Then, after an U-Boot update, turn off this protection is
> needed to allow saving U-Boot environment.
>
> It is not clear for me how to proceed. Disable the write protection from
> the board setup code could be an idea but a problem is that the SPI flash
> API don't export any helpful method...
> Maybe I should add one ?
>
> An another idea is disabling the write protection anyway while
> initializing the flash (from the low level macronix driver). It is quite
> straightforward but I don't know if a flash driver is allowed to do
> that. After all, a flash could be protected for some good reasons.
>
> My last idea is doing nothing and let an another piece of software
> handle the problem...
>
> Thanks in advance for advices.
My personal take: let users of the board do their own mistakes and thus,
do not protect the Flash, *except* for U-Boot itself.
So, if SPI Flash protection is possible on block or sector levels,
protect the blocks/sectors where U-Boot is located, including the
environment.
Saveenv should unprotect and re-protect the environment sector/block.
As for the kernel and rootfs... You can either leave them unprotected or
protected.
> Simon
>
> PS: some pointers about this project:
>
> git : http://git.lacie-nas.org/u-boot-lacie.git (branch netspace_v2)
You should keep this branch based on u-boot/master generally, and on
u-boot-arm/master right now because it has the most recent ARM commits.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2011-01-30 9:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-29 17:00 [U-Boot] SPI flash protection Simon Guinot
2011-01-30 9:36 ` Albert ARIBAUD [this message]
2011-01-30 14:56 ` Simon Guinot
2011-01-30 17:19 ` Albert ARIBAUD
2011-01-31 0:31 ` Simon Guinot
2011-01-31 6:52 ` Albert ARIBAUD
2011-01-31 7:17 ` Reinhard Meyer
2011-02-01 9:09 ` Simon Guinot
2011-02-01 12:26 ` Albert ARIBAUD
2011-02-15 8:42 ` Mike Frysinger
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=4D453111.50107@free.fr \
--to=albert.aribaud@free.fr \
--cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.