https://devzone.nordicsemi.com/f/nordic-q-a/58753/mesh-fails-to-publish-and-relay-packets-until-rtc-timer-wraps-aroundUsing Mesk v3.1 on an 52840 chip. We&#39;ve noticed that after running our app for several hours or days that our models become unable to send messages for a period of ~8.5 minutes. Once the first publication fails (error code 0x4) all further publicationsen-USTelligent Community 13Thu, 12 Mar 2020 16:19:24 GMThttps://devzone.nordicsemi.com/thread/239593?ContentTypeID=1Thu, 12 Mar 2020 16:19:24 GMT137ad170-7792-4731-bb38-c0d22fbe4515:41d446b6-5c5b-4d9d-b928-5dda7672ea33pquevedo<p>In case anyone else ever runs into this issue here is the patch we applied that solved the problem for us after 96 hours of testing.</p> <p>Shouldn&#39;t need the recovery mechanism we put in as the modifications to the timer_start and ovflw_handle appear to have stopped the issue from occurring but we left it in as good measure and because we confirmed it actually recovered publication.&nbsp;<a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/fixes_2D00_timer_2D00_not_2D00_firing.patch">devzone.nordicsemi.com/.../fixes_2D00_timer_2D00_not_2D00_firing.patch</a></p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/238576?ContentTypeID=1Fri, 06 Mar 2020 15:26:05 GMT137ad170-7792-4731-bb38-c0d22fbe4515:08ea6e73-5eda-4613-aead-14e65950cb84pquevedo<p>The models publish periodically at a random interval between 1-3 seconds and in response to certain requests.</p> <p>On average we typically see 4-5&nbsp; publishes in total per second (all unsegmented with no retransmission configured&nbsp;at the access layer).</p> <p>When this issue occurs it does not seem correlated to the number of messages sent or the packet transmission rate within the last couple seconds. In some cases we have only sent 1 or 2 messages within the last second, in other cases we have sent 5 messages.&nbsp;</p> <p>Here is a snippet of the last couple seconds before the issue starts. timestamps are in RTC ticks.</p> <p><pre class="ui-code" data-mode="text">[05-03-2020 17:09:29][122e][INFO] 3385545&gt; access.c: 1d5f:c5 [05-03-2020 17:09:30][122f][INFO] 3388825&gt; access.c: 1d5f:c6 [05-03-2020 17:09:30][1230][INFO] 3418319&gt; access.c: 1d5f:c5 [05-03-2020 17:09:31][1231][INFO] 3418749&gt; access.c: 1d5f:c4 [05-03-2020 17:09:31][1232][INFO] 3421592&gt; access.c: 1d5f:c6 [05-03-2020 17:09:31][1233][INFO] 3451085&gt; access.c: 1d5f:c5 [05-03-2020 17:09:32][1234][INFO] 3454362&gt; access.c: 1d5f:c6 [05-03-2020 17:09:32][1235][INFO] 3483855&gt; access.c: 1d5f:c5 [05-03-2020 17:09:33][1236][INFO] 3487138&gt; access.c: 1d5f:c6 [05-03-2020 17:09:33][1237][INFO] 3511124&gt; access.c: 1d5f:c1 [05-03-2020 17:09:34][1238][INFO] 3511145&gt; access.c: 1d5f:c2 [05-03-2020 17:09:34][1239][INFO] 3511166&gt; access.c: 1d5f:c3 [05-03-2020 17:09:34][123a][INFO] 3516625&gt; access.c: 1d5f:c5 [05-03-2020 17:09:34][123b][INFO] 3519902&gt; access.c: 1d5f:c6 [05-03-2020 17:09:34][123e][INFO] 3547080&gt; access.c: 1d5f:c1 [05-03-2020 17:09:35][123f][INFO] 3549395&gt; access.c: 1d5f:c5 [05-03-2020 17:09:35][1240][ERROR] 3549405&gt; core_tx_adv.c: packet_alloc no mem cnt 1 tevt @ 0x200086d4 ts 0xbd7eb362 </pre></p> <p>The same log but with the timestamp post-processed and in milliseconds showing the delta between logs</p> <p><pre class="ui-code" data-mode="text"> [05-03-2020 17:09:29][122e][INFO] 103318.634[+899.902] access.c: 1d5f:c5 [05-03-2020 17:09:30][122f][INFO] 103418.732[+100.098] access.c: 1d5f:c6 [05-03-2020 17:09:30][1230][INFO] 104318.817[+900.085] access.c: 1d5f:c5 [05-03-2020 17:09:31][1231][INFO] 104331.940[+13.123] access.c: 1d5f:c4 [05-03-2020 17:09:31][1232][INFO] 104418.701[+86.761] access.c: 1d5f:c6 [05-03-2020 17:09:31][1233][INFO] 105318.756[+900.055] access.c: 1d5f:c5 [05-03-2020 17:09:32][1234][INFO] 105418.762[+100.006] access.c: 1d5f:c6 [05-03-2020 17:09:32][1235][INFO] 106318.817[+900.055] access.c: 1d5f:c5 [05-03-2020 17:09:33][1236][INFO] 106419.006[+100.189] access.c: 1d5f:c6 [05-03-2020 17:09:33][1237][INFO] 107151.001[+731.995] access.c: 1d5f:c1 [05-03-2020 17:09:34][1238][INFO] 107151.642[+0.641] access.c: 1d5f:c2 [05-03-2020 17:09:34][1239][INFO] 107152.283[+0.641] access.c: 1d5f:c3 [05-03-2020 17:09:34][123a][INFO] 107318.878[+166.595] access.c: 1d5f:c5 [05-03-2020 17:09:34][123b][INFO] 107418.884[+100.006] access.c: 1d5f:c6 [05-03-2020 17:09:34][123e][INFO] 108248.291[+746.948] access.c: 1d5f:c1 [05-03-2020 17:09:35][123f][INFO] 108318.939[+70.648] access.c: 1d5f:c5 [05-03-2020 17:09:35][1240][ERROR] 108319.244[+0.305] core_tx_adv.c: packet_alloc no mem cnt 1 tevt @ 0x200086d4 ts 0xbd7eb362 </pre></p> <p></p> <p>Here is a log from another device with a slower packet rate prior to the event (timestamps post-processed to milliseconds)</p> <p><pre class="ui-code" data-mode="text"> [05-03-2020 22:42:04][9e59][INFO] 97135.223[+162.994] access.c: 1d5f:c6 [05-03-2020 22:42:05][9e5a][INFO] 97535.095[+399.872] access.c: 1d5f:c5 [05-03-2020 22:42:05][9e5b][INFO] 98035.126[+500.031] access.c: 1d5f:c6 [05-03-2020 22:42:05][9e5c][INFO] 98135.193[+100.067] access.c: 1d5f:c6 [05-03-2020 22:42:06][9e5d][INFO] 98535.156[+399.963] access.c: 1d5f:c5 [05-03-2020 22:42:06][9e5e][INFO] 99035.187[+500.031] access.c: 1d5f:c6 [05-03-2020 22:42:06][9e5f][INFO] 99135.193[+100.006] access.c: 1d5f:c6 [05-03-2020 22:42:07][9e60][INFO] 99535.217[+400.024] access.c: 1d5f:c5 [05-03-2020 22:42:07][9e61][INFO] 100035.248[+500.031] access.c: 1d5f:c6 [05-03-2020 22:42:08][9e62][INFO] 100135.284[+100.037] access.c: 1d5f:c6 [05-03-2020 22:42:08][9e63][INFO] 100535.278[+399.994] access.c: 1d5f:c5 [05-03-2020 22:42:08][9e64][INFO] 101035.309[+500.031] access.c: 1d5f:c6 [05-03-2020 22:42:08][9e65][INFO] 101135.315[+100.006] access.c: 1d5f:c6 [05-03-2020 22:42:09][9e66][ERROR] 101135.559[+0.244] core_tx_adv.c: packet_alloc no mem cnt 1 tevt @ 0x200086d4 ts 0x633a29ef</pre></p> <p>We suspect its the timer_start() routine in core/src/timer.c writing a stale value into the CC1 register of RTC1. We&#39;re trying some more experiments to test this.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/238569?ContentTypeID=1Fri, 06 Mar 2020 15:03:44 GMT137ad170-7792-4731-bb38-c0d22fbe4515:7899e303-cd97-4794-b113-a70139d6ac5bHung Bui<p>Hi,&nbsp;</p> <p>We will have to check with the R&amp;D team if they can find any issue related to this.&nbsp;</p> <p>Could you give some more information regarding your model ? Do you send a lot of data ? What&#39;s the data rate ?&nbsp;</p> <p><br />Would the same issue can be observed on the light switch example ? Have you tried to test that ?&nbsp;</p><div style="clear:both;"></div>