From: Aaron Williams <Aaron.Williams@caviumnetworks.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] NAND Re: mtdparts fails with NAND >= 4GB - Second try
Date: Tue, 8 Feb 2011 17:56:14 -0800 [thread overview]
Message-ID: <201102081756.14299.Aaron.Williams@caviumnetworks.com> (raw)
In-Reply-To: <201102081511.55001.Aaron.Williams@caviumnetworks.com>
On Tuesday, February 08, 2011 03:11:54 pm Aaron Williams wrote:
> On Tuesday, February 08, 2011 07:38:44 am Andrew Dyer wrote:
> > On Mon, Feb 7, 2011 at 16:58, Scott Wood <scottwood@freescale.com> wrote:
> > > On Mon, Jan 31, 2011 at 06:56:48PM -0800, Aaron Williams wrote:
> > >> Trying again submitting the patch.
> > >>
> > >> /* Do manufacturer-specific fixups */
> > >> switch (info->manufacturer_id) {
> > >>
> > >> + case 0x0000:
> > >> case 0x0001:
> > >> flash_fixup_amd(info, &qry);
> > >> break;
> > >
> > > This seems unrelated.
> > >
> > > Otherwise, the patch looks good. Whose tree should it go through?
> > > It's not really a NAND patch, though NAND is the reason for it.
> >
> > NAK
> >
> > This is not only unrelated (which the OP was told to fix on the
> > previous post of this patch), but wrong. The S29GL series chips don't
> > return 0x0000 for the manufacturer ID. AMD (later Spansion) have
> > always had mfg. ID 0x0001.
> >
> > I have various boards with S29GL064, S29GL128N, and S29GL256P, and
> > they all return the correct value (0x0001) for the mfg. ID. I looked
> > up the latest datasheet and they have not changed that section.
>
> I always get 0x0000 for the mfg ID and cannot explain it. The full part
> number is S29GL064N90TF103 010FF058. That is why it was added. Without it,
> the proper fixup doesn't happen with this chip.
>
> -Aaron
Note that in our case the port width is 16-bits and the chip width is 8 bits.
I added some printf statements for all read accesses to help.
Here's the output when I enable debugging:
flash detect cfi
fwc addr 1f400000 cmd f0 f0f0 16bit x 8 bit
fwc addr 1f400000 cmd ff ffff 16bit x 8 bit
fwc addr 1f4000aa cmd 98 9898 16bit x 8 bit
is= cmd 51(Q) addr 1f400020 flash_read16: address 1f400020, value 0x5151
is= 5151 5151
flash_read16: address 1f400020, value 0x5151
is= cmd 52(R) addr 1f400022 flash_read16: address 1f400022, value 0x5252
is= 5252 5252
flash_read16: address 1f400022, value 0x5252
is= cmd 59(Y) addr 1f400024 flash_read16: address 1f400024, value 0x5959
is= 5959 5959
flash_read16: address 1f400024, value 0x5959
flash_read8: address 1f400021, value 0x51
flash_read8: address 1f400023, value 0x52
flash_read8: address 1f400025, value 0x59
flash_read8: address 1f400027, value 0x2
flash_read8: address 1f400029, value 0x0
flash_read8: address 1f40002b, value 0x40
flash_read8: address 1f40002d, value 0x0
flash_read8: address 1f40002f, value 0x0
flash_read8: address 1f400031, value 0x0
flash_read8: address 1f400033, value 0x0
flash_read8: address 1f400035, value 0x0
flash_read8: address 1f400037, value 0x27
flash_read8: address 1f400039, value 0x36
flash_read8: address 1f40003b, value 0x0
flash_read8: address 1f40003d, value 0x0
flash_read8: address 1f40003f, value 0x7
flash_read8: address 1f400041, value 0x7
flash_read8: address 1f400043, value 0xa
flash_read8: address 1f400045, value 0x0
flash_read8: address 1f400047, value 0x3
flash_read8: address 1f400049, value 0x5
flash_read8: address 1f40004b, value 0x4
flash_read8: address 1f40004d, value 0x0
flash_read8: address 1f40004f, value 0x17
flash_read8: address 1f400051, value 0x2
flash_read8: address 1f400053, value 0x0
flash_read8: address 1f400055, value 0x5
flash_read8: address 1f400057, value 0x0
flash_read8: address 1f400059, value 0x2
flash_read8: address 1f40005b, value 0x7
flash_read8: address 1f40005d, value 0x0
flash_read8: address 1f40005f, value 0x20
flash_read8: address 1f400061, value 0x0
flash_read8: address 1f400063, value 0x7e
flash_read8: address 1f400065, value 0x0
flash_read8: address 1f400067, value 0x0
flash_read8: address 1f400069, value 0x1
flash_read8: address 1f40006b, value 0x0
flash_read8: address 1f40006d, value 0x0
flash_read8: address 1f40006f, value 0x0
flash_read8: address 1f400071, value 0x0
flash_read8: address 1f400073, value 0x0
flash_read8: address 1f400075, value 0x0
flash_read8: address 1f400077, value 0x0
flash_read8: address 1f400079, value 0x0
device interface is 2
found port 2 chip 1 port 16 bits chip 8 bits
flash_read8: address 1f400087, value 0x31
flash_read8: address 1f400089, value 0x33
00 : 51 52 59 02 00 40 00 00 00 00 00 27 36 00 00 07 QRY.. at .....'6...
10 : 07 0a 00 03 05 04 00 17 02 00 05 00 02 07 00 20 ...............
20 : 00 7e 00 00 01 00 00 00 00 00 00 00 00 00 00 10 .~..............
fwc addr 1f400000 cmd f0 f0f0 16bit x 8 bit
fwc addr 1f401554 cmd aa aaaa 16bit x 8 bit
fwc addr 1f400aaa cmd 55 5555 16bit x 8 bit
fwc addr 1f401554 cmd 90 9090 16bit x 8 bit
flash_read8: address 1f400001, value 0x0
flash_read8: address 1f400003, value 0x3f
fwc addr 1f400000 cmd f0 f0f0 16bit x 8 bit
fwc addr 1f4000aa cmd 98 9898 16bit x 8 bit
flash_read8: address 1f40009f, value 0x3
manufacturer is 2
manufacturer id is 0x0
device id is 0x3f
device id2 is 0x0
cfi version is 0x3133
size_ratio 1 port 16 bits chip 8 bits
found 2 erase regions
erase region 0: 0x0100007e
erase_region_count = 127 erase_region_size = 65536
erase region 1: 0x00200007
erase_region_count = 8 erase_region_size = 8192
fwc addr 1f400000 cmd f0 f0 8bit x 8 bit
fwc addr 1fbfe000 cmd 70 70 8bit x 8 bit
flash_read8: address 1fbfe000, value 0xe5
flash_read8: address 1fbfe000, value 0xe5
flash_is_busy: 0
Flash: 8 MiB
next prev parent reply other threads:[~2011-02-09 1:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 0:24 [U-Boot] mtdparts fails with NAND >= 4GB Aaron Williams
2011-01-28 1:06 ` Scott Wood
2011-01-28 1:14 ` Aaron Williams
2011-01-28 1:43 ` [U-Boot] [PATCH 1/1] NAND " Aaron Williams
2011-01-31 23:15 ` Aaron Williams
2011-01-31 23:28 ` Scott Wood
2011-02-01 2:56 ` [U-Boot] [PATCH 1/1] NAND Re: mtdparts fails with NAND >= 4GB - Second try Aaron Williams
2011-02-07 22:58 ` Scott Wood
2011-02-08 15:38 ` Andrew Dyer
2011-02-08 23:11 ` Aaron Williams
2011-02-09 1:56 ` Aaron Williams [this message]
[not found] ` <201102092228.40033.Aaron.Williams@caviumnetworks.com>
[not found] ` <AANLkTi=fsZXQjRFaZcB535n853WUxEicFqyzquWzMX41@mail.gmail.com>
2011-02-11 3:24 ` Aaron Williams
2011-02-11 3:27 ` Aaron Williams
2011-02-11 4:05 ` Aaron Williams
2011-02-12 0:15 ` Aaron Williams
2011-02-12 6:25 ` Albert ARIBAUD
2011-02-12 6:42 ` Aaron Williams
2011-02-12 7:01 ` Albert ARIBAUD
2011-02-12 7:06 ` Aaron Williams
2011-02-12 7:14 ` Aaron Williams
2011-02-12 7:51 ` Albert ARIBAUD
2011-02-12 7:57 ` Aaron Williams
2011-02-12 8:49 ` Albert ARIBAUD
2011-02-12 8:54 ` Aaron Williams
2011-02-12 10:08 ` Albert ARIBAUD
2011-02-12 12:06 ` Aaron Williams
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=201102081756.14299.Aaron.Williams@caviumnetworks.com \
--to=aaron.williams@caviumnetworks.com \
--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