<?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>Peripheral stops notifying data after working for some hours, then get backs to work in an hour</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/112971/peripheral-stops-notifying-data-after-working-for-some-hours-then-get-backs-to-work-in-an-hour</link><description>Hi, 
 I get a very strange issue. Below is my device information: 
 
 NCS v2.4.0, Zephyr 
 It acts as a Peripheral 
 It advertises itself, accepting connection 
 Connection parameters:
 
 interval: ~500ms 
 latency: 0 
 timeout: 4s 
 
 
 Connection TX</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 16 Jul 2024 14:34:31 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/112971/peripheral-stops-notifying-data-after-working-for-some-hours-then-get-backs-to-work-in-an-hour" /><item><title>RE: Peripheral stops notifying data after working for some hours, then get backs to work in an hour</title><link>https://devzone.nordicsemi.com/thread/494198?ContentTypeID=1</link><pubDate>Tue, 16 Jul 2024 14:34:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2a92a67f-ba90-4945-bf24-b0cfd733a3aa</guid><dc:creator>quan1328</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I figure out why it&amp;#39;s&amp;nbsp;not working. It&amp;#39;s because one of my thread was getting an infinite loop, causing the thread hang up. After a while, CPU locks up triggering the reset.&lt;/p&gt;
&lt;p&gt;Thanks.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Peripheral stops notifying data after working for some hours, then get backs to work in an hour</title><link>https://devzone.nordicsemi.com/thread/493492?ContentTypeID=1</link><pubDate>Thu, 11 Jul 2024 16:10:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bdf7cc27-f2ff-431c-a166-74349fe8f2ae</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi!&lt;/p&gt;
&lt;p&gt;1) Do you have any logs from the device?&lt;/p&gt;
&lt;p&gt;2) Does e.g. the function you call to send notifications return any errors?&lt;/p&gt;
&lt;p&gt;3) Have you confirmed that the function you use to send&amp;nbsp;&lt;span&gt;notifications&amp;nbsp;is actually being called? e.g. either through UART log-output, or e.g. toggling a debug pin&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;4) Maybe the central turned disabled the CCCD for the notifications, or that the&amp;nbsp;notifications are actually sent over-the-air but not reported to the phone application. To see what&amp;#39;s happening on-air, could you capture a sniffer trace of the issue?&amp;nbsp;&lt;a href="https://www.nordicsemi.com/Products/Development-tools/nrf-sniffer-for-bluetooth-le"&gt;https://www.nordicsemi.com/Products/Development-tools/nrf-sniffer-for-bluetooth-le&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>