<?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>Watchdog issues with with SDK 15.1.0 bootloader</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/38090/watchdog-issues-with-with-sdk-15-1-0-bootloader</link><description>Hi 
 I&amp;#39;ve just analyzed a behavior releated to the watchdog and the new SDK 15.1.0 bootloader. The bootloader just reseted after the configured watchdog timeout has elapsed (5 seconds in my case) and the integrated watchdog feeding logic of the bootloader</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 04 Sep 2018 13:26:42 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/38090/watchdog-issues-with-with-sdk-15-1-0-bootloader" /><item><title>RE: Watchdog issues with with SDK 15.1.0 bootloader</title><link>https://devzone.nordicsemi.com/thread/147194?ContentTypeID=1</link><pubDate>Tue, 04 Sep 2018 13:26:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2b9b738e-e43d-4739-ae5a-da2938f8b011</guid><dc:creator>Adrian Eggenberger</dc:creator><description>&lt;p&gt;Hi Bjorn&lt;/p&gt;
&lt;p&gt;Thanks for the answer. It confirmed everything I&amp;#39;ve seen in my analyzation.&lt;/p&gt;
&lt;p&gt;Regards Adrian&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Watchdog issues with with SDK 15.1.0 bootloader</title><link>https://devzone.nordicsemi.com/thread/147170?ContentTypeID=1</link><pubDate>Tue, 04 Sep 2018 12:18:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a2e64b2e-1c32-4ad4-969d-676fe289e2a7</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;Hi Adrian,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Yes, I do not see any issues with removing the&amp;nbsp;if (!nrf_clock_lf_is_running()) check in&amp;nbsp;timer_init.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;I discussed the&amp;nbsp;&lt;span&gt;m_wdt_keep_internal_feed variable with the SDK developer and he confirmed that this was a bug. The&amp;nbsp;m_wdt_keep_internal_feed flag can be removed entirely, i.e.&amp;nbsp;&lt;br /&gt;wdt_feed_timer_handler should look like this&lt;br /&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;static void wdt_feed_timer_handler(void)
{
        NRF_LOG_INFO(&amp;quot;Feeding WDT.&amp;quot;);
        wdt_feed();
}&lt;/pre&gt;&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Best regards&lt;/p&gt;
&lt;p&gt;Bjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>