From: "Tim Sander" <tim.sander@hbm.com>
To: Teresa Gamez <T.Gamez@phytec.de>
Cc: barebox@lists.infradead.org
Subject: Re: RFC: arm pcm043 1315.6 IM950 timing (Numonyx Axcell Errata)
Date: Tue, 23 Aug 2011 16:40:34 +0200 [thread overview]
Message-ID: <201108231640.35115.tim.sander@hbm.com> (raw)
In-Reply-To: <1314105745.3389.123.camel@lws-gamez>
Hi Teresa
> I'm right now working on updating the pcm043 barebox to work with
> new hardware revisions. Including updates for NOR Flash support.
These are good news.
> I have also made a patch quite similar to yours. This problem seems
> to occur only with NOR Flashes having a date code around 39/2010 and
> earlier. It took me some time to find a module which does have this
> problem (I just got it today and have not checked it yet).
> On newer NOR Flashes I could not see any affect/advantage with this
> workaround. I'll test your patch with this module.
It seems as if we got such a version. I can write partitions with tftp via
network but i can't do a saveenv even with my patch. So i guess its not
working as i hoped for. I guess since saveenv does an unprotect copy protect
itself it triggers the errata for these nor chips:
cfi_protect: unprotect 0xa0040000 (size 131072)
Flash buffer write error at address a0040000
Command Sequence Error.
cfi_protect: protect 0xa0040000 (size 131072)
> But adding this workaround will not be enough to support newer NOR flashes.
> The CS values need to be changed and support for u32 commands have to
> be added to cfi_flash. I'll send patches the next days.
As for the u32 support, isn't everything in place with:
CONFIG_DRIVER_CFI_BANK_WIDTH_4=y
Do you have some CS values for me to test with?
I've got the impression that writes on the 64Mb nor pcm043 are much faster
than the old hw revisions with 32Mb nor.
Best regards
Tim
Hottinger Baldwin Messtechnik GmbH, Im Tiefen See 45, 64293 Darmstadt, Germany | www.hbm.com
Registered as GmbH (German limited liability corporation) in the commercial register at the local court of Darmstadt, HRB 1147
Company domiciled in Darmstadt | CEO: Andreas Huellhorst | Chairman of the board: James Charles Webster
Als Gesellschaft mit beschraenkter Haftung eingetragen im Handelsregister des Amtsgerichts Darmstadt unter HRB 1147
Sitz der Gesellschaft: Darmstadt | Geschaeftsfuehrung: Andreas Huellhorst | Aufsichtsratsvorsitzender: James Charles Webster
The information in this email is confidential. It is intended solely for the addressee. If you are not the intended recipient, please let me know and delete this email.
Die in dieser E-Mail enthaltene Information ist vertraulich und lediglich für den Empfaenger bestimmt. Sollten Sie nicht der eigentliche Empfaenger sein, informieren Sie mich bitte kurz und loeschen diese E-Mail.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-08-23 14:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 12:21 Tim Sander
2011-08-23 12:53 ` Sascha Hauer
2011-08-23 13:22 ` Teresa Gamez
2011-08-23 14:40 ` Tim Sander [this message]
2011-08-24 8:54 ` Teresa Gamez
2011-08-24 10:07 ` Tim Sander
2011-08-24 12:25 ` Teresa Gamez
[not found] ` <201108231701.21401.tim.sander@hbm.com>
[not found] ` <1314270042.3389.608.camel@lws-gamez>
2011-08-25 14:57 ` Patch test results was (Re: RFC: arm pcm043 1315.6 IM950 timing (Numonyx Axcell Errata)) Tim Sander
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=201108231640.35115.tim.sander@hbm.com \
--to=tim.sander@hbm.com \
--cc=T.Gamez@phytec.de \
--cc=barebox@lists.infradead.org \
/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