From: "Ho-Kuo Chan" <hchan@wavesat.com>
To: "David Woodhouse" <dwmw2@infradead.org>
Cc: <linux-mtd@lists.infradead.org>
Subject: Re: Trouble indetifying FLASH part
Date: Fri, 24 May 2002 10:09:41 -0400 [thread overview]
Message-ID: <006601c2032c$a62c2330$0200010a@WT0136> (raw)
In-Reply-To: 14563.1022190250@redhat.com
Hi David,
> hchan@wavesat.com said:
> > Calling cfi_probe_chip with bus width 2, interleave 2 and device_type 8
> > Calling cfi_probe_chip with bus width 2, interleave 2 and device_type 16
>
> What you have is a single chip, isn't it?
>
> Why does it never probe for bus width 2, interleave 1 and device_type 16?
>
> --
> dwmw2
Ooops, sorry, I missed part of the copy/paste. This is the result with
interleave at 1 with device_type 16:
Calling cfi_probe_chip with bus width 2, interleave 1 and device_type 16
Output Reg: 0x45480000
TCR: 0x750a0000
ODR: 0x20000
Control 0: 0x17ee616
Addr = 0x0
Cmd_addr = 0x0, CFIDEV_INTERLEAVE = 0x1, type = 0x2
Val = 0xf000
Addr = 0xaa
Cmd_addr = 0x55, CFIDEV_INTERLEAVE = 0x1, type = 0x2
Val = 0x9800
Read 0x=0, cmd = 0x5100
Read 0x=100, cmd = 0x5200
Read = 0x3e00, cmd = 0x5900
CFI Query Failed for driver
Something just occurred to me: the calculated cmd values are endian swapped.
I just checked and LE_BYTE_SWAP is still on, I have just turned it off and
the device is now recognied:
Calling cfi_probe_chip with bus width 2, interleave 1 and device_type 16
Output Reg: 0x45480000
TCR: 0x750a0000
ODR: 0x20000
Control 0: 0x17ee616
Addr = 0x0
Cmd_addr = 0x0, CFIDEV_INTERLEAVE = 0x1, type = 0x2
Val = 0xf0
Addr = 0xaa
Cmd_addr = 0x55, CFIDEV_INTERLEAVE = 0x1, type = 0x2
Val = 0x98
Read 0x=51, cmd = 0x51
Read 0x=52, cmd = 0x52
Read = 0x59, cmd = 0x59
Number of erase regions: 2
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: 16 µs
Maximum byte/word write timeout: 512 µs
Full buffer write not supported
Typical block erase timeout: 1024 µs
Maximum block erase timeout: 16384 µs
Chip erase not supported
Device size: 0x400000 bytes (4 MiB)
Flash Device Interface description: 0x0002
- supports x8 and x16 via BYTE# with asynchronous interface
Max. bytes in buffer write: 0x1
Number of Erase Block Regions: 2
Erase Region #0: BlockSize 0x2000 bytes, 8 blocks
Erase Region #1: BlockSize 0x10000 bytes, 63 blocks
<snip>
number of CFI chips: 1
mtd: Giving out device 0 to Physically mapped flash
Thanks for your help!!!!
HK
next prev parent reply other threads:[~2002-05-24 14:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001301c1fcd9$76792c40$0200010a@WT0136>
2002-05-15 20:50 ` Trouble indetifying FLASH part Ho-Kuo Chan
2002-05-16 12:33 ` David Woodhouse
[not found] ` <5240.1021554647@redhat.com>
2002-05-16 13:36 ` Ho-Kuo Chan
2002-05-16 13:37 ` David Woodhouse
2002-05-16 14:12 ` Ho-Kuo Chan
2002-05-16 14:15 ` David Woodhouse
2002-05-16 14:52 ` Ho-Kuo Chan
2002-05-16 15:01 ` David Woodhouse
2002-05-16 17:37 ` Ho-Kuo Chan
2002-05-23 21:19 ` Ho-Kuo Chan
2002-05-23 21:44 ` David Woodhouse
2002-05-24 14:09 ` Ho-Kuo Chan [this message]
2002-05-16 6:53 Jim Zeus
-- strict thread matches above, loose matches on Subject: below --
2002-05-16 13:25 Ho-Kuo Chan
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='006601c2032c$a62c2330$0200010a@WT0136' \
--to=hchan@wavesat.com \
--cc=dwmw2@infradead.org \
--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