<?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>nrf52832 software/firmware &amp;quot;lock up&amp;quot;</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/99309/nrf52832-software-firmware-lock-up</link><description>Hi All, We are in pre-production stage of a program using the nrf52832 module. A small sample of our devices exhibit an issue where they will randomly appear to &amp;quot;lock up&amp;quot;. I will attempt to explain what this means. When the device locks up, any BLE advertising</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 04 May 2023 08:56:05 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/99309/nrf52832-software-firmware-lock-up" /><item><title>RE: nrf52832 software/firmware "lock up"</title><link>https://devzone.nordicsemi.com/thread/423712?ContentTypeID=1</link><pubDate>Thu, 04 May 2023 08:56:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:94537b34-c5cf-4ba1-91a6-56c3a2ca6c42</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
[quote user="dlewis"]As for the watchdog timer, that is an avenue we are looking into to relieve some of the negative effects, but we still can hopefully determine the exact cause so that we can eliminate it all together.&amp;nbsp;[/quote]
&lt;p&gt;Assuming that the&amp;nbsp;watchdog will reset the device when this &amp;quot;lock-up&amp;quot; happens, you can then use the code in this post here to save the location of the cpu program counter where the code was running when the watchdog reset happened, and then use addr2line with the .elf file to find the exact code line:&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/30075/saving-the-location-of-watchdog-timeout"&gt;Saving the location of Watchdog timeout&lt;/a&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52832 software/firmware "lock up"</title><link>https://devzone.nordicsemi.com/thread/423618?ContentTypeID=1</link><pubDate>Wed, 03 May 2023 17:10:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:555e779d-c0d4-46da-9f84-222514047608</guid><dc:creator>dlewis</dc:creator><description>&lt;p&gt;Thanks for the response! I&amp;#39;d have to check to confirm that &lt;span&gt;CONFIG_RESET_ON_FATAL_ERROR is set, but I believe it is because any other faults we experienced previously would automatically stop the debugger/restart the code in production configuration. As for the watchdog timer, that is an avenue we are looking into to relieve some of the negative effects, but we still can hopefully determine the exact cause so that we can eliminate it all together.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf52832 software/firmware "lock up"</title><link>https://devzone.nordicsemi.com/thread/423401?ContentTypeID=1</link><pubDate>Tue, 02 May 2023 21:37:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:64036402-dd8a-4055-ba88-14764aa7f0f4</guid><dc:creator>nordicator_prim3</dc:creator><description>&lt;p&gt;I don&amp;#39;t have a good way for you to figure out what&amp;#39;s actually happening but I do have a similar problem to you (only in that I have a strange bug that happens very rarely and can&amp;#39;t recreate it). It would be great to actually find the bug or to find out whats really happening, but I&amp;#39;ve at least found a couple good things that helped me at least detect the inactivity and ensure that a reset occurs.&lt;/p&gt;
&lt;p&gt;Do you have CONFIG_RESET_ON_FATAL_ERROR set to yes? This would make sure that if there was a hard fault then the device is sure to reset instead of hang and wait.&lt;/p&gt;
&lt;p&gt;Also, check out using the &lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.0.0/zephyr/services/task_wdt/index.html"&gt;zephyr watchdog timers&lt;/a&gt;. You can update this timer in a loop or based off of an interrupt from some preipheral that you expect to constantly see. If the watchdog timer doesn&amp;#39;t get updated in a timely fashion (like if the thread that updates the timer stops running) then you can configure it to hard reset the device.&lt;/p&gt;
&lt;p&gt;Good luck, I know these kinds of problems are annoying!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>