docs/nvs_flash: update the nvs flash offset comment according review

diff --git a/components/nvs_flash/include/nvs_flash.h b/components/nvs_flash/include/nvs_flash.h
index 1cade0e956514923d656ee4dbe5f9275866d67bf..d6e199025030133cad4bb0181e8d6c8d59e68241 100644 (file)
--- a/components/nvs_flash/include/nvs_flash.h
+++ b/components/nvs_flash/include/nvs_flash.h
@@ -21,7 +21,7 @@ extern "C" {
 /** Initialise NVS flash storage with default flash sector layout
 
     Temporarily, this region is hardcoded as a 12KB (0x3000 byte)
-    region starting at 24KB (0x6000 byte) offset in flash.
+    region starting at 36KB (0x9000 byte) offset in flash.
 
     @return ESP_OK if flash was successfully initialised.
 */

diff --git a/docs/partition-tables.rst b/docs/partition-tables.rst
index 5f5911bd528b88086d19f4aecd8b85e53631b21b..a1a46866eef604addb7b22520fbb3c7815bcee0f 100644 (file)
--- a/docs/partition-tables.rst
+++ b/docs/partition-tables.rst
@@ -23,7 +23,7 @@ Known Issues
 The below design document outlines the goals for the partition table system. At the moment, only some features are used:
 
 - data partition types "rf" & "wifi" are unused and can be entirely omitted to save space.
-- NVS (non-volatile-storage) uses a hardcoded 12KB (0x3000 byte) region at offset 0x6000.
+- NVS (non-volatile-storage) uses a hardcoded 12KB (0x3000 byte) region at offset 0x9000.
 
 Once a full user API is in place for partition access, these limitations will be resolved and you'll be able to use the partition mechanism fully for storing data in flash.