Hi,
Is there any limitation on maximum no of function call which should be made to add/delete profile function due to EEPROM used for configuration?
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi,
Is there any limitation on maximum no of function call which should be made to add/delete profile function due to EEPROM used for configuration?
Hi Mahesh,
Are you asking about the write endurance of the EEPROM?
Regards,
Aaron
Would also like to know if the firmware is smart and won't over write a profile if it exists or rewritie a setting that hasnt changed.
For example is it safe to always issue the netapp_dhcp on boot to set the dhcp mode of the module or should we try to do it only when we need to modify it.
This comes down to the write endurance of the eeprom and how we can minimise writes to it.
Hi Mahesh,
It depends on module manufacturer, but its probably going to be on the order of millions regardless. Our module should have an eeprom with 1,000,000 write cycles and 40 years data retention.
Regards,
Aaron
Aaron L said:Hi Mahesh,
It depends on module manufacturer, but its probably going to be on the order of millions regardless. Our module should have an eeprom with 1,000,000 write cycles and 40 years data retention.
Regards,
Aaron
Hi Aaron,
Are you sure you did not mean 100,000? We stress tested two separate CC3000 modules and they both failed after 120,000 write-erase cycles.