From: Sinan Akman <sinan@writeme.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] BDI3000 - Unprotect flash sectors
Date: Fri, 11 Jan 2013 23:04:04 -0500 [thread overview]
Message-ID: <50F0E0B4.4000308@writeme.com> (raw)
In-Reply-To: <E1C9442006A9AE48A7A4B85E0D01C4D45ACA78@stwexdb.stww2k.local>
On 01/11/2013 02:41 AM, Waibel Georg wrote:
> Hello,
>
> i'm not sure if this is the right place for this question...however, here it is:
>
> i'm using a BDI3000 to program uboot to the flash (Spansion S29GL512P) on a MPC5200B base board. Erasing / Programming works fine as long as the flash sectors are not protected (via PPB bit). On a protected sector the erase command fails (what makes sense). I thought I can use the unlock command to unprotect the sectors, but this command seems not to work:
>> unlock 0xfff00000 1000
Hi Georg, do you get the same error if you create an
ERASE list and have UNLOCK added as the mode for those
sectors that need to be unlocked ? Issue then ERASE or
UNLOCK without any parameter in the telnet session and
see if that makes any difference. Also, make sure that
address 0xfff00000 is the correct sector address.
Failing that, please try using the CFI interface of
your flash. Check in your flash memory data sheet for
all the CFI commands. Try to unlock a sector and then
read back the status register to see what the reported
error is. Use MD and MM commands to issue the CFI
commands to your flash.
Hope this helps
-- sinan
> Unlocking flash at 0xfff00000
> # Invalid parameter for flash programming
>
> Any ideas what I'm doing wrong?
>
> Flash configuration:
> [FLASH]
> CHIPTYPE MIRRORX16
> CHIPSIZE 0x04000000
> BUSWIDTH 16
> WORKSPACE 0x00000000
>
> Regards
> Georg Waibel
>
prev parent reply other threads:[~2013-01-12 4:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 7:41 [U-Boot] BDI3000 - Unprotect flash sectors Waibel Georg
2013-01-11 9:31 ` Stefan Roese
2013-01-14 8:03 ` Waibel Georg
2013-01-11 13:24 ` Marek Vasut
2013-01-12 4:04 ` Sinan Akman [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=50F0E0B4.4000308@writeme.com \
--to=sinan@writeme.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