Hello, Would appreciate help or any suggestions
One question, I select a value using a keypad and save it in Pic's eeprom memory, but the eeprom memory has a life time, I think from 1 million to 3 million read / write cycles.
What other option could be done to avoid harming Pic? (read only once the value recorded in memory) or some other option
Thanks
Enrique
Cycles in Eeprom
Moderator: Benj
-
- Posts: 311
- Joined: Sat Jan 12, 2008 2:08 am
- Has thanked: 104 times
- Been thanked: 47 times
- Contact:
- Steve001
- Valued Contributor
- Posts: 1189
- Joined: Wed Dec 31, 2008 3:37 pm
- Has thanked: 460 times
- Been thanked: 523 times
- Contact:
-
- Matrix Staff
- Posts: 9520
- Joined: Sat May 05, 2007 2:27 pm
- Location: Northamptonshire, UK
- Has thanked: 2585 times
- Been thanked: 3815 times
- Contact:
Re: Cycles in Eeprom
You could even consider saving eeprom on power failure.
Take a look at this whole topic as there is talk on how its done.
Another way is only write to EEPROM on variable change only.
Don't constantly read or write to EEPROM.
Take a look at this whole topic as there is talk on how its done.
Another way is only write to EEPROM on variable change only.
Don't constantly read or write to EEPROM.
Martin
-
- Posts: 311
- Joined: Sat Jan 12, 2008 2:08 am
- Has thanked: 104 times
- Been thanked: 47 times
- Contact:
Re: Cycles in Eeprom
Hello, Martin and Steve
Thanks a lot for the data. I appreciate the help
Enrique
Thanks a lot for the data. I appreciate the help
Enrique
-
- Posts: 311
- Joined: Sat Jan 12, 2008 2:08 am
- Has thanked: 104 times
- Been thanked: 47 times
- Contact:
Re: Cycles in Eeprom
Hi Martin
Excellent work, I can read only once the data in the eeprom together with DisableDataSend = 1 in long times if the DisableDataSend = 0 is lost it also means that the data of the eeprom 'M' was lost and re-read in the eeprom.
When you read a data from the eeprom, you know how long time the data is retained in a variable?. . .Hours, minutes, days?
Steve thank You, is another option I will also do the test with the example you gave me.
Thanks
Enrique
Excellent work, I can read only once the data in the eeprom together with DisableDataSend = 1 in long times if the DisableDataSend = 0 is lost it also means that the data of the eeprom 'M' was lost and re-read in the eeprom.
When you read a data from the eeprom, you know how long time the data is retained in a variable?. . .Hours, minutes, days?
Steve thank You, is another option I will also do the test with the example you gave me.
Thanks
Enrique
- Attachments
-
- Eeprom1.fcfx
- flowchart
- (8.97 KiB) Downloaded 309 times
- Benj
- Matrix Staff
- Posts: 15312
- Joined: Mon Oct 16, 2006 10:48 am
- Location: Matrix TS Ltd
- Has thanked: 4803 times
- Been thanked: 4314 times
- Contact:
Re: Cycles in Eeprom
Hello Enrique,
Most chips will feature some sort of a brown out mechanism so that the chip will reset if the power supply becomes too low or unstable which may lead to RAM corruption. The brown out should happen well before any RAM corruption happens.
A value stored in to RAM should be retained as long as the device remains sufficiently powered. So ideally Years is the answer.When you read a data from the eeprom, you know how long time the data is retained in a variable?. . .Hours, minutes, days?
Most chips will feature some sort of a brown out mechanism so that the chip will reset if the power supply becomes too low or unstable which may lead to RAM corruption. The brown out should happen well before any RAM corruption happens.
Regards Ben Rowland - MatrixTSL
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
-
- Posts: 311
- Joined: Sat Jan 12, 2008 2:08 am
- Has thanked: 104 times
- Been thanked: 47 times
- Contact: