<?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 reset with no WDT IRQ Handling</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/67407/watchdog-reset-with-no-wdt-irq-handling</link><description>Hi, 
 
 We have implemented a custom Watchdog Timeout handler, where we do the stack-dump. It has worked fine and we were able to analyze and fix the Watchdog resets. But now for one of the resets, the stack dump is missing. The RESETREAS register always</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 20 Oct 2020 11:35:49 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/67407/watchdog-reset-with-no-wdt-irq-handling" /><item><title>RE: Watchdog reset with no WDT IRQ Handling</title><link>https://devzone.nordicsemi.com/thread/275875?ContentTypeID=1</link><pubDate>Tue, 20 Oct 2020 11:35:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:42c2e772-31d7-4260-9cb1-f224fbddb6d2</guid><dc:creator>Ajith</dc:creator><description>&lt;p&gt;Thank you. I now have the stackdump.&amp;nbsp;&lt;span&gt;WDT_CONFIG_IRQ_PRIORITY&amp;nbsp; was at 7&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Watchdog reset with no WDT IRQ Handling</title><link>https://devzone.nordicsemi.com/thread/275820?ContentTypeID=1</link><pubDate>Tue, 20 Oct 2020 09:37:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ba18016d-6f2a-4639-bb97-e0401298c8e7</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Maybe you are getting a hardfault, or have you implemented your own hardfault handler as well? The weakly declared hardfault handler included in the startup file will just enter an infinite loop and thus block the WDT IRQ until the WD reset gets effectuated.&lt;/p&gt;
&lt;p&gt;Another possible explanation could be that the NRFX_WDT_CONFIG_IRQ_PRIORITY configuration is not being applied. Please check if WDT_CONFIG_IRQ_PRIORITY is defined in your sdk_config header. It will override the NRFX_WDT_CONFIG_IRQ_PRIORITY value if it is.&lt;/p&gt;
&lt;pre&gt;&lt;span&gt;&lt;br /&gt;&lt;/span&gt;&lt;span&gt;&lt;/span&gt;&lt;/pre&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>