fds_record_write() in quick succession corrupts datahttps://devzone.nordicsemi.com/f/nordic-q-a/66741/fds_record_write-in-quick-succession-corrupts-dataAll of the FDS examples I have seen seem to ignore the fact that fds_record_write() just queues a write, and therefore the data pointed to by p_record.data.p_data needs to not change until the write operation has actually been processed. How do I knowen-USTelligent Community 13Mon, 05 Oct 2020 21:01:56 GMTRE: fds_record_write() in quick succession corrupts datahttps://devzone.nordicsemi.com/thread/273063?ContentTypeID=1Mon, 05 Oct 2020 21:01:56 GMT137ad170-7792-4731-bb38-c0d22fbe4515:11dd7cec-373e-4121-b4c6-6ea62f261219Chris Ergo<p>Thanks for the suggestion. I tried it and it works.</p> <p>I&#39;m still curious if there is an official recommended way to handle this.</p><div style="clear:both;"></div>RE: fds_record_write() in quick succession corrupts datahttps://devzone.nordicsemi.com/thread/273060?ContentTypeID=1Mon, 05 Oct 2020 20:27:14 GMT137ad170-7792-4731-bb38-c0d22fbe4515:308c9f25-e23d-4d55-bba8-6322b65391b9kmassa5<p>Hey! I&#39;ve had this problem, try setting a flag variable upon issuing a write command that is only unset by FDS_EVT_WRITE events (within the fds_evt_handler function). Use the flag to control when write commands can be executed!</p><div style="clear:both;"></div>