Replies: 2 comments 1 reply
-
|
@Laczen , would you be able to have a look at this issue? Am I missing something here? Is it a limitation? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
@zafersn this is expected behavior. Doing an erase without noticing the user might result in valuable data being lost. IIRC there is some option to trigger an erase when data is detected at start of the sample. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I’m working with the NVS subsystem sample, and I’m seeing NVS write operations fail with error -5 (EIO) and the following message: flash_stm32_check_status: Status: 0x00000088 This happens when the storage partition sectors already contain data. It seems that the NVS sample requires the flash area to be pre-erased before use.
NOTE THAT: I am also seeing the same problem/behaivor when I use the zephyr SETTINGS(CONFIG_SETTINGS), it returns -5 when it calls: settings_save_one.
HW: STM32U575VI
Zephyr: v4.3.0-branch
Here is my config:
Storage partition: 0x1EC000, size 64KB (8 sectors × 8KB)
CONFIG_SETTINGS_NVS_SECTOR_COUNT=8
CONFIG_SETTINGS_NVS_SECTOR_SIZE_MULT=1
here is the log:
Beta Was this translation helpful? Give feedback.
All reactions