From: Tolunay Orkun <listmember@orkun.us>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Erase error on dual P30 (CFI) flash chips
Date: Fri, 15 Jun 2007 09:15:45 -0500 [thread overview]
Message-ID: <46729F11.4070204@orkun.us> (raw)
In-Reply-To: <200706151548.47448.sr@denx.de>
Stefan Roese wrote:
> On Friday 15 June 2007, w.wegner at astro-kom.de wrote:
>
>>> Flash erase error at address ffd80000
>>> Block Erase Error.
>>> Block locked.
>>> done
>>> Erased 1 sectors
>>>
>> if I am not mistaken, you have to also set:
>>
>> #define CFG_FLASH_PROTECTION 1
>>
>
> And you will have to set the environment variable "unlock" to "yes". This will
> unlock all non U-Boot special sectors by default upon powerup.
>
> => setenv unlock yes
> => saveenv
>
>
Alternative to setting "unlock" environment variable you will need to
issue "protect off" for any locked sector that should be unlocked. This
may be handy if you have other stuff on the flash which you would like
to keep protected. One way to do this is via a u-boot script that is
executed as part of boot. I think Intel chips (used to) preserve their
last lock status and recent Spansion chips start all locked upon boot so
you might not need unlock environment variable for your Intel part as
well once you have the proper sectors unlocked (for example jffs2 areas)
Tolunay
prev parent reply other threads:[~2007-06-15 14:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 11:55 [U-Boot-Users] Erase error on dual P30 (CFI) flash chips Floris Lambrechts
2007-06-15 12:01 ` w.wegner at astro-kom.de
2007-06-15 13:48 ` Stefan Roese
2007-06-15 14:15 ` Tolunay Orkun [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=46729F11.4070204@orkun.us \
--to=listmember@orkun.us \
--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