NVS strange performance; NVS needs to be primed/warmed up before it can be usedhttps://devzone.nordicsemi.com/f/nordic-q-a/111427/nvs-strange-performance-nvs-needs-to-be-primed-warmed-up-before-it-can-be-usedHello and thank you for your time. I seem to be getting some incorrect performance from the flash memory with NVS, in that NVS needs to be primed or something before it works properly. I have been testing with this code: void Prime_Flash () { en-USTelligent Community 13Mon, 27 May 2024 17:40:31 GMTRE: NVS strange performance; NVS needs to be primed/warmed up before it can be usedhttps://devzone.nordicsemi.com/thread/486057?ContentTypeID=1Mon, 27 May 2024 17:40:31 GMT137ad170-7792-4731-bb38-c0d22fbe4515:1bafbfab-1737-4df5-9297-fad490613795i_4556<p>Thank you for your reply.</p> <p>Per your suggestion, I created a new partition for storing my data in flash. I want to do more testing but it seems everything is working.</p> <p>If I might make a suggestion, im sure other people will also want to use BLE and the NVS in the same project, perhaps NRF might consider some changes, although I admit im not sure what would be the best way to handle it, to avoid them having the same problem I did.</p><div style="clear:both;"></div>RE: NVS strange performance; NVS needs to be primed/warmed up before it can be usedhttps://devzone.nordicsemi.com/thread/485748?ContentTypeID=1Fri, 24 May 2024 08:46:09 GMT137ad170-7792-4731-bb38-c0d22fbe4515:0e2ec826-967d-46dd-9b84-2a9d882aab68Sigurd<p>Hi!</p> <p>I found a similar report of this issue here:&nbsp;&nbsp;<a href="https://devzone.nordicsemi.com/f/nordic-q-a/84285/using-nvs-with-bluetooth-enabled">Using NVS with Bluetooth Enabled</a>&nbsp;</p> <p>Maybe you can try the suggested workaround there, with using your&nbsp;<span>own &quot;userstorage&quot; partition for&nbsp;nvs.</span></p> <p><span></span></p><div style="clear:both;"></div>RE: NVS strange performance; NVS needs to be primed/warmed up before it can be usedhttps://devzone.nordicsemi.com/thread/485684?ContentTypeID=1Thu, 23 May 2024 16:03:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:958cfbff-0c02-4eff-b918-e4f904dec6edi_4556<p>Hello and thank you for your reply; the right-most column of data represents what the write and read functions are returning:</p> <p>Write 0 4<br />Read 0 -2<br />Write 1 4<br />Read 1 -2<br />Write 2 4<br />Read 2 -2<br />Write 3 4<br />Read 3 -2<br />Write 4 4<br />Read 4 -2<br />Write 5 4<br />Read 5 -2<br />Write 6 4<br />Read 6 4<br />Write 7 4<br />Read 7 4<br />Write 8 4<br />Read 8 4<br />Write 9 4<br />Read 9 4<br />Write 10 4<br />Read 10 4<br />Write 11 4<br />Read 11 4<br />Write 12 4<br />Read 12 4<br />Flash ready took 13 tries</p> <p></p> <p>Every write returns a 4, indicating 4 bytes have been written; this inherently indicates a problem, given that we are writing the same data to the same address, and would therefore expect a 0 after the first write.</p> <p>The reads start by returning -2, indicating there isnt even an entry in the flash register that that address exists. On read 6 we finally get a 4, indicating four bytes were read, but the data doesnt match the expected data, so another loop iteration is executed.</p><div style="clear:both;"></div>RE: NVS strange performance; NVS needs to be primed/warmed up before it can be usedhttps://devzone.nordicsemi.com/thread/485648?ContentTypeID=1Thu, 23 May 2024 13:17:01 GMT137ad170-7792-4731-bb38-c0d22fbe4515:007542d2-7a90-496a-b59a-4060d7f4d823Sigurd<p>Hi!</p> <p>Could you check what value the&nbsp;<span>nvs_write and and&nbsp;nvs_read functions are returning ?</span></p><div style="clear:both;"></div>