<?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>How to implement issue [20] from the errata: &amp;quot;RTC: Register values are invalid&amp;quot;</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/48180/how-to-implement-issue-20-from-the-errata-rtc-register-values-are-invalid</link><description>Errata for nRF52832 Rev 2 version 1.2, errata item 20, RTC: Register values are invalid, has a recommended workaround that i&amp;#39;d like to ensure i&amp;#39;ve implemented correctly - &amp;quot;Execute the below code before you use RTC:&amp;quot;. 
 &amp;quot;...before you use RTC&amp;quot; seems broad</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 05 Jun 2019 12:27:22 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/48180/how-to-implement-issue-20-from-the-errata-rtc-register-values-are-invalid" /><item><title>RE: How to implement issue [20] from the errata: "RTC: Register values are invalid"</title><link>https://devzone.nordicsemi.com/thread/191103?ContentTypeID=1</link><pubDate>Wed, 05 Jun 2019 12:27:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2b23a3e5-1fb7-448f-87d2-564e8d7915d7</guid><dc:creator>ovrebekk</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;&lt;/p&gt;
&lt;p&gt;You only have to run the workaround at the start of the program, before you configure the RTC. Not every time you need to access it.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Starting the LF clock is always necessary if you want to use the RTC, and as long as you trigger the STOP task after the LF clock is started, before you configure and use the RTC, then you shouldn&amp;#39;t have any problems.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;You won&amp;#39;t have to worry about this workaround when using the app_timer module or the SoftDevice, as they have been designed with this issue in mind.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards&lt;br /&gt;Torbjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>