<?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>nRF52832 timer running fast</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/71436/nrf52832-timer-running-fast</link><description>Doing development on nRF52 DK board using buttonless DFU example and SDK 17.0.2. Running SES on Win10 and gnu compiler. 
 I&amp;#39;ve set up a 1 mS timer to run timing in my main loop. I find that it runs too fast by about 0.7%. This is unacceptable in my application</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 09 Feb 2021 15:27:46 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/71436/nrf52832-timer-running-fast" /><item><title>RE: nRF52832 timer running fast</title><link>https://devzone.nordicsemi.com/thread/293601?ContentTypeID=1</link><pubDate>Tue, 09 Feb 2021 15:27:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d937b377-2e9c-4f55-846b-67e4d4af6288</guid><dc:creator>Don</dc:creator><description>&lt;p&gt;Got it.&amp;nbsp; Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52832 timer running fast</title><link>https://devzone.nordicsemi.com/thread/293599?ContentTypeID=1</link><pubDate>Tue, 09 Feb 2021 15:13:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:05adc1a3-56a5-4c13-bf70-b6dc61c689ee</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Good to hear that solved the problem. FYI: The BLE will start and stop the HFCLK to save current consumption, so if the application need a accurate HFCLK is need to manually request it if it should stay ON all the time.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52832 timer running fast</title><link>https://devzone.nordicsemi.com/thread/293583?ContentTypeID=1</link><pubDate>Tue, 09 Feb 2021 14:22:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f9f44a5e-fffc-485a-8b7c-82f05e566635</guid><dc:creator>Don</dc:creator><description>&lt;p&gt;That seems to have done the trick!&amp;nbsp; Thanks.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I&amp;#39;m confused though.&amp;nbsp; How could the Bluetooth work if the clock is wrong?&amp;nbsp; I just verified that without that call, I can connect on BT while the clock is too fast.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52832 timer running fast</title><link>https://devzone.nordicsemi.com/thread/293575?ContentTypeID=1</link><pubDate>Tue, 09 Feb 2021 13:53:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f3ba8eaa-bb03-47a0-b565-69da2b8635e0</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Can you try to call sd_clock_hfclk_request() after enabling the softdevice to ensure that you have a accurate clock.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>