Conditions that lead to long flash write/erase timeshttps://devzone.nordicsemi.com/f/nordic-q-a/17145/conditions-that-lead-to-long-flash-write-erase-timesI am wondering what circumstances lead to the big difference of the write and erase times of the NVMC. Since the difference between the max. value is a multiple of the min. value are there certain things to pay attention or avoid? Thanks in advancen-USTelligent Community 13Wed, 19 Oct 2016 09:37:33 GMTRE: Conditions that lead to long flash write/erase timeshttps://devzone.nordicsemi.com/thread/65862?ContentTypeID=1Wed, 19 Oct 2016 09:37:33 GMT137ad170-7792-4731-bb38-c0d22fbe4515:f0077893-248b-4399-a321-192a6d076f29Pascal K&#252;nzi<p>Yes I was. That&#39;s good to know. Thank you!</p><div style="clear:both;"></div>RE: Conditions that lead to long flash write/erase timeshttps://devzone.nordicsemi.com/thread/65860?ContentTypeID=1Wed, 19 Oct 2016 09:06:28 GMT137ad170-7792-4731-bb38-c0d22fbe4515:578d25fa-2a2f-4c1c-bb27-02b12c690adaSigurd<p>If you are referring to the values in the PS, Chapter 11.8.1 Flash programming, these min and max values are best/worst case values with only the NVMC. The maximum values are a result of tests performed at very high temperatures, and at low voltages. While the min values are a result of testing at ideal temperatures and ideal voltages.</p><div style="clear:both;"></div>RE: Conditions that lead to long flash write/erase timeshttps://devzone.nordicsemi.com/thread/65861?ContentTypeID=1Wed, 19 Oct 2016 07:45:15 GMT137ad170-7792-4731-bb38-c0d22fbe4515:f6f1640b-1412-4568-b41e-0eaf8ca0659aPascal K&#252;nzi<p>Thank you! So the SoftDevice is the main reason for those max. times. Without SoftDevice they should be close to min value. Is that correct?</p><div style="clear:both;"></div>RE: Conditions that lead to long flash write/erase timeshttps://devzone.nordicsemi.com/thread/65859?ContentTypeID=1Wed, 19 Oct 2016 07:37:47 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3a57692f-6731-4a46-96bd-97cca92ae510Sigurd<p>When using SoftDevice you should use the <a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.sds/dita/softdevices/s130/flash_mem_api/flash_mem_api.html?cp=2_3_0_0_7">Flash memory API</a>. Use <a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v3.0.0/group___n_r_f___s_o_c___f_u_n_c_t_i_o_n_s.html?cp=2_3_0_1_0_2_7_2_9#ga8b49f2e72e97291aecc18ce396956eed">sd_flash_write()</a> to write and <a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v3.0.0/group___n_r_f___s_o_c___f_u_n_c_t_i_o_n_s.html?cp=2_3_0_1_0_2_7_2_7#ga9c93dd94a138ad8b5ed3693ea38ffb3e">sd_flash_page_erase()</a> to erase.</p> <p>The API will schedule flash access in between radio events automatically, to avoid conflicts between the radio and the flash operations. The way this works is that you don&#39;t really know when the flash access will happen, but you will get an event after the flash operation is complete telling you whether or not the flash operation was successful.</p> <p>In cases where flash access fails you can typically just retry the operation, but if you have so aggressive connection parameters that there is no room for flash operations (mainly a problem for flash erase operations) you might have to either change the connection parameters or temporarily disconnect the BLE link.</p><div style="clear:both;"></div>RE: Conditions that lead to long flash write/erase timeshttps://devzone.nordicsemi.com/thread/65858?ContentTypeID=1Wed, 19 Oct 2016 05:26:24 GMT137ad170-7792-4731-bb38-c0d22fbe4515:70236fc4-47be-4df9-8437-3713d8526501Pascal K&#252;nzi<p>Yes the S132. Is it only due to the restricted access of the NVMC when using a SoftDevice?</p><div style="clear:both;"></div>RE: Conditions that lead to long flash write/erase timeshttps://devzone.nordicsemi.com/thread/65857?ContentTypeID=1Tue, 18 Oct 2016 14:37:28 GMT137ad170-7792-4731-bb38-c0d22fbe4515:8a932741-4f46-4642-b2f9-add2c9648ab5Sigurd<p>Are you using a SoftDevice?</p><div style="clear:both;"></div>