<?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>unable to go into UART interrupt after 6 minutes running</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/15330/unable-to-go-into-uart-interrupt-after-6-minutes-running</link><description>Hello, 
 I am using nrf51822 doing projects. I met an issuse which is that at the first 6 minutes, it can normaly go into UART interrupt and run subroutine successfully. But after 6 minutes running, it can not go into UART interrupt again. I use Keil</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 03 Aug 2016 13:55:35 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/15330/unable-to-go-into-uart-interrupt-after-6-minutes-running" /><item><title>RE: unable to go into UART interrupt after 6 minutes running</title><link>https://devzone.nordicsemi.com/thread/58590?ContentTypeID=1</link><pubDate>Wed, 03 Aug 2016 13:55:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b5ca84d0-f706-4725-85af-66cc2d8ca617</guid><dc:creator>Ole Bauck</dc:creator><description>&lt;p&gt;Do you know where in the code you are &amp;quot;stuck&amp;quot;? Go into debug mode and stop the execution when you don&amp;#39;t go into uart interrupt or main anymore.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: unable to go into UART interrupt after 6 minutes running</title><link>https://devzone.nordicsemi.com/thread/58593?ContentTypeID=1</link><pubDate>Wed, 03 Aug 2016 01:29:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3f2f230c-1585-4d3f-aa5b-5871d220b8bb</guid><dc:creator>sunnyjet16</dc:creator><description>&lt;p&gt;I masked some subroutines such as read external memory and key scan. I&amp;#39;m not sure if subrountines causes this issue. I use a variable to test the uart interrupt. When enterring the subroutine, the variable will have an increment. When the variable stops increasing, it means it does not enter interrupt.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: unable to go into UART interrupt after 6 minutes running</title><link>https://devzone.nordicsemi.com/thread/58592?ContentTypeID=1</link><pubDate>Wed, 27 Jul 2016 08:41:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c61fc5fb-4e08-4e84-bcde-def8231eb099</guid><dc:creator>Ole Bauck</dc:creator><description>&lt;p&gt;Which functions did you mask out? You are sure that the application is not hitting an error condition and freezes, see &lt;a href="https://devzone.nordicsemi.com/question/60125/my-device-is-freezing-and-restarting/"&gt;here&lt;/a&gt;?&lt;/p&gt;
&lt;p&gt;How do you check that the interrupt is not entered? Blinking a LED?&lt;/p&gt;
&lt;p&gt;System parameters do you mean the UART registers? You can see those if you are running the debugger and stops the code. The NRF_UART0-&amp;gt;EVENTS_RXDRDY will be set when data is received on the UART, and if interrupt is enabled for this event (should be if you are to enter the interrupt when something is received) then when this is set you should enter the interrupt. You can use PPI to toggle a LED when this event happens.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: unable to go into UART interrupt after 6 minutes running</title><link>https://devzone.nordicsemi.com/thread/58591?ContentTypeID=1</link><pubDate>Wed, 27 Jul 2016 01:22:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a9b345cb-3e48-4ab2-a68a-5eef39f416db</guid><dc:creator>sunnyjet16</dc:creator><description>&lt;p&gt;Hi Ole,
I did not use sd_power_system_off(). Yesterday, I masked some functions and it can run continuously about 1 hours without issue. But after one hour, it can not enter mainloop and UART interrupt again.
Is there any methods to oversee the system parameters?
Regards
Alex&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: unable to go into UART interrupt after 6 minutes running</title><link>https://devzone.nordicsemi.com/thread/58589?ContentTypeID=1</link><pubDate>Tue, 26 Jul 2016 09:40:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cbe4004c-718e-4f08-8f18-24651df4b6e8</guid><dc:creator>Ole Bauck</dc:creator><description>&lt;p&gt;Do you go to system OFF mode for example with &lt;code&gt;sd_power_system_off()&lt;/code&gt;? The examples do this by default after 3 minutes (APP_ADV_TIMEOUT_IN_SECONDS).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>