<?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>SDK15.2 Operational issues between FDS and PPI ADC</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/41009/sdk15-2-operational-issues-between-fds-and-ppi-adc</link><description>Hi Nordic, 
 Does FDS affect PPI ADC acquisition when writing data? The test found that once the FDS is written to the data, the ADC data returned by the PPI ADC is fixed. 
 1.The acquired AD data is correct before the FDS write operation. 
 
 2.After</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 17 Dec 2018 09:30:52 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/41009/sdk15-2-operational-issues-between-fds-and-ppi-adc" /><item><title>RE: SDK15.2 Operational issues between FDS and PPI ADC</title><link>https://devzone.nordicsemi.com/thread/162017?ContentTypeID=1</link><pubDate>Mon, 17 Dec 2018 09:30:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:da170098-9f01-4e1b-b145-c747273fba4a</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;I copy my answer from the other thread:&lt;/p&gt;
&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The CPU will be halted during the flash write operation, depending on how frequent the ecg_data occurs, it may not be able to service the interrupts between measurements. Maybe this is causing your program flow to misbehave. Can you check your ADC configuration has changed and/or if your event source for the PPI channel to the ADC task has changed?&lt;/p&gt;
&lt;p&gt;An FDS write operation may not take very long time if it&amp;#39;s only an flash write operations that occurs (maybe tens of ~us range), but if the FDS write trigger an flash erase operation to be able to write, then the CPU may be halted for 100ms, which is very long time.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SDK15.2 Operational issues between FDS and PPI ADC</title><link>https://devzone.nordicsemi.com/thread/161796?ContentTypeID=1</link><pubDate>Fri, 14 Dec 2018 05:42:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ba579f40-e432-4048-b1a2-66098323ec27</guid><dc:creator>Jray</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;&lt;span&gt;Kenneth,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp; &amp;nbsp;&amp;nbsp;I have not received your reply, can you help me analyze this problem?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Thanks!&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SDK15.2 Operational issues between FDS and PPI ADC</title><link>https://devzone.nordicsemi.com/thread/161190?ContentTypeID=1</link><pubDate>Tue, 11 Dec 2018 12:26:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7d921846-9380-4a14-bf26-d5f3ad276fa9</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Did you see my response in case&amp;nbsp;218696?&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>