<?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 Sample Code</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/13656/fds-sample-code</link><description>Hi, 
 I am trying to use the FDS for saving some variables and displaying them again later. I have downloaded the NRF52-fds-master sample code posted on github. However, this uses the peer manager and I don&amp;#39;t want to include that in my final code. I</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sun, 15 Oct 2017 08:04:38 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/13656/fds-sample-code" /><item><title>RE: FDS Sample Code</title><link>https://devzone.nordicsemi.com/thread/52184?ContentTypeID=1</link><pubDate>Sun, 15 Oct 2017 08:04:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6605b4dd-8703-4972-8ab8-8fc68d932ce1</guid><dc:creator>Tanasis!</dc:creator><description>&lt;p&gt;Do you have also an example for SDK 12.x? This one &lt;a href="https://devzone.nordicsemi.com/question/173279/nrf51-sdk-12-fds-issues/"&gt;doesn&amp;#39;t seem to work with SDK 12.x&lt;/a&gt;. Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: FDS Sample Code</title><link>https://devzone.nordicsemi.com/thread/52183?ContentTypeID=1</link><pubDate>Wed, 26 Oct 2016 08:32:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:49e77a2a-ab1b-4c2b-8bfc-d5ed34d4719d</guid><dc:creator>Stefan Birnir Sverrisson</dc:creator><description>&lt;p&gt;You can find &lt;a href="https://github.com/hubuhubu/nRF52-fds-example"&gt;simple fds example here&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: FDS Sample Code</title><link>https://devzone.nordicsemi.com/thread/52180?ContentTypeID=1</link><pubDate>Fri, 16 Sep 2016 15:22:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ba0a18fc-4b22-46da-9c7d-3288ec75a043</guid><dc:creator>saiteja</dc:creator><description>&lt;p&gt;hi, rk where i can get fds simple examples for nrf51.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: FDS Sample Code</title><link>https://devzone.nordicsemi.com/thread/52179?ContentTypeID=1</link><pubDate>Thu, 05 May 2016 19:06:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:01f546af-4c4c-4a2f-bcb0-f5153300a487</guid><dc:creator>alhay49</dc:creator><description>&lt;p&gt;Thank you for the notes. I worked out what the problem was.
I was initalising the FDS module and then calling the write command without waiting for the event handler to return. I&amp;#39;ve now added a delay and it is working well.
The sample code I had reviewed had the peer manager component that also initialises the FDS so by the time they did test writes this initialisation had already been completed and they didn&amp;#39;t have a check to make sure that it was.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: FDS Sample Code</title><link>https://devzone.nordicsemi.com/thread/52182?ContentTypeID=1</link><pubDate>Thu, 05 May 2016 18:53:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1831c1ae-7dca-4e11-b040-88a0cb6102bc</guid><dc:creator>alhay49</dc:creator><description>&lt;p&gt;Yes, I had read through the initialising and had the pm_init in the main function.
I solved the issue.
The sample code initialised the peer manager and then called a test init later. This means the system initialises the fds module twice and the first time is early during the start up.
In my code I had my test method calls right after the initialisation and didn&amp;#39;t wait for the event handler to return that it had been initialised. I added a delay flag to wait for the response and now it works.
Thanks for the help!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: FDS Sample Code</title><link>https://devzone.nordicsemi.com/thread/52178?ContentTypeID=1</link><pubDate>Thu, 05 May 2016 07:42:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f8c41172-d944-46ad-bc0f-6d86c33780fc</guid><dc:creator>RichieJH</dc:creator><description>&lt;p&gt;Ok, one other thing to check is you are initialising correctly, I see a comment in the SDK &amp;quot;In the Peer Manager, fds_init is part of the initialization function pm_init.&amp;quot;  Presumably you have already accounted for that?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: FDS Sample Code</title><link>https://devzone.nordicsemi.com/thread/52177?ContentTypeID=1</link><pubDate>Thu, 05 May 2016 00:52:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:76b06d7a-cb66-4a2b-b4d7-0d210b8f6b64</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;Of course FDS works without the peer manager and it works with the softdevice and the uart drivers and everything else, it&amp;#39;s simply another wrapper around the flash writing event system, well actually fstorage is another wrapper around the flash writing event system and fds is just built on top of that.&lt;/p&gt;
&lt;p&gt;Basically sounds like you&amp;#39;re on the right path, so bang some debugging in there and see what&amp;#39;s going on. Is your sys_evt_dispatch() getting called with flash storage events and do the events you&amp;#39;re getting make sense, ie is the write actually happening, but you&amp;#39;re just not getting the callback? Is the underlying fstorage subsystem getting initialized properly and your client properly registered to it?&lt;/p&gt;
&lt;p&gt;Or post some code, it&amp;#39;s impossible to debug observations. You&amp;#39;re probably just missing one small thing, the FS and FDS work pretty well, much better than the old pstorage module.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: FDS Sample Code</title><link>https://devzone.nordicsemi.com/thread/52176?ContentTypeID=1</link><pubDate>Wed, 04 May 2016 23:47:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dd3be0f3-897e-4ac4-b014-95ba29afe17a</guid><dc:creator>alhay49</dc:creator><description>&lt;p&gt;I test call the methods for reading and writing after initializing the ble components (ble stack, gap params, services etc) but before calling the advertising start method. This is how it is done in the sample code. I am assuming that the radio isn&amp;#39;t active until I start advertising.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: FDS Sample Code</title><link>https://devzone.nordicsemi.com/thread/52181?ContentTypeID=1</link><pubDate>Wed, 04 May 2016 23:14:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2060dfa6-c138-4fa3-95b9-d90223456541</guid><dc:creator>RichieJH</dc:creator><description>&lt;p&gt;The radio has higher priority and may prevent flash operation.  Have you tried getting it to work with simple static data?  If you are trying to trigger flash operation when the radio is working in relation to the BLE UART that could be problematic.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>