<?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 LFRC calibration current consumption during System ON low-power mode</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/128526/nrf54l15-lfrc-calibration-current-consumption-during-system-on-low-power-mode</link><description>Hi Nordic team, 
 I am working on a custom board based on the nRF54L15 using nRF Connect SDK v3.1.0. 
 On our hardware, the nRF54L15 has a 32 MHz crystal connected to XC1/XC2, but there is no external 32.768 kHz crystal connected to XL1/XL2. The XL1/XL2</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 01 Jul 2026 13:18:41 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/128526/nrf54l15-lfrc-calibration-current-consumption-during-system-on-low-power-mode" /><item><title>RE: nRF54L15 LFRC calibration current consumption during System ON low-power mode</title><link>https://devzone.nordicsemi.com/thread/568662?ContentTypeID=1</link><pubDate>Wed, 01 Jul 2026 13:18:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:58d25e13-af74-4635-8d89-fcb969f20b2a</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi MIke,&amp;nbsp;&lt;br /&gt;I&amp;#39;m taking over the ticket&amp;nbsp;because Simon is taking his vacation.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I agree that LFRC calibration wouldn&amp;#39;t be the main reason you are seeing such high current with System On Idle.&amp;nbsp;&lt;br /&gt;My suggestion is:&amp;nbsp;&lt;br /&gt;- Try testing with very simple application, for example blinky. Please compare the current consumption with same firmware on a DK.&amp;nbsp;All GPIO pins (except for the LED) should be left to default, high impedance. &lt;br /&gt;- You can also test with something doesn&amp;#39;t use LFCLK, for example simply put the CPU to sleep indefinitely wouldn&amp;#39;t require&amp;nbsp;LFCLK to run. This can rule out the RC calibration if it&amp;#39;s the case.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;- Try using a multi meter to confirm the current consumption with what you see on the power analyzer. We experienced issue with our PPK to measure&amp;nbsp;current consumption on the nRF54L due to high inrush current. The average sleep current should be fine though.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF54L15 LFRC calibration current consumption during System ON low-power mode</title><link>https://devzone.nordicsemi.com/thread/568458?ContentTypeID=1</link><pubDate>Fri, 26 Jun 2026 05:22:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:53b48bc1-68e9-47ab-b523-4da7def492bf</guid><dc:creator>Mike012</dc:creator><description>&lt;p&gt;Hi &lt;a class="internal-link view-user-profile" href="https://devzone.nordicsemi.com/members/simonr"&gt;Simonr&lt;/a&gt;,&lt;/p&gt;
&lt;p&gt;Thank you for the clarification.&lt;/p&gt;
&lt;p&gt;Regarding your questions:&lt;/p&gt;
&lt;p&gt;Yes, we agree that the average current around 40&amp;ndash;50 &amp;micro;A cannot be explained by LFRC calibration alone. In our measurement, the current floor / baseline is approximately 40&amp;ndash;50 &amp;micro;A, while the periodic peaks can reach several hundred &amp;micro;A and sometimes around 1 mA.&lt;/p&gt;
&lt;p&gt;Our target is to reduce the System ON low-power current as much as possible. Ideally, we would like to get closer to the single-digit &amp;micro;A range if possible, but we understand that this depends on what remains enabled in the system.&lt;/p&gt;
&lt;p&gt;At this stage, we are still checking possible board-level and firmware-level contributors, including GPIO states, possible back-powering through GPIOs connected to unpowered peripherals, external peripheral power rails, pull-up / pull-down current paths, UART or logging interfaces, sensors, PMIC states, and load switch states.&lt;/p&gt;
&lt;p&gt;There are external Wi-Fi and GNSS devices on the board, but during this test they are intended to be placed in sleep or low-power state. We are still verifying whether their power rails, control pins, and related GPIO states are fully consistent with the expected low-power condition, and whether there could be any remaining leakage or back-powering path.&lt;/p&gt;
&lt;p&gt;We do have a deeper PMIC-controlled off/shipping state available, which gives significantly lower current. However, for this specific test, we are evaluating the current consumption while the SoC remains in System ON low-power mode.&lt;/p&gt;
&lt;p&gt;I also checked the Online Power Profiler for Bluetooth LE with nRF54L15 and LF clock set to Internal RC. The result shows that the LF clock calibration current contribution is approximately 0.5 &amp;micro;A. Therefore, I understand that the LFRC calibration itself should not be the main reason for the 40&amp;ndash;50 &amp;micro;A baseline current.&lt;/p&gt;
&lt;p&gt;I would also like to confirm one more point about the RC calibration period. My understanding is that the RC calibration period defines how often the LFRC calibration is performed. During the actual calibration activity, we can expect a current peak because the LFRC is calibrated against the HF clock. However, between two calibration events, while the system is waiting for the next calibration period, is there still any additional current consumption caused by the calibration mechanism itself, or is the average contribution mainly from the short calibration events?&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Mike&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF54L15 LFRC calibration current consumption during System ON low-power mode</title><link>https://devzone.nordicsemi.com/thread/568323?ContentTypeID=1</link><pubDate>Tue, 23 Jun 2026 14:13:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:af4545f5-e191-4e2d-ae42-4be993d40497</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;1. Yes, the RC oscillator calibration calibrates towards the HF clock on the board, so these 600µA peaks would be expected during calibration. The calibration process is described here in the datasheet:&amp;nbsp;&lt;a href="https://docs.nordicsemi.com/r/bundle/ps_nrf54l15/page/clock.html-calibrating_32768khz_rcosc"&gt;https://docs.nordicsemi.com/r/bundle/ps_nrf54l15/page/clock.html-calibrating_32768khz_rcosc&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;2. The datasheet does not have any data describing the LFRC impact on current consumption, but you can use the Online Power Profiler for BLE to get estimates on the expected idle current consumption with and without a LFXO clock.&amp;nbsp;&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/power/w/opp/2/online-power-profiler-for-bluetooth-le"&gt;Online Power Profiler for Bluetooth LE&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;3. This would be the current consumption of the whole SoC, but you would avoid them with an external LF oscillator. In total, the full clock calibration current addition should be approximately 0.5µA to the overall idle current.&lt;/p&gt;
&lt;p&gt;4. Yes, for any application using BLE, you should not edit the LFRC calibration interval, as it needs to be within the BLE specification&amp;#39;s accuracy. And for that, calibration every 4 seconds is required.&lt;/p&gt;
&lt;p&gt;5. An LFXO would lower the idle current consumption somewhat, but is there a reason you need to have it in system ON mode? A power management IC would be way more efficient for handling a shipping mode, but it depends on how you get it out of shipping mode I guess.&lt;/p&gt;
&lt;p&gt;If the average current consumption is around 40µA that is not&amp;nbsp;&lt;strong&gt;just&lt;/strong&gt; the LFRC oscillator&amp;#39;s current consumption though, as it still should be in the single digit µA if the calibration is the only thing consuming current? I see you say&amp;nbsp;&lt;strong&gt;most of&lt;/strong&gt; the peripherals are disabled, but are anything left enabled on your end that might explain the current consumption you&amp;#39;re seeing? Do you have a target current consumption number to reach? What is the floor current of current consumption trace here? Can you upload the whole file so we can review it for you?&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>