<?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>nRF9160 Help needed to find reset / reboot cause</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/88970/nrf9160-help-needed-to-find-reset-reboot-cause</link><description>Hi, 
 I&amp;#39;m having issues debugging a case where the device is reset / rebooted every 1-2 days on average for some reason without any error message as to why. If any error is encountered during startup or the main loop sys_reboot(0) is called but I&amp;#39;m always</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 22 Jun 2022 19:05:31 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/88970/nrf9160-help-needed-to-find-reset-reboot-cause" /><item><title>RE: nRF9160 Help needed to find reset / reboot cause</title><link>https://devzone.nordicsemi.com/thread/373785?ContentTypeID=1</link><pubDate>Wed, 22 Jun 2022 19:05:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2ca59ce0-2604-43c7-af0d-7d5fb1487821</guid><dc:creator>Patriku</dc:creator><description>&lt;p&gt;Hi Markus,&lt;/p&gt;
&lt;p&gt;So, I&amp;#39;ve done some more testing with the extra &lt;span&gt;logging&lt;/span&gt; enabled, the first time it ran for about 5 days and the other time about 1 day before resetting. Unfortunately nothing related to the error or any hints of the reset was outputted before the reset. Still getting&amp;nbsp;RESETPIN as reset reason.&lt;/p&gt;
&lt;p&gt;I have another Thingy91 that I&amp;#39;ll do the same test on and see if i get the same issue in case it&amp;nbsp;could be some hardware related issue or something.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Do you have any other suggestions?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;/Patrik&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF9160 Help needed to find reset / reboot cause</title><link>https://devzone.nordicsemi.com/thread/373783?ContentTypeID=1</link><pubDate>Wed, 22 Jun 2022 18:50:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f3b2c2ef-2e8a-4998-9950-85b022fad441</guid><dc:creator>Patriku</dc:creator><description>[quote userid="112435" url="~/f/nordic-q-a/88970/nrf9160-help-needed-to-find-reset-reboot-cause/373178"]Integrating Memfault may be helpful for this type of problems. The library installs a fault handler that analyses the fault and stores the result in a RAM section that is not overwritten by the reboot. After reboot the data can be uploaded to the Memfault backend and analysed.[/quote]
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Hi, I&amp;#39;ll have a look into Memfault unfortunately it seems like it&amp;#39;s not available straight out of the box for&amp;nbsp;&lt;span&gt;nRF Connect SDK:&amp;nbsp;&lt;/span&gt;1.5.1, it looks like it was added in 1.6.0. Anyhow I don&amp;#39;t think it would be much work to just add the specific parts I need like the fault handler.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF9160 Help needed to find reset / reboot cause</title><link>https://devzone.nordicsemi.com/thread/373178?ContentTypeID=1</link><pubDate>Mon, 20 Jun 2022 09:13:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bae69f03-b077-4496-b933-4a0ae34be825</guid><dc:creator>asprenger</dc:creator><description>&lt;p&gt;Integrating Memfault may be helpful for this type of problems. The library installs a fault handler that analyses the fault and stores the result in a RAM section that is not overwritten by the reboot. After reboot the data can be uploaded to the Memfault backend and analysed.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF9160 Help needed to find reset / reboot cause</title><link>https://devzone.nordicsemi.com/thread/372669?ContentTypeID=1</link><pubDate>Wed, 15 Jun 2022 18:49:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1f5579e9-0818-431d-b246-7b5fb8bd12a0</guid><dc:creator>Patriku</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
[quote userid="100109" url="~/f/nordic-q-a/88970/nrf9160-help-needed-to-find-reset-reboot-cause/372574#372574"]&lt;span&gt;Interestingly enough, the Thingy91 has no reset pin connected by default. Have you done any modifications to the board, maybe?&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;[/quote]
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;No hardware modifications has been done, it&amp;#39;s straight out of the box. Anyhow I see now in the documentation regarding RESETREAS register that&amp;nbsp;it should be cleared, which I haven&amp;#39;t been doing.&lt;/p&gt;
[quote userid="100109" url="~/f/nordic-q-a/88970/nrf9160-help-needed-to-find-reset-reboot-cause/372574#372574"]&lt;p&gt;&lt;span&gt;What I probably would do at this point is to enable debug logging for the libraries/modules your application is using, like e.g.&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.0.0/kconfig/index.html#CONFIG_NRF_MODEM_LIB_LOG_LEVEL_DBG"&gt;Modem library&lt;/a&gt;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.5.1/kconfig/CONFIG_AT_CMD_LOG_LEVEL_DBG.html#cmdoption-arg-CONFIG_AT_CMD_LOG_LEVEL_DBG"&gt;AT command interface&lt;/a&gt; &amp;amp; &lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.5.1/kconfig/CONFIG_AT_NOTIF_LOG_LEVEL_DBG.html#cmdoption-arg-CONFIG_AT_NOTIF_LOG_LEVEL_DBG"&gt;notifications&lt;/a&gt;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Your sensor layer&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;...&lt;/span&gt;&lt;/li&gt;&lt;/ul&gt;[/quote]
&lt;p&gt;I&amp;#39;ll enable some more logging and get back to you.&lt;/p&gt;
&lt;p&gt;/Patrik&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF9160 Help needed to find reset / reboot cause</title><link>https://devzone.nordicsemi.com/thread/372574?ContentTypeID=1</link><pubDate>Wed, 15 Jun 2022 12:37:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4f10cfe7-f576-4e90-90ef-7cfc084a0c08</guid><dc:creator>Albrecht Markus Schellenberger</dc:creator><description>&lt;p&gt;&lt;span&gt;Hello Patrik,&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
[quote user=""]When getting the reset reason with &lt;strong&gt;nrf_power_resetreas_get(NRF_POWER)&lt;/strong&gt; I get &lt;strong&gt;RESETPIN (&lt;/strong&gt;NRF_POWER_RESETREAS_RESETPIN_MASK&lt;strong&gt;)&lt;/strong&gt;[/quote]
&lt;p&gt;&lt;span&gt;Interestingly enough, the Thingy91 has no reset pin connected by default. Have you done any modifications to the board, maybe?&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
[quote user=""]Would a modem trace provide some details or is it only used for analyzing the communication between the device and the LTE network?[/quote]
&lt;p&gt;&lt;span&gt;A modem trace helps to analyse what the modem does, but even though it would&amp;nbsp;crash it should not cause the application core to crash as well, at least not right away.&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;
[quote user=""]Do you have any additional debugging options I could enable to hopefully get some more insight into why it might reset?[/quote]
&lt;p&gt;&lt;span&gt;What I probably would do at this point is to enable debug logging for the libraries/modules your application is using, like e.g.&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span&gt;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.0.0/kconfig/index.html#CONFIG_NRF_MODEM_LIB_LOG_LEVEL_DBG"&gt;Modem library&lt;/a&gt;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.5.1/kconfig/CONFIG_AT_CMD_LOG_LEVEL_DBG.html#cmdoption-arg-CONFIG_AT_CMD_LOG_LEVEL_DBG"&gt;AT command interface&lt;/a&gt; &amp;amp; &lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.5.1/kconfig/CONFIG_AT_NOTIF_LOG_LEVEL_DBG.html#cmdoption-arg-CONFIG_AT_NOTIF_LOG_LEVEL_DBG"&gt;notifications&lt;/a&gt;&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;Your sensor layer&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span&gt;...&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;span&gt;Maybe they can provide you with some more information. You probably shouldn’t enable them all at once though, as the output can be huge.&lt;/span&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Regards,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Markus&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>