All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] cfi: Problem with Intel Strata 28F320 flash
Date: Tue, 08 Mar 2011 14:08:26 +0100	[thread overview]
Message-ID: <4D762A4A.8070002@denx.de> (raw)

Hello,

as I am actual trying to get the keymile boards in sync with actual
mainline u-boot, I faced the following Problem with an Intel Strata
Flash on the mgcoge (mpc8247 based board):

I couldn;t unprotect/erase/write/protect some (not all!) Flash sectors.

For Example, I could do this without errors on the sectors where
u-boot sits (First three sectors), but not with the environment (next
two sectors)!

After some debugging, I found out, that, if I revert commit

commit 54652991caedc39b2ec2e5b49e750669bfcd1e2e
Author: Philippe De Muyter <phdm@macqel.be>
Date:   Tue Aug 17 18:40:25 2010 +0200

    Work around bug in Numonyx P33/P30 256-Mbit 65nm flash chips.

    I have "ported" U-boot to a in house made board with Numonyx Axcell P33/P30
    256-Mbit 65nm flash chips.

    After some time :( searching for bugs in our board or soft, we have
    discovered that those chips have a small but annoying bug, documented in
    "Numonyx Axcell P33/P30 256-Mbit Specification Update"
[...]

It works again fine, and without problems ... did somebody faced
similiar issues with the cfi driver? Some Ideas?

bye,
Heiko
-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

             reply	other threads:[~2011-03-08 13:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-08 13:08 Heiko Schocher [this message]
2011-03-08 14:26 ` [U-Boot] cfi: Problem with Intel Strata 28F320 flash Philippe De Muyter
2011-03-09  6:41   ` Heiko Schocher
2011-03-09 13:21     ` Detlev Zundel
2012-07-27 14:11       ` Gerlando Falauto
2012-07-30 11:07         ` Heiko Schocher
2012-07-30 11:11           ` Stefan Roese
2012-08-03  8:01           ` Stefan Roese

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=4D762A4A.8070002@denx.de \
    --to=hs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.