NVM flash memory endurance

3 thoughts on “NVM flash memory endurance

  1. In Easy Script in Python documentation, there is note about limited number of program erase cycles of flash memories. I assume, that there is not wear-leveling algorithms implemented in module flash driver. But it seems, there is some kind of flash protection using RAM memory buffers while writting – existence of non-standard function flashflush(). Is there any recomendation, how to use python file objects for writting data to NVM with respect of flash memory endurance? Something like “If it is possible, do not write small blocks frequently …” or “Do not write more file objects alternately …”. How often occures program-erase cycles in flash, when I open file and I will periodicaly write e.g. 20 bytes?
  2. Thank you for response, I read this thread, but I think, it is not answer on my question.

    The question is, if I am using NVM in python scripts, is there any (recomended) flash friendly use of file objects? I mean something such as writting larger data blocks instead of many short blocks or so. I do not know Telit s internal implementation of flash access, so I do not know if every write to file cause programm/erase cycle on flash or internal memory buffers do it for me and I need not worry about size of data that I am writting.