<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>flash FDS writing operation is not happening</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/92669/flash-fds-writing-operation-is-not-happening</link><description>Hi team, 
 I am using NRF52833 DK with PCA10100 on it and s140 soft device version.. 
 While writing data into the flash, it is not updating. 
 Here I am attaching my fds code: 
 /* File ID and Key used for the configuration record. */ 
 #define CONFIG_FILE</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 11 Oct 2022 13:52:27 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/92669/flash-fds-writing-operation-is-not-happening" /><item><title>RE: flash FDS writing operation is not happening</title><link>https://devzone.nordicsemi.com/thread/390291?ContentTypeID=1</link><pubDate>Tue, 11 Oct 2022 13:52:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:14a6a8fc-b2f7-425b-8cf5-58448f35833c</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
[quote user="hareesh gorle"]That is now working fine after made that changes.[/quote]
&lt;p&gt;Good to hear.&lt;/p&gt;
[quote user="hareesh gorle"]But after system reset, my flash data also get erased. What could be the reason.[/quote]
&lt;p&gt;I&amp;#39;m not aware of anything that can cause the flash data to be automatically erased on a reset, except maybe from an old chip with worn out flash (flash write/erase lifetime is &lt;a href="https://infocenter.nordicsemi.com/topic/ps_nrf52833/abs_max_ratings.html"&gt;minimum 10 000 cycles&lt;/a&gt;) . If the flash data is erased from a reset, something in your application must be erasing the data. Can you dump the content of the FDS pages (or full flash) before and after reset, and upload the files here?&lt;/p&gt;
[quote user="hareesh gorle"]Please let me know if anything I need to configure in sdk_config.h or in any other files.[/quote]
&lt;p&gt;There is no sdk_config.h settings that will cause the FDS data to be erased by a chip reset.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Jørgen&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: flash FDS writing operation is not happening</title><link>https://devzone.nordicsemi.com/thread/390215?ContentTypeID=1</link><pubDate>Tue, 11 Oct 2022 09:32:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9efda604-7f0e-4aba-854d-e3cd6a7701d1</guid><dc:creator>hareesh gorle</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;That is now working fine after made that changes.&lt;/p&gt;
&lt;p&gt;But after system reset, my flash data also get erased. What could be the reason.&lt;/p&gt;
&lt;p&gt;Please let me know if anything I need to configure in sdk_config.h or in any other files.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks and regards,&lt;/p&gt;
&lt;p&gt;Hareesh.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: flash FDS writing operation is not happening</title><link>https://devzone.nordicsemi.com/thread/389940?ContentTypeID=1</link><pubDate>Mon, 10 Oct 2022 07:43:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:68d1eac6-46db-465f-87f8-e9373bf17c8a</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;The error code corresponds to&amp;nbsp;&lt;a href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.1.0/group__fds.html#ggafa9be5679ab03d785820f2474c5ccc6ea04e28034cadb17722f619a2aed3dfda6"&gt;&lt;span&gt;FDS_ERR_NOT_FOUND&lt;/span&gt;&lt;/a&gt;&amp;nbsp;(0x8609). If the record have not been written for the first time using fds_record_write(), the&amp;nbsp;&lt;span&gt;fds_record_find() function will return this error. You can handle the error in a different way than passing the error code to APP_ERROR_CHECK(), for instance by writing the record if it does not exist.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: flash FDS writing operation is not happening</title><link>https://devzone.nordicsemi.com/thread/389885?ContentTypeID=1</link><pubDate>Sat, 08 Oct 2022 06:50:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7392f3d8-e38d-4094-921f-3fc0088c6b50</guid><dc:creator>hareesh gorle</dc:creator><description>&lt;p&gt;Hi Jorgen,&lt;/p&gt;
&lt;p&gt;I am getting following error while debugging.&lt;/p&gt;
&lt;p&gt;&amp;lt;error&amp;gt; app: ERROR 34313 [Unknown error code] at D:\nrf_sdk\nRF5_SDK_17.1.0_ddde560\nRF5_SDK_17.1.0_ddde560\examples\Ble_experiments\ble_uart_peripheral-NID\main.c:1088&lt;br /&gt;PC at: 0x000282B5&lt;br /&gt;&amp;lt;error&amp;gt; app: End of error report&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;rc = fds_record_find(CONFIG_FILE, CONFIG_REC_KEY, &amp;amp;desc, &amp;amp;tok);&lt;br /&gt; APP_ERROR_CHECK(rc);&amp;nbsp; //===================================&amp;gt;&amp;nbsp;&lt;span&gt;main.c:1088&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks and regards,&lt;/p&gt;
&lt;p&gt;Hareesh&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: flash FDS writing operation is not happening</title><link>https://devzone.nordicsemi.com/thread/389821?ContentTypeID=1</link><pubDate>Fri, 07 Oct 2022 12:26:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0ca7e512-6721-4912-a0ca-848c0779e5e7</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;How do you check that it is not updating? Do you get any error codes?&lt;/p&gt;
&lt;p&gt;FDS writes are asynchronous, meaning that the write is not necessarily completed when the write/update function returns. You need to implement the event handler and wait for the events indicating operation success before reading back the record. When using a Softdevice, the flash operations will be scheduled between BLE events and other Softdevice tasks.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Jørgen&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>