| ??? 05/01/10 15:20 Read: times |
#175590 - Not quite true Responding to: ???'s previous message |
Daniel Contarino said:
Hi Riaz,
Read carefully http://www.atmel.com/dyn/resou...oc3286.pdf page 9. Writing a single byte in internal EEPROM takes 128ms!!. Writing a 32 byte page in 4ms or as 32 x 4ms single byte writes (128ms). So even if there is only one bit that is altered in a 32 byte page, it will cost you 4ms. If no bits have been changed, you do not need to waste 4ms. You will probably choose a strategy that is appropriate to your data. Clearly, blindly writing one byte at a time to EEPROM when the data has not altered is very inefficient. A single chip solution is very convenient for certain applications. You just have to choose what is best for your app. David. |
| Topic | Author | Date |
| help regarding 89s8253 | 01/01/70 00:00 | |
| i can,t understand what is the problem | 01/01/70 00:00 | |
| Either write less data to EEPROM or switch to 8-bit F-RAM | 01/01/70 00:00 | |
| i CAN understand what is the problem...... | 01/01/70 00:00 | |
| EEPROM need not be too slow. | 01/01/70 00:00 | |
| 'too' is a very relative word | 01/01/70 00:00 | |
| I use to work with AT89S8253 | 01/01/70 00:00 | |
| do not forget | 01/01/70 00:00 | |
| Not quite true | 01/01/70 00:00 | |
| maybe not, but ... | 01/01/70 00:00 | |
Be reasonable. | 01/01/70 00:00 |