The answer to this question is probably quite obvious to everyone except me, yet I don’t know how to find an answer.
Writing to EEPROM has a significant, several msec, latency. In the Arduino examples I’ve seen, Delay is used, but that stops everything. My question is: is it really necessary to stop the sketch or just avoid another write until the last EEPROM action is done?
I don’t need instructions in how to avoid Delay; I do know how to do that. I just need to know whether other non-EEPROM actions can continue during the write time.
Just in case it might affect your answer, here’s an outline of what I want to do. I have just one byte that I need to store in non-volatile memory. In the worst case, that number will be read as much as 100 times a day, and written to perhaps <=20 times a day. If I always use the same address, this will give a minimum life-time of 2.28 years, which is not enough for this application. Hence I intend to use a ring of 20 addresses, giving something like 45 years. Use of this number is not “real-time”, hence the slow nature of EEPROM is of no concern, but other things I will be doing should not be delayed for that time. If Delay is actually required, I will use an external FRAM chip even for just this one number, but that seems pretty silly.