Number of times....
denno
Posts: 223
in Propeller 1
one can WRITE or READ from EEPROM in the Propeller before that part of the EEPROM cell, location wears out?
Thanks...
Thanks...
Comments
But remember that internally the EEPROM does the equivalent of a page write and that page can be 64 or 128 bytes, so writing to one byte affects all bytes in the page.
Actually it doesn't count if it does not changed any bits from 1 to 0 apparently. So you could hit the same byte in the page but the wear doesn't affect the other bytes. But too many have worried too much for too long about EEPROM wear. You can write to the same byte every 5 minutes and it would take around 10 years to be around the minimum mark. But wear does not mean failure but it can mean that the cell does not hold the charge as well or for as long, but then again all memory that relies on charges on floating gates such as EPROM, EEPROM, Flash etc will eventually lose some charge and become corrupted. This has been the case with EPROMs programmed decades ago that have suffered from bit rot. So too is the fate of all silicon memory.
Peter, I know you are aware of the following, but it may be of interest to some others on the forum.
Then there is the flow/growth of the silicon metal that effects all usual silicon chips
The metal tracks actually "flow" as the metal is in fact liquid metal and is subject to flow and also grow spurs with age. These effects are more pronounced in chips around 22nm and below because the tracks and spaces are so fine that over time the tracks flow which can create shorts and opens. I read that Intel processor chips (and of course others too) are only guaranteed to last ~10 years before some of these effects could render the chips unreliable. I'm unsure of how much is fact and how much is hype, but there is obviously some truth buried in there.
EEPROM technology (the windowed variety) of memory was fascinating. To program a "bit" you blasted the "fuse(s)" with a high voltage/current (~12V and ~~50mA) the fuse would burn out and the bit would be "programmed". Then if you exposed the chip to UV light for ~30 minutes, those blown fuses would self-heal (grow back) and all would be good for further programming. That is why you should find labels (to block the UV) on the windows of these chips. If you didn't have a label then you could expect problems some time down the track, depending on the amount of UV hitting the chip.
Metal flow has been well understood for a long time and even back in the 70's with actual "fuse" cell technology there was always a problem with whiskers growing (rather than flowing). If no more chips were made for the next 10 years then maybe the only chips that might still be operating are the older chips, and then maybe not unless it used mask ROM. So maybe the P2 and TAQOZ will still be running
We only have to worry about 22nm and below so P2 will be good almost for life.
I always thought the EPROMs were basically fuses which grew back under UV. But i see i have been wrong for the last 45 years Oh well, I’m still learning at my age
Lets say, you program a PROPELLER's EEPROM. So, the gate of the individual cell, through the programming, is charged with a "1" or it is discharged for a "0". That condition, 1 or 0 can be stored for how long?
Right now, I have several Basic Stamps running various watch dog programs on my boat. These programs have been running now for 13 years, non stop. A DO/LOOP, always checking various sensors. Will the program ever fail, meaning a "1" might change to a"0" in a cell?
Would this explain why, some old Radio Shack stuff, would fail after a long period of time? LOL
Of course if software would periodically or after reset read the EEPROM and write that data back then this should refresh it although to be sure you would erase then reprogram. However this is risky while it is running in-situ because the power might fail at that moment and then your memory would be corrupted etc.
Question, is it necessary to add a PAUSE 50 "after" each WRLONG and/or RDLONG to give the EEPROM time for it's WRITE.
Tracy, nice to hear from you again. You have helped me in the past with some ultrasonic issues, trying to scare the deer out of my garden...turns out that a fence works better...LOL
The 32k x 8, mentioned above...what software would you use to program that. The "x8" means it has 8 COGs?
Thanks again to all...