esp-idf

Wykres commitów

Autor	SHA1	Wiadomość	Data
Ivan Grokhotkov	7998b6ca2e	components/nvs: handle more cases where sudden power off may happen This commit fixes several issues with state handling in nvs::Page. It also adds extra consistency checks in nvs::PageManger initialization. These changes were verified with a new long-running test ("test recovery from sudden poweroff"). This test works by repeatedly performing same pseudorandom sequence of calls to nvs_ APIs. Each time it repeats the sequence, it introduces a failure into one of flash operations (write or erase). So if one iteration of this test needs, say, 25000 flash operations, then this test will run 25000 iterations, each time introducing the failure point at different location.	2016-08-23 12:08:00 +08:00
Angus Gratton	9ec0e1545d	Standardise remaining uses of SDK to ESP-IDF	2016-08-19 15:01:15 +08:00
Ivan Grokhotkov	bd6ea4393c	Initial public version	2016-08-17 23:08:22 +08:00

Autor

SHA1

Wiadomość

Data

Ivan Grokhotkov

7998b6ca2e

components/nvs: handle more cases where sudden power off may happen

This commit fixes several issues with state handling in nvs::Page. It also adds extra consistency checks in nvs::PageManger initialization.
These changes were verified with a new long-running test ("test recovery from sudden poweroff"). This test works by repeatedly performing same pseudorandom sequence of calls to nvs_ APIs. Each time it repeats the sequence, it introduces a failure into one of flash operations (write or erase). So if one iteration of this test needs, say, 25000 flash operations, then this test will run 25000 iterations, each time introducing the failure point at different location.

2016-08-23 12:08:00 +08:00

Angus Gratton

9ec0e1545d

Standardise remaining uses of SDK to ESP-IDF

2016-08-19 15:01:15 +08:00

Ivan Grokhotkov

bd6ea4393c

Initial public version

2016-08-17 23:08:22 +08:00

3 Commity (3ccec167065f0acf6b8de0e8c5d04ced9ce8041c)