<?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>Assertion fail after initializing task watchdog with hardware watchdog fallback</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/118591/assertion-fail-after-initializing-task-watchdog-with-hardware-watchdog-fallback</link><description>I&amp;#39;m using nRF Connect SDK v2.7.0 with v2.7.0 toolchain to program a device with nRF52840 SoC. 
 When configuring task watchdog timer with hardware fallback an assertion fails in nrfx_wdt.c:277. 
 In the main function the task watchdog timer is configured</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 05 Mar 2025 12:56:43 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/118591/assertion-fail-after-initializing-task-watchdog-with-hardware-watchdog-fallback" /><item><title>RE: Assertion fail after initializing task watchdog with hardware watchdog fallback</title><link>https://devzone.nordicsemi.com/thread/525978?ContentTypeID=1</link><pubDate>Wed, 05 Mar 2025 12:56:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5216dd35-b5c9-43ee-98ec-644d93b7f3e4</guid><dc:creator>KacperF</dc:creator><description>&lt;p&gt;I couldn&amp;#39;t resolve it by changing the stack size, I just used the hardware watchdog API instead of task watchdog.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Assertion fail after initializing task watchdog with hardware watchdog fallback</title><link>https://devzone.nordicsemi.com/thread/525825?ContentTypeID=1</link><pubDate>Tue, 04 Mar 2025 20:36:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5ee6c975-fff0-4d31-8d4b-0996b5410ba3</guid><dc:creator>GabrielDS</dc:creator><description>&lt;p&gt;Same issue.&amp;nbsp; What did you find to solve it?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Assertion fail after initializing task watchdog with hardware watchdog fallback</title><link>https://devzone.nordicsemi.com/thread/521336?ContentTypeID=1</link><pubDate>Tue, 04 Feb 2025 14:31:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1043c6aa-5a47-484c-8eb7-25b17501ee0f</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Seems like an assert on stack overflow error, try increasing main thread stack size&amp;nbsp;&lt;span&gt;CONFIG_MAIN_STACK_SIZE to something bigger.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Also please enable the debug logs in your prj.conf as below&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;pre class="ui-code" data-mode="text"&gt;Here are the config options I typically use:

# Debugging configuration
CONFIG_THREAD_NAME=y
CONFIG_THREAD_ANALYZER=y
CONFIG_THREAD_ANALYZER_AUTO=y
CONFIG_THREAD_ANALYZER_RUN_UNLOCKED=y
CONFIG_THREAD_ANALYZER_USE_PRINTK=y

# add asserts
CONFIG_ASSERT=y
CONFIG_ASSERT_VERBOSE=y
CONFIG_ASSERT_NO_COND_INFO=n
CONFIG_ASSERT_NO_MSG_INFO=n
CONFIG_RESET_ON_FATAL_ERROR=n
CONFIG_THREAD_NAME=y&lt;/pre&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;After prestine built with the above changes, please provide the logs again.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>