<?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>Does the NFC Type 4 library globally disable interrupts at any point?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/20346/does-the-nfc-type-4-library-globally-disable-interrupts-at-any-point</link><description>Does the NFC library globally disable interrupts at any point? We&amp;#39;re trying to track down an issue where our code occasionally misses an I2C event during NFC read/write.</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 31 Mar 2017 14:11:08 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/20346/does-the-nfc-type-4-library-globally-disable-interrupts-at-any-point" /><item><title>RE: Does the NFC Type 4 library globally disable interrupts at any point?</title><link>https://devzone.nordicsemi.com/thread/79301?ContentTypeID=1</link><pubDate>Fri, 31 Mar 2017 14:11:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:77c22a2c-4e09-4f20-a41a-d0e6703dd19d</guid><dc:creator>CurtisHx</dc:creator><description>&lt;p&gt;To answer my own question: No, the NFC Type 4 library does not globally disable interrupts.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Does the NFC Type 4 library globally disable interrupts at any point?</title><link>https://devzone.nordicsemi.com/thread/79300?ContentTypeID=1</link><pubDate>Mon, 20 Mar 2017 14:52:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1f05d0b4-bdf3-470b-bffa-cd5ce1c102ca</guid><dc:creator>CurtisHx</dc:creator><description>&lt;p&gt;Thanks for the update.  Turns out our problem was not related to the NFC Library disabling / enabling interrupts.  It was caused by a timing problem in our code.  Good to know about the NFC interrupts, though.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Does the NFC Type 4 library globally disable interrupts at any point?</title><link>https://devzone.nordicsemi.com/thread/79299?ContentTypeID=1</link><pubDate>Mon, 20 Mar 2017 14:34:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6bf86427-83ed-4c86-b159-104d9e4585c2</guid><dc:creator>Michal</dc:creator><description>&lt;p&gt;Yes, the NFC library can globally disable interrupts through nrf_drv_clock module, look for &lt;code&gt;CRITICAL_REGION_ENTER()&lt;/code&gt; and &lt;code&gt;CRITICAL_REGION_EXIT()&lt;/code&gt; macros (using critical sections for RMW operations on driver&amp;#39;s state variables). The nrf_drv_clock is used for controlling oscillators. NFC can only be enabled when a high precession crystal oscillator is running.&lt;/p&gt;
&lt;p&gt;But even if IRQs are disabled, the I2C events should be set as pending and should fire when the interrupts are enabled again.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>