https://devzone.nordicsemi.com/f/nordic-q-a/50076/nvmc-of-nrf52810The NVMC writting functions hasn&#39;t return values, void nrf_nvmc_write_bytes(uint32_t address, const uint8_t * src, uint32_t num_bytes) Does it mean that all internal FLASH writting operations will be successful? Except for erasing times to the upperen-USTelligent Community 13Tue, 23 Jul 2019 07:02:36 GMThttps://devzone.nordicsemi.com/thread/199927?ContentTypeID=1Tue, 23 Jul 2019 07:02:36 GMT137ad170-7792-4731-bb38-c0d22fbe4515:8ff5e86c-f855-454e-9a21-cd3e3fde3289Vidar Berg<p>It depends on your requirements. I would generally say FDS has it handles updates of existing data. The Peer manager module which is included in all examples that support pairing/bonding uses the FDS, so if you use those, you can simply register a new FDS user.&nbsp;</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/199900?ContentTypeID=1Tue, 23 Jul 2019 00:54:58 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3563727e-28d0-4a9f-87c9-1731ba341183Hansome<p>fstorage and fds, Which is better?</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/199768?ContentTypeID=1Mon, 22 Jul 2019 12:02:27 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d75455e0-df34-4a4b-bc9a-9358dcad53d7Vidar Berg<p>Hi,</p> <p>Flash writes can&nbsp;become corrupted if you experience unexpected resets due to power loss, etc.&nbsp;&nbsp;&nbsp;You may consider appending a checksum to your data to have a way of verifying the integrity. Also note that you will not get direct access to the NVMC if you use the Softdevice (nordic bluetooth stack). In that case, you need to use the Softdevice flash API, preferably through the fstorage or <a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.3.0/lib_fds.html?cp=5_1_3_55">fds </a>library.&nbsp;</p><div style="clear:both;"></div>