NVS, possibility of broken data
Posted: Thu Feb 25, 2021 6:52 am
Hi all!
I see official NVS documentation, examples and component API in esp-idf. I see that it has several CRC values. For example in a page header and in NVS entry. As I understand, it is used to validate data. It can protect data against occasional bit changes. But I don't understand how to detect it.
Does nvs_open return ESP_ERR_NVS_NOT_INITIALIZED in this case? Does nvs_get_* return ESP_ERR_NVS_INVALID_NAME in this case? It's not really clear how can user control NVS data correctness. Could you help me to clarify this question?
I see official NVS documentation, examples and component API in esp-idf. I see that it has several CRC values. For example in a page header and in NVS entry. As I understand, it is used to validate data. It can protect data against occasional bit changes. But I don't understand how to detect it.
Does nvs_open return ESP_ERR_NVS_NOT_INITIALIZED in this case? Does nvs_get_* return ESP_ERR_NVS_INVALID_NAME in this case? It's not really clear how can user control NVS data correctness. Could you help me to clarify this question?