From: Cliff Brake <cliff.brake@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Overwriting protected flash memory!!!
Date: Thu, 9 Dec 2004 15:27:59 -0500 [thread overview]
Message-ID: <f96d234e04120912273b1f0a2b@mail.gmail.com> (raw)
In-Reply-To: <20041209192215.CD773C146C@atlas.denx.de>
On Thu, 09 Dec 2004 20:22:10 +0100, Wolfgang Denk <wd@denx.de> wrote:
> No. Not even that. For most boards, the "protect" feature in U-Boot
> is only a flag that prevents certain commands from working on such
> "protected" flash areas. Only very few flash chips, and even fewer
> boards using these chips, actually use some kind of hardware
> protection.In most cases, just using a couple of "mm" or "mw"
> commands to enter the erase or program seqence is all what's needed
> to erase / corrupt "protected" sectors.
>
> The "protect" stuff is something that is intended to prevent
> accidential data loss by a istyped command etc. It cannot protect you
> from doing stupid things.
Thanks for the information -- I had assumed the protect command set
the lock bits (for Intel flash). Setting the CFG_FLASH_PROTECTION
option may cause the lock bits to be set in the flash (did not trace
through the code fully). But it is still very possible to corrupt
flash as writes to a range of address will clear the lock bit (as
Wolfgang pointed out).
--
=======================
Cliff Brake
http://bec-systems.com
next prev parent reply other threads:[~2004-12-09 20:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 17:51 [U-Boot-Users] Overwriting protected flash memory!!! Cabral, Kevin
2004-12-09 18:35 ` Wolfgang Denk
2004-12-09 19:00 ` Cliff Brake
2004-12-09 19:22 ` Wolfgang Denk
2004-12-09 20:27 ` Cliff Brake [this message]
2004-12-09 20:45 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2004-12-09 21:31 Cabral, Kevin
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=f96d234e04120912273b1f0a2b@mail.gmail.com \
--to=cliff.brake@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox