<?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>Odd WDT behavior</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/50896/odd-wdt-behavior</link><description>Hi, 
 
 We have an freertos based app (SDK14.2). 
 Recently we have added a WDT support in the following manner: 
 
 The init code initializes the WDT reload value to T+3 seconds (currently 13 sec), run in Sleep, pause in Halt. This is done in main()</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 13 Aug 2019 12:03:06 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/50896/odd-wdt-behavior" /><item><title>RE: Odd WDT behavior</title><link>https://devzone.nordicsemi.com/thread/203812?ContentTypeID=1</link><pubDate>Tue, 13 Aug 2019 12:03:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:50007041-3594-4166-b836-a6ec49aab332</guid><dc:creator>eyalasko</dc:creator><description>[quote userid="2111" url="~/f/nordic-q-a/50896/odd-wdt-behavior/203806"] however you can in the CONFIG register configure &amp;quot;Pause watchdog while the CPU is halted by the debugger&amp;quot;[/quote]
&lt;p&gt;I&amp;#39;m doing this, however upon startup it takes several seconds until&amp;nbsp;all tasks are initialized and their task loop begin to run (and feed the WD RR channels)&lt;/p&gt;
&lt;p&gt;If for some reason the WD counter does not start from CRV=13 sec (e.g.if being stopped-restarted by the debugger),&amp;nbsp;the system will experience WD reset as not all of the tasks WD feeding kicked in &lt;span class="emoticon" data-url="https://devzone.nordicsemi.com/cfs-file/__key/system/emoji/1f61e.svg" title="Disappointed"&gt;&amp;#x1f61e;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Odd WDT behavior</title><link>https://devzone.nordicsemi.com/thread/203806?ContentTypeID=1</link><pubDate>Tue, 13 Aug 2019 11:41:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7f2d4274-47cd-44a9-b30f-7a7f787884ac</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;It is not possible to stop-restart it&amp;nbsp;&lt;span&gt;programmaticly, however you can in the CONFIG register configure &amp;quot;Pause watchdog while the CPU is halted by the debugger&amp;quot;. This may help?&lt;/span&gt;&amp;nbsp;&lt;/p&gt;
[quote user="eyalasko"]Hence looking at the &amp;#39;1&amp;#39;s on (watchdog) startup may suggest on the hanged task .[/quote]
&lt;p&gt;That is my understanding also yes.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Odd WDT behavior</title><link>https://devzone.nordicsemi.com/thread/203792?ContentTypeID=1</link><pubDate>Tue, 13 Aug 2019 11:09:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3d48ceb2-caa6-42ba-b45b-e880565feb78</guid><dc:creator>eyalasko</dc:creator><description>[quote userid="27169" url="~/f/nordic-q-a/50896/odd-wdt-behavior/203787"]What REQSTATUS flags are used for?[/quote]
&lt;p&gt;I think I figured it out -&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If any of the enabled channels REQSTATUS bits is &amp;#39;1&amp;#39; when the timer elapses, WD reset will fire ???&lt;/p&gt;
&lt;p&gt;Hence looking at the &amp;#39;1&amp;#39;s on (watchdog) startup may suggest on the hanged task .&lt;/p&gt;
&lt;p&gt;(Alternatively when channels is &amp;#39;fed&amp;#39;, it turns &amp;#39;0&amp;#39;. When all (enabled) flags are 0, the timer&amp;#39;s count&amp;nbsp; resets to CRV)&lt;/p&gt;
&lt;p&gt;Can you confirm?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Odd WDT behavior</title><link>https://devzone.nordicsemi.com/thread/203787?ContentTypeID=1</link><pubDate>Tue, 13 Aug 2019 10:58:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8d657f3a-8f80-4f4e-b66d-75f986c09f3a</guid><dc:creator>eyalasko</dc:creator><description>&lt;p&gt;Thanks.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;So if I understand you correctly the WDT keeps running after soft reset even if its not (re) configured?&lt;/p&gt;
&lt;p&gt;If so, is there a way to stop-restart it programmaticly so it will not interfer with debugging ?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Also,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;What REQSTATUS flags are used for?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks again&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Odd WDT behavior</title><link>https://devzone.nordicsemi.com/thread/203785?ContentTypeID=1</link><pubDate>Tue, 13 Aug 2019 10:49:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c2a48bf4-48f3-4b34-9eb7-7dcb08c9110b</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Yes, likely there is a soft reset during debug mode in this case to re-start the application, a soft reset will not reset WDT. A pin reset, power on reset, brown out reset, and watchdog reset will reset the WDT.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>