Re: FM24C256 serial EEPROM, doubt in page write mode
Bookmark this page:
 Yahoo!
 Google
 Windows Live
 del.icio.us
 digg
 Netscape
|
|
||||||||||
|
Posted by Mike Harrison on August 9, 2008, 9:37 am
Please log in for more thread options wrote: There are subtle differences between manufacturers of eeproms, and page-write behaviour can be different. If you have the correct datasheet for the maker of your eeprom, it is also possible the that datasheet has been copy-and-pasted from previous versions and they didn't update it properly. Or they did a die rev. The wrap-to-start behaviour is rarely useful, so people would be unlikely to notice as it;s unlikely to have been used. However anyone designing around a chip that does cross boundaries 'properly', and then encountering one that same-page-wrapped would quickly see problems. (e.g. when production changes supplier...) | ||||||||||
| Similar Threads | Posted |
| Re: FM24C256 serial EEPROM, doubt in page write mode | August 9, 2008, 9:37 am |
| tutorial about how to write in eeprom in 9s12xdt512 | June 5, 2007, 7:30 am |
| How to write EEPROM of RTL8100 network card. | October 9, 2006, 8:12 am |
| I2C EEPROM recommendation (with software write protect to prevent corruption) | March 28, 2006, 1:12 am |
| How to address ( serial and parallel) eeprom | January 26, 2008, 5:16 am |
| doubt | June 30, 2007, 1:15 am |
| doubt | February 9, 2008, 6:34 am |
| Basic doubt | December 22, 2005, 10:27 pm |
| PCI arbiter doubt | January 17, 2006, 12:17 am |
| Doubt about SERDES | March 31, 2006, 12:05 pm |
| PIC Language Doubt | September 2, 2006, 11:10 am |
| Please clarify my doubt | August 18, 2007, 4:55 am |
| Protel design doubt | February 28, 2005, 7:10 pm |
| Basic doubt in I2C interface | April 4, 2005, 12:45 am |
| PCI arbiter doubt in REQ signal | January 18, 2006, 10:36 pm |
>I was just interfacing my ATmega128 uc with FM24C256 EEPROM on i2c
>bus. The datasheet of the eeprom mentions a Page Write mode, where it
>says that the memory is devided into pages of 64byte each, starting at
>addresses 0x0040, 0x0080..and so on.
>the datasheet says that in page write mode we can continuously write
>max of 64bytes and if more byte are sent to the eeprom, they will roll-
>over to the starting address of the page, rather than getting written
>into the next page.
>So, i wrote a code to write n read the eeprom. It works fine.
>now, the doubt is, when i sent more than 64bytes continuously, the
>excess bytes are getting written into the next page rather than
>rolling-over and getting written to the same page beginning, which i
>confirmed by reading the pages one by one.
>well, this doesn't do any harm, but i'm just curious, how come
>datasheet is wrong?? or did i misunderstand something??
>
>Thanx.