From: yidong zhang <zhangyd6@gmail.com>
To: Guillaume LECERF <glecerf@gmail.com>
Cc: taliaferro62@gmail.com, yegorslists@googlemail.com,
linux-mtd@lists.infradead.org,
Wolfram Sang <w.sang@pengutronix.de>,
David.Woodhouse@intel.com
Subject: Re: Re :Re: [Help] SST39VF6401B Support
Date: Fri, 22 Oct 2010 16:46:30 +0800 [thread overview]
Message-ID: <AANLkTi=NKDPhdoDYE0ZdM2tuqWdFBNbui1AHZw_wXx97@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinr5E2E4Nth_-XybNPKfHnrgSFPWtVqxkMdQa-Y@mail.gmail.com>
On Fri, Oct 22, 2010 at 3:52 PM, Guillaume LECERF <glecerf@gmail.com> wrote:
> 2010/10/22 yidong zhang <zhangyd6@gmail.com>:
>>>> Yes, i did test both SST39VF6401B and SST38VF6401 a moment ago; The
>>>> SST39VF6401B works fine. But the SST38VF6401 couldn't work because of
>>>> the sector-size.It was 64KByte when i displayed the erase size.
>>>
>>> Could you send me your log with SST38VF6401 please ?
>>> I need to investigate on this.
>>
>> Typical byte/word write timeout: 8 µs
>> Maximum byte/word write timeout: 16 µs
>> Typical full buffer write timeout: 8 µs
>> Maximum full buffer write timeout: 64 µs
>> Typical block erase timeout: 16 ms
>> Maximum block erase timeout: 32 ms
>> Typical chip erase timeout: 32 ms
>> Maximum chip erase timeout: 64 ms
>> Device size: 0x800000 bytes (8 MiB)
>> Flash Device Interface description: 0x0001
>> - x16-only asynchronous interface
>> Max. bytes in buffer write: 0x20
>> Number of Erase Block Regions: 2
>
> You didn't applied my latest patch, you would have only 1 erase region
> if you did.
It was printed by the print_cfi_ident function. And the region
number is readed from the flash. So there was 2 erase region
>> Erase Region #0: BlockSize 0x10000 bytes, 1024 blocks
>> cif->cfiq->EraseRegionInfo[i] = 10003ff
>> Erase Region #1: BlockSize 0x10000 bytes, 128 blocks
>> cif->cfiq->EraseRegionInfo[i] = 100007f
>> mb86hxx_pflash: Found 1 x16 devices at 0x0 in 16-bit bank
>> number of CFI chips: 1
>> ersize is 10000, ernum is 400
>> Sum of regions (4000000) != total size of set of interleaved chips (800000)
>
> This is the typical error with SST chips when the
> fixup_sst39vf_rev_b() fixup function isn't called.
It did call the fixup_sst39vf_recv_b() function, so you can see
>>number of CFI chips: 1
When we take the 1st erase region, we will get the wrong flash size
because of the wrong information(ersize is 10000, ernum is 400).
>
> Could you try and report me which patches you applied and what results
> you have with SST38VF6401 ?
Sorry, my current kernel version is not the latest one. My kernel
version is 2.6.31. I changed the code as your patch. But i can
confirm that the flash(SST39VF6401B) works fine. But the SST38VF6401
flash couldn't pass the probe. Please see the log below
>> Erase Region #0: BlockSize 0x10000 bytes, 1024 blocks
>> cif->cfiq->EraseRegionInfo[i] = 10003ff
>> Erase Region #1: BlockSize 0x10000 bytes, 128 blocks
>> cif->cfiq->EraseRegionInfo[i] = 100007f
I think the information we get from the flash is wrong. So we
shuoldn't take the 1st Erase Region. We can not get the right
description of the flash in the CFI mode. Maybe they should be moved
to JEDEC mode.
> --
> Guillaume LECERF
> GeeXboX developer - www.geexbox.org
>
next prev parent reply other threads:[~2010-10-22 8:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-16 7:08 Re :Re: [Help] SST39VF6401B Support yidong zhang
2010-10-16 10:07 ` Wolfram Sang
2010-10-16 12:25 ` yidong zhang
2010-10-16 13:17 ` Wolfram Sang
2010-10-16 14:20 ` yidong zhang
2010-10-18 4:00 ` yidong zhang
2010-10-18 11:41 ` Wolfram Sang
2010-10-18 13:05 ` yidong zhang
2010-10-18 13:41 ` Guillaume LECERF
2010-10-21 10:33 ` Guillaume LECERF
[not found] ` <AANLkTinLTW25faUTBfKBVcpFXFrtv1UhWWDN9Dgm1jOH@mail.gmail.com>
[not found] ` <AANLkTiknoWR_v-TfV5M5ZwsV3Lsk=EDDD185kXp4B96V@mail.gmail.com>
[not found] ` <AANLkTin-4fGYzD8a9rDp9M7YEk1y7JbXmZVLjA=3iU3Q@mail.gmail.com>
2010-10-21 15:24 ` Guillaume LECERF
2010-10-22 0:17 ` yidong zhang
2010-10-22 7:52 ` Guillaume LECERF
2010-10-22 8:46 ` yidong zhang [this message]
2010-10-22 10:41 ` Guillaume LECERF
2010-10-22 15:07 ` yidong zhang
2010-10-22 15:36 ` Guillaume LECERF
2010-10-22 15:42 ` yidong zhang
2010-10-22 17:50 ` Fabio Giovagnini
2011-06-16 0:55 ` Flávio Silveira
2011-06-20 3:12 ` Flávio Silveira
2011-06-20 3:36 ` yidong zhang
2011-06-20 23:55 ` Flávio Silveira
2011-12-08 21:21 ` Flávio Silveira
2011-12-09 23:15 ` Flávio Silveira
2011-12-10 0:54 ` Guillaume LECERF
2011-12-10 1:56 ` Flávio Silveira
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='AANLkTi=NKDPhdoDYE0ZdM2tuqWdFBNbui1AHZw_wXx97@mail.gmail.com' \
--to=zhangyd6@gmail.com \
--cc=David.Woodhouse@intel.com \
--cc=glecerf@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=taliaferro62@gmail.com \
--cc=w.sang@pengutronix.de \
--cc=yegorslists@googlemail.com \
/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;
as well as URLs for NNTP newsgroup(s).