docs(storage): clarify example READMEs and when to use each

Update storage example docs so FATFS getting_started and wear_levelling
are clearly distinct, refresh the storage index paths, and add
"When to use this example" sections across storage examples.
This commit is contained in:
sonika.rathi
2026-08-19 14:54:49 +02:00
parent 76a34b3f85
commit b38461a0a8
28 changed files with 221 additions and 51 deletions
@@ -7,6 +7,11 @@ The purpose of this example is to show how to use the simplified, read-only API
A very practical application of being able to access the NVS in the bootloader build would be faster device restoration, where-in the application stores the device's current state/configurations and post a reset it would read the NVS to restore the device's last state, without waiting for application to boot-up.
## When to use this example
- You need to read NVS data from the bootloader (before the app starts), e.g. for fast state restoration.
- You want to use the simplified, read-only NVS bootloader API.
## Usage of this example:
Simply compile it: