<?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>SD Assert fault at address 0x016ADA</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/107342/sd-assert-fault-at-address-0x016ada</link><description>Hi, 
 I have set up a network with 52 nodes that communicate via a vendor model. After a few days, one or more devices have a hardfault and reboot 
 SD Assert fault at address 0x016ADA 
 Can you help me what is triggering this error? 
 Chip nrf52840 SDK</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 01 Feb 2024 09:01:10 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/107342/sd-assert-fault-at-address-0x016ada" /><item><title>RE: SD Assert fault at address 0x016ADA</title><link>https://devzone.nordicsemi.com/thread/467081?ContentTypeID=1</link><pubDate>Thu, 01 Feb 2024 09:01:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:880f516e-4d6f-4092-b768-ddb6efcbfb42</guid><dc:creator>Michael Moser</dc:creator><description>&lt;p&gt;I will change it.&amp;nbsp;Unfortunately, I currently don&amp;#39;t have an installation where I can reproduce this problem.&lt;/p&gt;
&lt;p&gt;Thanks Michael&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SD Assert fault at address 0x016ADA</title><link>https://devzone.nordicsemi.com/thread/465585?ContentTypeID=1</link><pubDate>Tue, 23 Jan 2024 13:28:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8bf2bc3d-336f-49dd-885e-ed8fbd3ad0b0</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Try increasing TIMESLOT_END_SAFETY_MARGIN_US in steps of 100 us up to 1000 us, and see if that improves&amp;nbsp;the behavior. (\mesh\core\include\timeslot.h)&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SD Assert fault at address 0x016ADA</title><link>https://devzone.nordicsemi.com/thread/465101?ContentTypeID=1</link><pubDate>Fri, 19 Jan 2024 15:25:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:746d1174-8aec-4381-b462-42b63b5d04c6</guid><dc:creator>Michael Moser</dc:creator><description>&lt;p&gt;Hallo Sigurd&lt;/p&gt;
&lt;p&gt;The&amp;nbsp;&lt;span&gt;NRF_SDH_CLOCK_LF_ACCURACY is set to 1 (500ppm)&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;We are using the internal LF RC oscilator.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;// &amp;lt;h&amp;gt; Clock - SoftDevice clock configuration

//==========================================================
// &amp;lt;o&amp;gt; NRF_SDH_CLOCK_LF_SRC  - SoftDevice clock source.
 
// &amp;lt;0=&amp;gt; NRF_CLOCK_LF_SRC_RC 
// &amp;lt;1=&amp;gt; NRF_CLOCK_LF_SRC_XTAL 
// &amp;lt;2=&amp;gt; NRF_CLOCK_LF_SRC_SYNTH 

#ifndef NRF_SDH_CLOCK_LF_SRC
#define NRF_SDH_CLOCK_LF_SRC 0
#endif

// &amp;lt;o&amp;gt; NRF_SDH_CLOCK_LF_RC_CTIV - SoftDevice calibration timer interval. 
#ifndef NRF_SDH_CLOCK_LF_RC_CTIV
#define NRF_SDH_CLOCK_LF_RC_CTIV 16
#endif

// &amp;lt;o&amp;gt; NRF_SDH_CLOCK_LF_RC_TEMP_CTIV - SoftDevice calibration timer interval under constant temperature. 
// &amp;lt;i&amp;gt; How often (in number of calibration intervals) the RC oscillator shall be calibrated
// &amp;lt;i&amp;gt;  if the temperature has not changed.

#ifndef NRF_SDH_CLOCK_LF_RC_TEMP_CTIV
#define NRF_SDH_CLOCK_LF_RC_TEMP_CTIV 0
#endif

// &amp;lt;o&amp;gt; NRF_SDH_CLOCK_LF_ACCURACY  - External clock accuracy used in the LL to compute timing.
 
