<?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>gpiote input realtime event handler is interrupted by BLE operation in the softdevice</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/93126/gpiote-input-realtime-event-handler-is-interrupted-by-ble-operation-in-the-softdevice</link><description>I am using the softdevice from SDK 17.0.2 for bluetooth communication in my nRF52840 instrument application. I am using a gpiote event handler to acquire 8192 readings from an ADC interrupting the gpiote every 31.25 uS (32 KHz). My ISR reads the 32 bit</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 21 Oct 2022 18:36:17 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/93126/gpiote-input-realtime-event-handler-is-interrupted-by-ble-operation-in-the-softdevice" /><item><title>RE: gpiote input realtime event handler is interrupted by BLE operation in the softdevice</title><link>https://devzone.nordicsemi.com/thread/391958?ContentTypeID=1</link><pubDate>Fri, 21 Oct 2022 18:36:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e8d40df4-d652-43ad-976a-e1fa88ce7010</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;Yes, it sounds like you will need the PPI to offload the CPU in this case. The highest interrupt priority will always be reserved to the Softdevice to handle timing critical protocol events ( see &lt;span&gt;&lt;a title="Processor usage patterns and availability" href="https://infocenter.nordicsemi.com/topic/sds_s132/SDS/s1xx/processor_avail_interrupt_latency/processor_usage_patterns.html?cp=4_7_3_0_15_2"&gt;Processor usage patterns and availability&lt;/a&gt;&lt;/span&gt;).&lt;/p&gt;
&lt;p&gt;We do not have any examples for connection a GPIOTE event to SPIM start task via PPI, but there are some instructions on how it can be done in the&amp;nbsp;&lt;span&gt;&lt;a title="SPI master" href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.1.0/hardware_driver_spi_master.html?cp=8_1_2_0_13"&gt;SPI master&lt;/a&gt;&lt;/span&gt; driver documentation, see the &amp;quot;Repeated transfers&amp;quot; section under &amp;quot;Advanced usage&amp;quot;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Vidar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>