I see.
But, if you are erasing eeprom very frequently in your application, I do not now what "very frequently means ??", then your eeprom will be dead "very soon".
Then, very soon, your customers will be calling you "very frequently".
I see.
But, if you are erasing eeprom very frequently in your application, I do not now what "very frequently means ??", then your eeprom will be dead "very soon".
Then, very soon, your customers will be calling you "very frequently".
"If the Earth were a single state, Istanbul would be its capital." Napoleon Bonaparte
hehehe
all true
but like i said i'm just experimenting with reading and writing.
When i manage to get it right i will move to external eeproms
Microchip states that it's "1,000,000 write EEPROM endurance".
I hope it's true
.
yeah i remind this one... but i'm not sure if it wasn't only for EXTERNAL eeprom.. playing with page write, voltage and temperature seems to be external dedicated tricks to me... but yeah i may have missed the one about PIC!
http://www.picbasic.co.uk/forum/showthread.php?t=1670
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Yep, got me again, that's the one I was talking about. For some reason, I thought it was for internal eeprom/flash. I have yet to totally wipe out a flash PIC or on chip EEPROM on a PIC yet. I've worn out a small chunk of one, like the first 64 bytes of an older 18F4620, but not completely...yet...today...or even this year... I can sure try![]()
Some statements from 24LC32 datasheet.
"
• Endurance:
- 10,000,000 Erase/Write cycles
guaranteed for High Endurance Block
- 1,000,000 E/W cycles guaranteed for
Standard Endurance Block
"
In the same datasheet, there is also this;
"...the first 4K, starting at address 000,
is rated at 10,000,000 E/W cycles guaranteed. The
remainder of the array, 28K bits, is rated at 100,000 E/W cycles guaranteed."
Do I get it wrong, or the datasheet contradicts itself?
----------------
"If the Earth were a single state, Istanbul would be its capital." Napoleon Bonaparte
What this is saying is that the first 4k locations are 'high endurance' (and probably physically larger). The remaining 28k bytes are 'standard endurance'.
Just make sure your code always starts to store data from address 0 so the low adfdresses get most writes and the highest see less writes.
HTH
Brian
Bookmarks