<?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>nRF5340 LFCLK oscillator control clarification</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/115580/nrf5340-lfclk-oscillator-control-clarification</link><description>What is the exact LFCLK control behavior with regards to control from both the APPCORE and NETCORE? The clock control figure at https://docs.nordicsemi.com/bundle/ps_nrf5340/page/chapters/clock/doc/clock.html shows one LFCLK feeding both the APPCORE and</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 17 Oct 2024 11:26:23 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/115580/nrf5340-lfclk-oscillator-control-clarification" /><item><title>RE: nRF5340 LFCLK oscillator control clarification</title><link>https://devzone.nordicsemi.com/thread/506702?ContentTypeID=1</link><pubDate>Thu, 17 Oct 2024 11:26:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5be5b3df-fbe1-4e79-983f-f454d0576612</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi Dustin&lt;/p&gt;
&lt;p&gt;First off, I&amp;#39;m uploading this block diagram for reference:&lt;br /&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1729162251505v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Referring to the block diagram above you can see that there is one LFCLK RC oscillator, and one LF synthesized clock in the system. So&amp;nbsp;&lt;strong&gt;true&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Any core can trigger the calibration task independently of the other, but a DONE event will be generated in both cores when complete. So&amp;nbsp;&lt;strong&gt;true&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;&lt;span style="font-family:inherit;"&gt;If two instances of the LFCLK control system request different LFCLK sources, the power and clock subsystem will secure that the most accurate of the requested LFCLK sources is selected. If one instance requests a particular source to stop when another LFCLK control instance requests the ame source to run, but at a lower accuracy, the power and clock subsystem will switch to the less accurate source. So&amp;nbsp;&lt;strong&gt;true&lt;/strong&gt;.&lt;/span&gt;&lt;span style="font-family:inherit;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;True&lt;/strong&gt;, based on the previous paragraph.&lt;/li&gt;
&lt;li&gt;This returns an indication of what LF clock source is running. This register value in any CLOCK instance reflects status only due to configurations/actions in that CLOCK instance.&lt;/li&gt;
&lt;li&gt;Only if the RTC is enabled for the project/application this would be true. It&amp;#39;s possible to not use the RTC at all.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;span style="font-family:inherit;"&gt;Best regards,&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>