From: Wang Jian <lark@linux.net.cn>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Suggestion on flash init
Date: Tue, 03 Jan 2006 23:34:51 +0800 [thread overview]
Message-ID: <20060103232431.EB1F.LARK@linux.net.cn> (raw)
In-Reply-To: <20060103140842.42E073540BC@atlas.denx.de>
Hi Wolfgang Denk,
On Tue, 03 Jan 2006 15:08:42 +0100, Wolfgang Denk <wd@denx.de> wrote:
> In message <20060103205317.0711.LARK@linux.net.cn> you wrote:
> >
> > In my situation, S29AL016M works in x8 mode, which has different command
> > sequence from in x16 mode.
>
> If you look closer it is not so different at all.
>
> > x16 mode sector erase
> > addr[0x555] = 0xAA;
> > addr[0x2AA] = 0x55;
> > addr[0x555] = 0x80;
> > addr[0x555] = 0xAA;
> > addr[0x2AA] = 0x55;
> > addr[0x000] = 0x30;
> ...
> > x8 mode sector erase
> > addr[0xAAA] = 0xAA;
> > addr[0x555] = 0x55;
> > addr[0xAAA] = 0x80;
> > addr[0xAAA] = 0xAA;
> > addr[0x555] = 0x55;
> > addr[0x000] = 0x30;
>
> 0x555 = 0xAAA >> 1
> 0x2AA = 0x555 >> 1
>
> > I have little knowledge about other flash chips, so it is not easy for
> > me to write clean patch for cfi_flash.c, although I want to.
>
> The code is actually the very same, just taking into account the
> different addressing mode.
>
I am not sure if other kind of AMD flash chips use such x8/x16 command
sequence. I am afraid that I will fix one thing and break other things.
--
lark
next prev parent reply other threads:[~2006-01-03 15:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-25 4:33 [U-Boot-Users] Suggestion on flash init Wang Jian
2005-12-25 10:19 ` Wolfgang Denk
2005-12-25 12:02 ` Wang Jian
2005-12-25 16:34 ` Wolfgang Denk
2005-12-26 1:49 ` Wang Jian
2006-01-03 13:16 ` Wang Jian
2006-01-03 14:08 ` Wolfgang Denk
2006-01-03 15:34 ` Wang Jian [this message]
2006-01-03 15:44 ` Wolfgang Denk
2006-01-04 22:31 ` Tolunay Orkun
2006-01-04 23:51 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2006-01-05 16:20 Nuno João (Ext_NBS)
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=20060103232431.EB1F.LARK@linux.net.cn \
--to=lark@linux.net.cn \
--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