<?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 update fails with radio driver and softdevice active</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/65310/fds-update-fails-with-radio-driver-and-softdevice-active</link><description>Hello, 
 I am developing a BLE and IEEE 802.1.4 multiprotocol device. I implemented a parser to change some settings of the device. T he configuration is updated with this piece of code: 
 
 m_fds_write_in_progress is reset to false in the fds event handler</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 28 Aug 2020 11:27:47 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/65310/fds-update-fails-with-radio-driver-and-softdevice-active" /><item><title>RE: FDS update fails with radio driver and softdevice active</title><link>https://devzone.nordicsemi.com/thread/266979?ContentTypeID=1</link><pubDate>Fri, 28 Aug 2020 11:27:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:390381d2-e1d5-48da-b465-ad6cf5c3e654</guid><dc:creator>MeisterBob</dc:creator><description>&lt;p&gt;I had suspected something like this. That did the trick thank you&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: FDS update fails with radio driver and softdevice active</title><link>https://devzone.nordicsemi.com/thread/266909?ContentTypeID=1</link><pubDate>Fri, 28 Aug 2020 08:48:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1e8d62cc-e897-4e52-90ec-c5a0fe30c6a8</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Most likely the&amp;nbsp;&lt;span&gt;nrf_802154_receive() function is running in an interrupt context with higher (or equal) priority than the FDS/Fstorage event handler. The FDS handler is blocked by the current interrupt context until the while loop &amp;quot;times out&amp;quot; and the function exits. Once the receive-handler exits, the FDS/fstorage interrupt is processed.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;It is not good practice to stay for extended periods of time inside interrupt context handler. You should rather set a flag to process the flash write in main context, or use app_scheduler to schedule event handling later.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Best regards,&lt;br /&gt;Jørgen&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>