I would like to revisit an old issue discussed in thread 301, i.e. FLASH memory endurance.
How is the Python internal file system allocating memory? Hopefully, it would have some rotating principle to spread FLASH memory cell wear all over available FLASH memory, instead of always opening a file at the beginning of the FLASH address range.
If not, is there any good "trick" in Python to achieve such an even stress over the entire FLASH memory space?
Thanks, Tom
Hi Tom,
we have a file system and thus the files are not written in a fixed position. so also if you write the same file more times, a subsequent write is done in a near sector. In this way the writes are distributed over the entire flash andin this wayincreases itsduration.
Anyway we discourage to use the module as a datalogger
I would like to revisit an old issue discussed in thread 301, i.e. FLASH memory endurance.
How is the Python internal file system allocating memory? Hopefully, it would have some rotating principle to spread FLASH memory cell wear all over available FLASH memory, instead of always opening a file at the beginning of the FLASH address range.
If not, is there any good "trick" in Python to achieve such an even stress over the entire FLASH memory space?
Thanks, Tom
Hi Tom,
we have a file system and thus the files are not written in a fixed position. so also if you write the same file more times, a subsequent write is done in a near sector. In this way the writes are distributed over the entire flash and in this way increases its duration.
Anyway we discourage to use the module as a datalogger