<?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>Questions about NCS hardware interrupt time and SPI</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/115005/questions-about-ncs-hardware-interrupt-time-and-spi</link><description>The question is as follows： 
 When I read the ADS1299 data through SPI in the GPIOTE interrupt, I found that there was a time limit. Within about 50us. As shown in the figure below, the DRDY channel is the interrupt pin, and the program is the detection</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 27 Sep 2024 13:38:21 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/115005/questions-about-ncs-hardware-interrupt-time-and-spi" /><item><title>RE: Questions about NCS hardware interrupt time and SPI</title><link>https://devzone.nordicsemi.com/thread/504198?ContentTypeID=1</link><pubDate>Fri, 27 Sep 2024 13:38:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ad5d9b61-4381-4651-8b23-2a3e2862b5e4</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Do you have any log output or similar that shows the problem?&lt;/p&gt;
&lt;p&gt;Any code to reproduce this issue?&lt;/p&gt;
&lt;p&gt;What is the state of your firmware after this 68 bytes are read?&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
[quote user=""]Second question, using SPIM in NCS will turn on EASYDMA by default, so will executing spim to read data in interrupt take up MCU resources?[/quote]
&lt;p&gt;It will read/write according to the supplied buffers, and provide an event back when it is done. If it is setup in a synchronous way, it will go to idle and wait for the event to come back.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
[quote user=""]The third question, if the execution of spim will occupy MCU resources, is it possible to enable PPI + GPIOTE + SPIM to avoid the problem of time limit in interruptions? If I can, I just have to build this way, will read the data placed with RAM, is not able to completely avoid MCU resources. That way I can add other items like LCD and data algorithms[/quote]
&lt;p&gt;Yes, but this will require the use of&amp;nbsp;the nrfx_spim driver directly. I would recommend that we look into the initial issue first before considering this option.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;/p&gt;
&lt;p&gt;Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>