https://devzone.nordicsemi.com/f/nordic-q-a/65700/wear-levelingNordic nRF52840, with regards to stored security keys in flash, some wear leveling schemes move data when being updated but do not erase data from the old location. This is an issue when going through the FIPS 140-2 certification. Can you comment in thisen-USTelligent Community 13Wed, 09 Sep 2020 13:35:08 GMThttps://devzone.nordicsemi.com/thread/268776?ContentTypeID=1Wed, 09 Sep 2020 13:35:08 GMT137ad170-7792-4731-bb38-c0d22fbe4515:a215add4-0586-4a5c-95ed-bcc26518f342Kenneth<p>If you use the FDS module to store data, then you are right that when updating stored data in flash, it will simply write new data to a free location in the available flash pages reserved for FDS, without deleting or erasing previous data (it&#39;s only marked as &quot;invalid&quot;). The reason for this is to reduce the wear on the flash, e.g. flash retention is 10.000 flash erase operations if I remember correctly, in addition flash erase operations take time, so for most applications you want to reduce the amount of flash operations. If this is a problem there are basically two options:</p> <p>- run the fds_gc() each time you update the data in question, because running garbage collection this will &quot;clean up&quot; flash pages to erase data that is no longer valid, note that this will trigger multiple flash erase operations depending on the number of flash pages that are reserved for the FDS.&nbsp;</p> <p>OR</p> <p>- don&#39;t use the FDS module, but instead use the flash api directly to store data raw in a flash page.</p> <p>Kenneth</p><div style="clear:both;"></div>