SST Flash Support (SST39VF160)
Stefan Roese
stefan.roese at esd-electronics.com
Tue May 21 11:41:34 EDT 2002
> SST 39VF160 chips are CFI-compliant. You shouldn't need any special code
> for them -- just use cfi_probe.
That's what I tried too. Here is what I get when I use the sst flash's (all
debug info turned on):
>>>
physmap flash device: 200000 at ffc00000
CFI: Found no Physically mapped flash device at location zero
<<<
On the amd flash board I get the following debug messages:
>>>
physmap flash device: 200000 at ffc00000
Number of erase regions: 4
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: 0x200000 bytes (2 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: 4
Erase Region #0: BlockSize 0x4000 bytes, 1 blocks
Erase Region #1: BlockSize 0x2000 bytes, 2 blocks
Erase Region #2: BlockSize 0x8000 bytes, 1 blocks
Erase Region #3: BlockSize 0x10000 bytes, 31 blocks
kmod: failed to exec /sbin/modprobe -s -k cfi_cmdset_0002, errno = 2
Support for command set 0002 not present
cfi_probe: No supported Vendor Command Set found
<<<
Any thoughts/suggestions?
Thanks a lot,
Stefan.
More information about the linux-mtd
mailing list