From: Philippe De Muyter <phdm@macqel.be>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCHv2 CFI flash]: Workaround for Numonyx Axcell?P33/P30 256-Mbit 65nm bug
Date: Tue, 10 Aug 2010 18:12:53 +0200 [thread overview]
Message-ID: <20100810161253.GA16134@frolo.macqel> (raw)
In-Reply-To: <201008101728.59679.sr@denx.de>
On Tue, Aug 10, 2010 at 05:28:59PM +0200, Stefan Roese wrote:
> Hi Philippe,
>
> one more thing:
>
> On Monday 09 August 2010 17:46:03 Philippe De Muyter wrote:
> > Here is the excerpt from the errata :
> >
> > Workaround: If the interval between 60h and its subsequent command
> > can be guaranteed within 20?s, Option I is recommended,
> > otherwise Option II (involves hardware) should be selected.
> > Option I: The table below lists the detail command sequences:
> > Command
> > Data bus Address bus Remarks
> > Sequence
> > 1 90h Block Address
> > Read Lock Status
> > 2 Read Block Address + 02h
> > (2)(3) (1)
> > 3 60h Block Address
> > (2)(3) (1) Lock/Unlock/RCR
> > Configuration 4 D0h/01h/03h Block Address
> > Notes:
> > (1) Block Address refers to RCR configuration data only when the 60h
> > command sequence is used to set RCR register combined with 03h
> > subsequent command.
> > (2) For the third and fourth command sequences, the Block Address must
> > be the same.
> > (3) The interval between 60h command and its subsequent D0h/01h/2Fh/03h
> > commands should be less than 20?s.
>
> Please add this workaround text from the errata to the commit text in your
> next patch version. This makes things easier - no need to search for the
> errata.
OK
Philippe
prev parent reply other threads:[~2010-08-10 16:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 11:57 [U-Boot] [PATCH CFI flash]: Workaround for Numonyx Axcell P33/P30 256-Mbit 65nm bug Philippe De Muyter
2010-06-23 12:48 ` Wolfgang Denk
2010-06-23 13:10 ` [U-Boot] [PATCHv2 " Philippe De Muyter
2010-08-06 23:11 ` Wolfgang Denk
2010-08-09 8:32 ` Joakim Tjernlund
2010-08-09 12:57 ` Philippe De Muyter
2010-08-09 15:48 ` Philippe De Muyter
2010-08-09 15:55 ` Joakim Tjernlund
2010-08-09 13:52 ` Stefan Roese
2010-08-09 15:46 ` Philippe De Muyter
2010-08-10 11:20 ` Stefan Roese
2010-08-10 13:31 ` Philippe De Muyter
2010-08-10 13:39 ` Stefan Roese
2010-08-10 15:28 ` Stefan Roese
2010-08-10 16:12 ` Philippe De Muyter [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=20100810161253.GA16134@frolo.macqel \
--to=phdm@macqel.be \
--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