https://devzone.nordicsemi.com/f/nordic-q-a/103985/nvs-storage-cannot-properly-read-stored-data-after-reboot-nrf9160dkI used the NVS example for the NRF9160. It worked very well. I can run the example, without any issue. However, I then integrated the NVS example into my actual project. Most things work. I can write to the device, and then read it. No problem. Buten-USTelligent Community 13Thu, 21 Sep 2023 14:44:49 GMThttps://devzone.nordicsemi.com/thread/447120?ContentTypeID=1Thu, 21 Sep 2023 14:44:49 GMT137ad170-7792-4731-bb38-c0d22fbe4515:ac97ba18-a328-406e-a07c-93e306757cdeMaria Gilje<p>Hi Steve,</p> [quote user=""]1. nvs_read() ALWAYS returns a size of 254, even before anything is written to it (right after a fresh erase &amp; flash). In the NVS example code, there is a test to see if there is any data in the given address ID. [/quote] <p>How do you read the value of the return? Is it possible that nvs_read is returning a negative error code, but you are reading it as an unsigned int?</p> [quote user=""]2. Once I DO write to the given ID with nvs_write(), I can then read it back without issue, during the same session. Upon reboot (not re-flash), however, the program is back to always returning 254 as the size, whether or not something had been written there before rebooting. In this case there should be have been something there, a struct of size 228 byes.[/quote] <p>I don&#39;t have details for you right now, but I can elaborate later.</p> <p>Note that Zephyr Settings storage has a partition in NVS. You can share the partition with Zephyr Settings storage by defining the partitions in .yaml. See <a href="https://devzone.nordicsemi.com/f/nordic-q-a/77781/problem-to-read-back-flash-with-nvs-when-concurrent-use-with-bluetooth/331360">this reply</a> in a previous ticket. </p> <p>Please let me know if this is helpful. If you are having trouble still, I will help you more.</p> <p>Best Regards,</p> <p>Maria</p><div style="clear:both;"></div>