<?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>nrf54l15-power-increase-caused-by-nfc-read</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/126900/nrf54l15-power-increase-caused-by-nfc-read</link><description>With NCS 3.0 and the nRF54L15, even after applying patches, the power consumption anomaly can still be reproduced at the edge of the NFC range. The power consumption anomaly persists even after upgrading to NCS 3.2.1, with a power consumption of 365uA</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 10 Feb 2026 14:15:17 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/126900/nrf54l15-power-increase-caused-by-nfc-read" /><item><title>RE: nrf54l15-power-increase-caused-by-nfc-read</title><link>https://devzone.nordicsemi.com/thread/560809?ContentTypeID=1</link><pubDate>Tue, 10 Feb 2026 14:15:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e124b124-0481-4087-9041-c43c40810d72</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I see. I have tested with the &lt;a href="https://github.com/nrfconnect/sdk-nrf/blob/447abf08fa74b2ddbf0f4723b47cdad73f6c1f68/samples/nfc/record_text"&gt;NFC: Text record&lt;/a&gt;&amp;nbsp;sample, with two lines added to prj.conf to disable logging (as that leads to high idle current consumption in itself):&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;CONFIG_LOG=n
CONFIG_SERIAL=n&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;However, after a fairly large set of attempts I was still not able to reproduce the issue. Is special firmware needed to trigger this issue? Are you able to trigger with the&amp;nbsp;mentionned sample, or other code you can share?&lt;/p&gt;
&lt;p&gt;Also, are you only able to trigger with specific Android devices? If so, which phone do you use, and which app? Are you able to trigger this issue using other NFC readers, stand alone or iOS devices, or similar?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf54l15-power-increase-caused-by-nfc-read</title><link>https://devzone.nordicsemi.com/thread/560734?ContentTypeID=1</link><pubDate>Tue, 10 Feb 2026 05:56:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7c26d7b8-6af1-4ef5-b78a-06654478279e</guid><dc:creator>xht1987</dc:creator><description>&lt;p&gt;Connect the PCBA to a power analyzer. Use an Android phone to find the NFC&amp;#39;s maximum distance range. Then, repeatedly move the phone quickly close to and away from this maximum distance. Repeating this process should quickly reproduce the issue, usually after about 10 to 100 repetitions. I haven&amp;#39;t tested this with an iPhone yet, so I&amp;#39;m unsure if it can be reproduced.&amp;nbsp;When power consumption issues occurred during testing, exceeding 300&amp;micro;A, my program would stop the NFC every 10 minutes, modify the NFC data, and then restart the NFC. After restarting the NFC via software, the power consumption dropped to 159&amp;micro;A, but it couldn&amp;#39;t return to the normal power consumption of 4&amp;micro;A.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf54l15-power-increase-caused-by-nfc-read</title><link>https://devzone.nordicsemi.com/thread/560652?ContentTypeID=1</link><pubDate>Mon, 09 Feb 2026 12:45:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:41bee1a8-e3e4-42c7-9774-5671dc4b13b4</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Are you able to&amp;nbsp;consistently&amp;nbsp;reproduce this? Can you&amp;nbsp;elaborate&amp;nbsp;on how you test and trigger this behavior? Does it depend on your firmware, or which NFC reader you test with?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>