From: llandre <r&d2@dave-tech.it>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Setting strataflash lock bit accidentally
Date: Fri, 21 Jul 2006 12:19:48 +0200 [thread overview]
Message-ID: <44C0AA44.5050400@dave-tech.it> (raw)
Let's assume that, because a software bug, an application has
accidentally set the lock bit of the flash sector used to store the
U-Boot environment. In this case, when trying to store a new environment
with the saveenv command, U-Boot would not be able to complete the
operation. Is it enough to define CFG_FLASH_PROTECTION in order to
handle this situation and to allow U-Boot to unlock the sector (same
thing would happen in case the locked sectors fall in the memrory area
devoted to store kernels or ramsisks)? If no, how do you suggest to
manage this situation?
TIA,
llandre
DAVE Electronics System House - R&D Department
web: http://www.dave-tech.it
email: r&d2 at dave-tech.it
next reply other threads:[~2006-07-21 10:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-21 10:19 llandre [this message]
2006-07-21 11:02 ` [U-Boot-Users] Setting strataflash lock bit accidentally Wolfgang Denk
2006-07-21 11:22 ` llandre
2006-07-21 11:45 ` Wolfgang Denk
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=44C0AA44.5050400@dave-tech.it \
--to=r&d2@dave-tech.it \
--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