In article <>,
says...
>
> On 08.08.2011 21:24, elil wrote:
>
> > I'd like to understand why ALL Serial Flash chips always come with SPI
> > vs Serial EEPROM chips that always come with I2C ?
>
> That can't be understood, because it simply isn't true. SPI EEPROMs
> exist. Microwire (which is really just a subset of SPI) EEPROMs exist.
>
> > Why not vice versa for example?
>
> Possibly because Flash by design has a massive asymmetry of read vs.
> write speeds. To accommodate that speed in a useful fashion, the
> interface has to be _fast_. I2C usually just isn't fast enough.
For read cycles the interface matters, when it comes to flash or EEPROM
writes cycles even slow I2C (much less than 100kHz) is often TOO fast
for multibyte write cycles. let alone times for page erases.
Newer serial devices for I2C support even the 3.4MHz I2C spec that has
been around for a long time, I2C has never been limited to 400kHz, just
by some controller designs.
I tend to try where possible to use devices like Ramtron FRAM devices
for these types of applications if the capacity can cope with it as both
SPi and I2C variants are available. Easy interfacing and less software
overhead.
You are looking for 128kbit device Ramtron have 128kbit and 512kbit
as SPI and I2C, use what matches your requirements.
Write cycles are faster than serial bus speeds, writes can be done
without delays.
NO erase cycles, very low standby current.
Can be erased more times than most EEPROM and a lot of flash. data
retention period is speced longer as well.
Generally pin compatible with serial Flas/eeprom devices (especially
8 pin varieties).
Other manufacturers exist.
--
Paul Carpenter |
<http://www.pcserviceselectronics.co.uk/> PC Services
<http://www.pcserviceselectronics.co.uk/fonts/> Timing Diagram Font
<http://www.gnuh8.org.uk/> GNU H8 - compiler & Renesas H8/H8S/H8 Tiny
<http://www.badweb.org.uk/> For those web sites you hate