public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] BDI3000 - Unprotect flash sectors
Date: Fri, 11 Jan 2013 10:31:19 +0100	[thread overview]
Message-ID: <50EFDBE7.1010605@denx.de> (raw)
In-Reply-To: <E1C9442006A9AE48A7A4B85E0D01C4D45ACA78@stwexdb.stww2k.local>

Hi Georg,

On 01/11/2013 08:41 AM, Waibel Georg wrote:
> 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
> 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

Yes, the BDI doesn't support the unlocking of the Advanced Locking Bits
(PPB) of these Spansion (and other manufacturers) type chips. You need
to manually unlock the sectors in the telnet BDI session by writing the
unlocking sequence to the sector(s). Or use U-Boot to do this (if possible).

Please note that some patches to better support this PPB locking have
been applied to mainline just now. And I also have some patches to
support this PPB (un)-locking in Linux a short while ago which are still
pending:

http://lists.infradead.org/pipermail/linux-mtd/2012-December/045295.html

Hope this helps.

Thanks,
Stefan

  reply	other threads:[~2013-01-11  9:31 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 [this message]
2013-01-14  8:03   ` Waibel Georg
2013-01-11 13:24 ` Marek Vasut
2013-01-12  4:04 ` Sinan Akman

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=50EFDBE7.1010605@denx.de \
    --to=sr@denx.de \
    --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