public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Manfred Gruber <gruber.m@utanet.at>
To: linux-mtd@lists.infradead.org
Subject: Re: Number of CFI chips ?
Date: Fri, 20 Aug 2004 13:15:01 +0200	[thread overview]
Message-ID: <200408201315.01078.gruber.m@utanet.at> (raw)
In-Reply-To: <1092999456.14552.3387.camel@hades.cambridge.redhat.com>

hi !

Am Freitag, 20. August 2004 12:57 schrieben Sie:
> On Fri, 2004-08-20 at 13:00 +0200, Manfred Gruber wrote:
> > Hi guys !
> >
> > I am trying to find out why my 2 AM29LV256M do not work.
> > See before was: Re: JFFS2 with AM29LV256M
> >
> > I found out that CFI only detects one chip.
> >
> > What should CFI detect when I have 2 AM29LV256M chips on a 32 bit bus.
> > Each AM29LV256 has 16 bit bus with with connected to the 32bit bus. So
> > CFI has to setect 2 chips, am i right ?(wehn interleave is set to 2, and
> > buswith is set to 32)
> >
> > When it only detects one chip, my problem must be in detecting the chips
> > by CFI, is this correct ?
>
> Not necessarily. Some of our printks are confusing -- if it claims to
> have detected only one chip then it might mean one _pair_ of chips. Can
> you show exactly what it said?

this is the output, you see that i have phymaped 64MB, but cfiprobe only 
detects 32MB. also only one erase region and so on 

physmap flash device: 4000000 at 10000000
genprobe_new_chip nr of chips 2
Number of erase regions: 1
Primary Vendor Command Set: 0002 (AMD/Fujitsu Standard)
Primary Algorithm Table at 0040
Alternative Vendor Command Set: 0000 (None)
No Alternate Algorithm Table
Vcc Minimum:  2.7 V
Vcc Maximum:  3.6 V
No Vpp line
Typical byte/word write timeout: 128 s
Maximum byte/word write timeout: 256 s
Typical full buffer write timeout: 128 s
Maximum full buffer write timeout: 4096 s
Typical block erase timeout: 1024 ms
Maximum block erase timeout: 16384 ms
Chip erase not supported
Device size: 0x2000000 bytes (32 MiB)
Flash Device Interface description: 0x0002
  - supports x8 and x16 via BYTE# with asynchronous interface
Max. bytes in buffer write: 0x20
Number of Erase Block Regions: 1
  Erase Region #0: BlockSize 0x10000 bytes, 512 blocks
phys_mapped_flash: Found 2 x16 devices at 0x0 in 32-bit bank
 Amd/Fujitsu Extended Query Table at 0x0040
Using buffer write method
phys_mapped_flash: CFI does not contain boot bank location. Assuming top.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
6 RedBoot partitions found on MTD device phys_mapped_flash
Creating 6 MTD partitions on "phys_mapped_flash":
0x00000000-0x00040000 : "RedBoot"

and number of cfi chips tells :1 

thanks regards manfred

  reply	other threads:[~2004-08-20 11:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-20 11:00 Number of CFI chips ? Manfred Gruber
2004-08-20 10:57 ` David Woodhouse
2004-08-20 11:15   ` Manfred Gruber [this message]
2004-08-20 11:13     ` David Woodhouse
2004-08-20 11:27       ` Manfred Gruber
2004-08-20 11:40         ` David Woodhouse
2004-08-20 13:23           ` Number of CFI chips and Re: JFFS2 with AM29LV256M Manfred Gruber

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=200408201315.01078.gruber.m@utanet.at \
    --to=gruber.m@utanet.at \
    --cc=linux-mtd@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