// &amp;lt;0=&amp;gt; NRF_CLOCK_LF_ACCURACY_250_PPM 
// &amp;lt;1=&amp;gt; NRF_CLOCK_LF_ACCURACY_500_PPM 
// &amp;lt;2=&amp;gt; NRF_CLOCK_LF_ACCURACY_150_PPM 
// &amp;lt;3=&amp;gt; NRF_CLOCK_LF_ACCURACY_100_PPM 
// &amp;lt;4=&amp;gt; NRF_CLOCK_LF_ACCURACY_75_PPM 
// &amp;lt;5=&amp;gt; NRF_CLOCK_LF_ACCURACY_50_PPM 
// &amp;lt;6=&amp;gt; NRF_CLOCK_LF_ACCURACY_30_PPM 
// &amp;lt;7=&amp;gt; NRF_CLOCK_LF_ACCURACY_20_PPM 
// &amp;lt;8=&amp;gt; NRF_CLOCK_LF_ACCURACY_10_PPM 
// &amp;lt;9=&amp;gt; NRF_CLOCK_LF_ACCURACY_5_PPM 
// &amp;lt;10=&amp;gt; NRF_CLOCK_LF_ACCURACY_2_PPM 
// &amp;lt;11=&amp;gt; NRF_CLOCK_LF_ACCURACY_1_PPM 

#ifndef NRF_SDH_CLOCK_LF_ACCURACY
#define NRF_SDH_CLOCK_LF_ACCURACY 1
#endif
&lt;/pre&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Regards Michael&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SD Assert fault at address 0x016ADA</title><link>https://devzone.nordicsemi.com/thread/465023?ContentTypeID=1</link><pubDate>Fri, 19 Jan 2024 12:00:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4b324e14-187a-4f39-bdf9-1a8ac83abea2</guid><dc:creator>Sigurd</dc:creator><description>[quote userid="101880" url="~/f/nordic-q-a/107342/sd-assert-fault-at-address-0x016ada/464190"]The hard fault address is different from the hard fault address in the case 98787. 0x016ADA instead of&amp;nbsp;&lt;span&gt;0x15BA4.&lt;/span&gt;[/quote]
&lt;p&gt;It&amp;#39;s only different because it&amp;#39;s a different SoftDevice version, but both points to the same assert in the code.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Are you using internal LF RC oscillator&amp;nbsp;for LF clock, or do you have LF crystal?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;What is&amp;nbsp;NRF_SDH_CLOCK_LF_ACCURACY set to ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SD Assert fault at address 0x016ADA</title><link>https://devzone.nordicsemi.com/thread/464643?ContentTypeID=1</link><pubDate>Wed, 17 Jan 2024 15:05:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b09a46be-6cf6-477b-9433-eb3edd83dff0</guid><dc:creator>Michael Moser</dc:creator><description>&lt;p&gt;Any proposal.&lt;br /&gt;What is the reason for this SD assert at the address&amp;nbsp;&lt;span&gt;0x016ADA?&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SD Assert fault at address 0x016ADA</title><link>https://devzone.nordicsemi.com/thread/464190?ContentTypeID=1</link><pubDate>Mon, 15 Jan 2024 13:29:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:74b665ab-541b-4af4-b254-8acd797954da</guid><dc:creator>Michael Moser</dc:creator><description>&lt;p&gt;Hello Sigurd&lt;/p&gt;
&lt;p&gt;Thanks for your answer.&lt;/p&gt;
&lt;p&gt;The hard fault address is different from the hard fault address in the case 98787. 0x016ADA instead of&amp;nbsp;&lt;span&gt;0x15BA4.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;I read through the case but I didn&amp;#39;t find a solution to this problem.&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&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;Michael&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SD Assert fault at address 0x016ADA</title><link>https://devzone.nordicsemi.com/thread/464002?ContentTypeID=1</link><pubDate>Fri, 12 Jan 2024 14:19:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ffba834c-ed59-4f11-a237-a5f4a95f5a24</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi!&lt;/p&gt;
&lt;p&gt;It&amp;#39;s the same assert that is discussed in this case here:&amp;nbsp;&lt;a id="i1" href="https://devzone.nordicsemi.com/f/nordic-q-a/98787/mesh-sdk-pb-remote---device-crash-when-provisionning"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/98787/mesh-sdk-pb-remote---device-crash-when-provisionning&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>