<?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>Could I move the external 32.768kHz crystal on 51822 for keyboard application???</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/2473/could-i-move-the-external-32-768khz-crystal-on-51822-for-keyboard-application</link><description>Hi, 
 As the title said, I need more GPIOs for application, and could I use the XL1 and XL2 ?
What happen when use RC oscillator instead?
 
 Thanks.</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 06 Aug 2014 12:25:20 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/2473/could-i-move-the-external-32-768khz-crystal-on-51822-for-keyboard-application" /><item><title>RE: Could I move the external 32.768kHz crystal on 51822 for keyboard application???</title><link>https://devzone.nordicsemi.com/thread/9974?ContentTypeID=1</link><pubDate>Wed, 06 Aug 2014 12:25:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d6f15655-d087-491f-8d57-3fbe5ca358df</guid><dc:creator>FormerMember</dc:creator><description>&lt;p&gt;Yeah, couldn&amp;#39;t come up with a realistic low power use case where the synthesized clock would be useful.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Could I move the external 32.768kHz crystal on 51822 for keyboard application???</title><link>https://devzone.nordicsemi.com/thread/9973?ContentTypeID=1</link><pubDate>Mon, 28 Jul 2014 16:59:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2b470224-aa77-44d6-8050-a1b8ef79877d</guid><dc:creator>syntroniks</dc:creator><description>&lt;p&gt;In my experiments running with LFCLKSRC_RC_OSC_4000 I notice a few microamps higher current consumption relative to the 32khz crystal. Perhaps the hf clock is turned off inbetween connection events. The 16MHz osc is not a requirement of the internal 32khz osc. The synthesized lf clock, however, does require the HFCLK to be running. I don&amp;#39;t know why there is even a synthesized clock :D Limited uses I guess&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Could I move the external 32.768kHz crystal on 51822 for keyboard application???</title><link>https://devzone.nordicsemi.com/thread/9972?ContentTypeID=1</link><pubDate>Thu, 08 May 2014 12:15:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ce28d932-6935-46a4-8935-e18a2c2e8954</guid><dc:creator>FormerMember</dc:creator><description>&lt;p&gt;You&amp;#39;ll have to add the current required for the HF_CLK. The datasheet says that HF_CLK oscillator will consume around 470uA when it needs to drive for any peripheral, 25 uA if it is idle. I guess (not sure) HF_CLK  providing clock to LF_CLK accounts to it being active, so 470 uA more, which is quite a bit. I hope someone can clarify this.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Could I move the external 32.768kHz crystal on 51822 for keyboard application???</title><link>https://devzone.nordicsemi.com/thread/9971?ContentTypeID=1</link><pubDate>Thu, 08 May 2014 10:20:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a2d2eeea-afa6-4839-8c7a-d8d8b9c5ca52</guid><dc:creator>jimlin</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;How much current will it raise when sleep, if the synthesized LFCLK used?
&lt;/code&gt;&lt;/pre&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Could I move the external 32.768kHz crystal on 51822 for keyboard application???</title><link>https://devzone.nordicsemi.com/thread/9970?ContentTypeID=1</link><pubDate>Thu, 08 May 2014 09:20:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e47b06d0-c72f-4bb5-ab33-117556e0b227</guid><dc:creator>FormerMember</dc:creator><description>&lt;p&gt;For a BLE application, you&amp;#39;ll need at least 250 ppm accuracy for the LF clock and this cannot be achieved with RC oscillator. The other option that you have is to use the LF clock synthesized from the HF clock.
The advantage with this option apart from having 2 additional GPIOs is that you wouldn&amp;#39;t have to wait for 0.3s for the LF OSC to settle if you stop it and you&amp;#39;ll have predictable and low latency from waking up. But the con is that the sleep power required would be higher.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>