<?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>Is there documentation that show the relationship between events and interrupts.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/14208/is-there-documentation-that-show-the-relationship-between-events-and-interrupts</link><description>It seems like there are several asynchronous things that happen and it&amp;#39;s unclear what had proprioty over each other. I assume interrupts asynchronously interrupt everything else. But do event, interrrupt events, if so under what conditions. Are handler</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 01 Jun 2016 10:28:00 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/14208/is-there-documentation-that-show-the-relationship-between-events-and-interrupts" /><item><title>RE: Is there documentation that show the relationship between events and interrupts.</title><link>https://devzone.nordicsemi.com/thread/54279?ContentTypeID=1</link><pubDate>Wed, 01 Jun 2016 10:28:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8832337a-5321-42d2-b01f-81c83d8ffe43</guid><dc:creator>Ole Bauck</dc:creator><description>&lt;p&gt;&lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52832.ps.v1.0/peripheral_interface.html?cp=2_2_0_13_5#concept_awc_t4z_vr"&gt;Here&lt;/a&gt; is documentation on events and interrupts.&lt;/p&gt;
&lt;p&gt;Events will not interrupt the code. Events will set a register that the CPU can read or the PPI can use to toggle tasks.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>