<?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>FDS leaves a &amp;quot;hole&amp;quot; in flash?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/29299/fds-leaves-a-hole-in-flash</link><description>Hi, 
 I have seen some curious behavior with the FDS module. I&amp;#39;m using nRF5SDK 14.2.0 with s140_nrf52840_5.0.0-2.alpha, with FreeRTOS. In short: In some cases it seems that doing writes/updates that collide somehow will leave &amp;quot;holes&amp;quot; (0xFFFFFFFF where</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 09 Jan 2018 14:32:15 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/29299/fds-leaves-a-hole-in-flash" /><item><title>RE: FDS leaves a "hole" in flash?</title><link>https://devzone.nordicsemi.com/thread/116549?ContentTypeID=1</link><pubDate>Tue, 09 Jan 2018 14:32:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:79f17653-5710-4a49-900a-6545204a9348</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;I can see the confusion, but this symbol only ensures that the library works with different users, like peer_manager and application, it does not ensure thread safe operations. We are looking into the possibility of making it thread safe, but this will require a very large amount of critical region sections, which will disable interrupts. I can&amp;#39;t say anything about if or when this will happen.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: FDS leaves a "hole" in flash?</title><link>https://devzone.nordicsemi.com/thread/116550?ContentTypeID=1</link><pubDate>Tue, 09 Jan 2018 13:26:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:90321eba-197e-4eef-aaf2-0f789100c43d</guid><dc:creator>&amp;#216;yvind</dc:creator><description>&lt;p&gt;Thanks, I see. I guess I got confused by the inclusion of FDS_THREADS definition. Also, does the word &amp;quot;currently&amp;quot; indicate that this will be made thread safe soon?&lt;/p&gt;
&lt;p&gt;Anyway, this seems to be stable enough for me with my mentioned workaround.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: FDS leaves a "hole" in flash?</title><link>https://devzone.nordicsemi.com/thread/116548?ContentTypeID=1</link><pubDate>Tue, 09 Jan 2018 13:11:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:063288f7-02ec-4150-934c-73866845560d</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Unfortunately, Flash storage, which FDS build on is &lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v14.2.0/lib_fstorage.html?cp=4_0_0_3_51"&gt;currently not thread safe&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Jørgen&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>