<?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>WDT Times Out Prematurely ( nRF9160 )</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/56165/wdt-times-out-prematurely-nrf9160</link><description>We&amp;#39;re experiencing occasional unexpected hardware watchdog resets. The watchdog is set to 10 minutes, and sometimes just 2 minutes after feeding the WDT we see a reset triggered with the watchdog being specified as the reset reason on boot. Are there</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 03 Jan 2020 17:54:07 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/56165/wdt-times-out-prematurely-nrf9160" /><item><title>RE: WDT Times Out Prematurely ( nRF9160 )</title><link>https://devzone.nordicsemi.com/thread/227484?ContentTypeID=1</link><pubDate>Fri, 03 Jan 2020 17:54:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a9caf47a-b3f1-4ad7-a685-6d2de56f520b</guid><dc:creator>MJD093</dc:creator><description>&lt;p&gt;This is probably a bad idea. Have you thought about using a non-blocking method instead?&lt;/p&gt;
&lt;p&gt;For example, setting your modem state, activating the modem and then monitoring the CEREG response periodically to determine connection status, thus leaving your device in a state to which it can respond to events and reload the WDT.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: WDT Times Out Prematurely ( nRF9160 )</title><link>https://devzone.nordicsemi.com/thread/227483?ContentTypeID=1</link><pubDate>Fri, 03 Jan 2020 17:49:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e7280eb4-0c21-4c85-aa9d-7cf044a3dc67</guid><dc:creator>phipi</dc:creator><description>&lt;p&gt;The other issue is that on boot we block on connecting to the cellular network which may take up to several minutes in some cases. During this time nothing else is running to kick the WDT&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: WDT Times Out Prematurely ( nRF9160 )</title><link>https://devzone.nordicsemi.com/thread/227473?ContentTypeID=1</link><pubDate>Fri, 03 Jan 2020 16:16:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bf7344eb-d29b-4725-968c-da2843c0089d</guid><dc:creator>phipi</dc:creator><description>&lt;p&gt;We have a work item reloading one channel and the main thread reloading the other channel. The work queue is on a 5 minute interval, however the main thread will reload whenever it processes something. I&amp;#39;ve changed the work item to 30 seconds now, which may resolve our issue, however it seems like this is a bug regardless.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: WDT Times Out Prematurely ( nRF9160 )</title><link>https://devzone.nordicsemi.com/thread/227472?ContentTypeID=1</link><pubDate>Fri, 03 Jan 2020 16:07:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:32a94320-24df-4680-ab08-c36e7c639a40</guid><dc:creator>MJD093</dc:creator><description>&lt;p&gt;How is it reloaded? Upon a specific task being completed, an event or is it perpetually reloaded throughout the code at a rate that is definitely going to be every few seconds? I know you mentioned that it can happen after only 2 minutes but with mine, the code runs the reload every few lines and I haven&amp;#39;t noticed any odd behaviour.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: WDT Times Out Prematurely ( nRF9160 )</title><link>https://devzone.nordicsemi.com/thread/227470?ContentTypeID=1</link><pubDate>Fri, 03 Jan 2020 16:02:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2b7ea619-053b-43dd-899a-a6e18bb078fb</guid><dc:creator>phipi</dc:creator><description>&lt;p&gt;It has definitely happened in different parts of the code but there&amp;#39;s no way to know exactly when so there&amp;#39;s a chance it was performing similar types of tasks when it happened.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: WDT Times Out Prematurely ( nRF9160 )</title><link>https://devzone.nordicsemi.com/thread/227469?ContentTypeID=1</link><pubDate>Fri, 03 Jan 2020 15:56:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:52353c6f-4fc1-40f9-9b9a-fdebcbc06265</guid><dc:creator>MJD093</dc:creator><description>&lt;p&gt;What exactly is the device doing when it does trip if it is possible to know. Does it trip at the same point everytime or randomly?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: WDT Times Out Prematurely ( nRF9160 )</title><link>https://devzone.nordicsemi.com/thread/227468?ContentTypeID=1</link><pubDate>Fri, 03 Jan 2020 15:54:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9e248b4b-fdec-4660-a716-6075ad2004e8</guid><dc:creator>phipi</dc:creator><description>&lt;p&gt;There&amp;#39;s no real predicable pattern. We&amp;#39;ve seen it minutes after boot and days after boot&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: WDT Times Out Prematurely ( nRF9160 )</title><link>https://devzone.nordicsemi.com/thread/227461?ContentTypeID=1</link><pubDate>Fri, 03 Jan 2020 15:28:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6c12eb21-4146-4f01-b5fb-937cd4a37851</guid><dc:creator>MJD093</dc:creator><description>&lt;p&gt;When you say 95% of the time. Over how much time on average does the issue manifest? Immediately after boot, hours, days?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: WDT Times Out Prematurely ( nRF9160 )</title><link>https://devzone.nordicsemi.com/thread/227451?ContentTypeID=1</link><pubDate>Fri, 03 Jan 2020 14:45:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:90127cd1-7f48-4adb-bd69-c8bff353bfbd</guid><dc:creator>phipi</dc:creator><description>&lt;p&gt;Yes, we have but it&amp;#39;s not always practical in our code. Also, the 10 minute timeout seems to work 95% of the time so I&amp;#39;m concerned with masking the issue by simple decreasing the period.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: WDT Times Out Prematurely ( nRF9160 )</title><link>https://devzone.nordicsemi.com/thread/227447?ContentTypeID=1</link><pubDate>Fri, 03 Jan 2020 14:32:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ea134c4e-8074-4086-831f-70d1d2d7aad2</guid><dc:creator>MJD093</dc:creator><description>&lt;p&gt;Have you tried setting the WDT to a smaller value to observe how the WDT behaves?&lt;/p&gt;
&lt;p&gt;I have WDT set to 5 seconds and observe no unexpected issues with the WDT.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>