<?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>32.768Khz crystal frequency offset detection</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/96612/32-768khz-crystal-frequency-offset-detection</link><description>Hi, 
 We had a product developed with nRF52810. We found some product would frequently disconnect with samsung cellphone.We tested 2.4G frequence of the product in fix frequence, the 2.4G frequence was fine. So we guessed it may be caused by 32.768Khz</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 14 Feb 2023 01:24:29 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/96612/32-768khz-crystal-frequency-offset-detection" /><item><title>RE: 32.768Khz crystal frequency offset detection</title><link>https://devzone.nordicsemi.com/thread/409719?ContentTypeID=1</link><pubDate>Tue, 14 Feb 2023 01:24:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:de2b20ef-ffad-49aa-b1e4-a6570833fd87</guid><dc:creator>james</dc:creator><description>&lt;p&gt;Hi haakonsh&lt;/p&gt;
&lt;p&gt;&amp;nbsp; Thanks so much.It helps me a lot.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: 32.768Khz crystal frequency offset detection</title><link>https://devzone.nordicsemi.com/thread/409593?ContentTypeID=1</link><pubDate>Mon, 13 Feb 2023 13:08:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:de90625c-bd7a-4151-8dd2-9e820483d65e</guid><dc:creator>haakonsh</dc:creator><description>&lt;p&gt;You can f.ex. measure the crystal&amp;#39;s signal directly by using an oscilloscope&amp;nbsp;to get start-up time, frequency offset, jitter, etc.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;One pitfall here is that a typical probe adds 9-12pF load to the signal. This can be overcome by either using an inductive probe, active probe (1-2pF load), or temporarily change the value of the crystal&amp;#39;s loading capacitor so that the total capacitive load matches the original load cap value.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;If you only need to measure offset you can can set up a GPIOTE channel to toggle a pin on RTC compare/overflow event, and then measure the pin with an analog or digital scope. Here you&amp;#39;ll want to run the RTC without prescaling and toggle the pin at large time periods, in order to average out the timing &amp;quot;error&amp;quot; of the PPI peripheral. PPI is bound to the 16MHz clock and need one clock cycle from a received EVENT to trigger a given TASK (min 61.25ns, max 122.5ns).&lt;br /&gt;&lt;br /&gt;An RTC overflow event will happen every 1s. PPM can then be calculated: ( 1s - (1s / (1s + error))) * 10^6.&lt;br /&gt;The maximum measurement error introduced by the PPI system is -0.1225PPM at 1s, which should be more good enough for clock accuracy verification.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>