<?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>Are PPI events and interrupt connected?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/18008/are-ppi-events-and-interrupt-connected</link><description>How should we comprehend the nature of PPI, when dealing with radio interrupts? 
 For example, if I point radio event handler call back ( of this type: 
 static nrf_radio_signal_callback_return_param_t*) 
 to a radio interrupt event handler function</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 30 Nov 2016 05:33:42 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/18008/are-ppi-events-and-interrupt-connected" /><item><title>RE: Are PPI events and interrupt connected?</title><link>https://devzone.nordicsemi.com/thread/69417?ContentTypeID=1</link><pubDate>Wed, 30 Nov 2016 05:33:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a8829920-f556-400e-bdd1-4d596bfa6c62</guid><dc:creator>Mitch996</dc:creator><description>&lt;p&gt;No need, it&amp;#39;s quite clear, depends largely on how I configure it.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Are PPI events and interrupt connected?</title><link>https://devzone.nordicsemi.com/thread/69416?ContentTypeID=1</link><pubDate>Tue, 29 Nov 2016 12:20:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e171f39d-3fbd-41a1-815e-f4bd9cc3706b</guid><dc:creator>Petter Myhre</dc:creator><description>&lt;p&gt;An event can trigger an interrupt, it depends on how you have configured the peripheral.&lt;/p&gt;
&lt;p&gt;An event can trigger task, it depends on how you have configured the shorts of the peripheral, and the PPI.&lt;/p&gt;
&lt;p&gt;I think this is well explained in Section 10 in the nRF51 Series reference manual v3.0.&lt;/p&gt;
&lt;p&gt;Please add a comment if there is anything I need to clarify.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Are PPI events and interrupt connected?</title><link>https://devzone.nordicsemi.com/thread/69415?ContentTypeID=1</link><pubDate>Tue, 29 Nov 2016 01:27:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b8a3598a-3556-40ad-8541-71018290a158</guid><dc:creator>Mitch996</dc:creator><description>&lt;p&gt;Putting my question in a more straightforward way:
Does triggering either one of them mean you have to trigger the other?&lt;/p&gt;
&lt;p&gt;Or you can trigger just one?&lt;/p&gt;
&lt;p&gt;Or normally, triggering one of them has no impact whatsoever on the other?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Are PPI events and interrupt connected?</title><link>https://devzone.nordicsemi.com/thread/69414?ContentTypeID=1</link><pubDate>Mon, 28 Nov 2016 12:43:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:da024ed2-c414-4ffc-a4fe-73426e978e36</guid><dc:creator>Petter Myhre</dc:creator><description>&lt;p&gt;I having trouble understanding what you mean. PPI allows you to connect an event in one peripheral to a task in another peripheral, the event will trigger the task without CPU intervention. If you don&amp;#39;t use PPI you usually configure the peripheral to trigger an interrupt when a certain event happens, so that the CPU can react to it, with for example setting a task in another peripheral.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>