<?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>Provisioning Assert with 0x24A42 last call address using Softdevice 6.1.1</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/43742/provisioning-assert-with-0x24a42-last-call-address-using-softdevice-6-1-1</link><description>Hi. 
 
 I use a modified lightswitch server application with Nordic SDK 15.2, Mesh SDK 3.1.0 and Softdevice 6.1.1. 
 
 During provisioning I experience a software assert with following call stack address prior assert handling: 
 
 0x24A42 
 
 The address</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 11 Mar 2019 13:56:08 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/43742/provisioning-assert-with-0x24a42-last-call-address-using-softdevice-6-1-1" /><item><title>RE: Provisioning Assert with 0x24A42 last call address using Softdevice 6.1.1</title><link>https://devzone.nordicsemi.com/thread/175357?ContentTypeID=1</link><pubDate>Mon, 11 Mar 2019 13:56:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d74c0742-8e63-4587-9cb5-75941f646d0d</guid><dc:creator>Bj&amp;#248;rn Kvaale</dc:creator><description>&lt;p&gt;Sorry for the delayed response. I have been on vacation for a week. I saw that you opened a new case with case ID: 224805. I suggest you continue there.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Provisioning Assert with 0x24A42 last call address using Softdevice 6.1.1</title><link>https://devzone.nordicsemi.com/thread/174551?ContentTypeID=1</link><pubDate>Wed, 06 Mar 2019 12:59:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e4fa738a-1f27-4106-88ed-32b6f78f50c1</guid><dc:creator>Ronny L</dc:creator><description>&lt;p&gt;No, I don&amp;#39;t.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Provisioning Assert with 0x24A42 last call address using Softdevice 6.1.1</title><link>https://devzone.nordicsemi.com/thread/172253?ContentTypeID=1</link><pubDate>Thu, 21 Feb 2019 09:23:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:60ee131a-1c25-4351-b04c-6bb890b2a820</guid><dc:creator>Bj&amp;#248;rn Kvaale</dc:creator><description>&lt;p&gt;Do you receive any other logging information with error codes such as from app_error_weak.c? Maybe &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/36002/mesh-error-code-4"&gt;this devzone case&lt;/a&gt; could be helpful.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Provisioning Assert with 0x24A42 last call address using Softdevice 6.1.1</title><link>https://devzone.nordicsemi.com/thread/171969?ContentTypeID=1</link><pubDate>Tue, 19 Feb 2019 18:18:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:10f7fd9b-ecf2-478f-a65a-2ee84fef43d4</guid><dc:creator>Ronny L</dc:creator><description>&lt;p&gt;Any idea?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Provisioning Assert with 0x24A42 last call address using Softdevice 6.1.1</title><link>https://devzone.nordicsemi.com/thread/171460?ContentTypeID=1</link><pubDate>Fri, 15 Feb 2019 16:31:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:58eaa494-6d85-4215-a71f-ed36e12a9a80</guid><dc:creator>Ronny L</dc:creator><description>&lt;p&gt;Thanks for the feedback.&lt;/p&gt;
&lt;p&gt;We have nodes running and functional but have a team which experiences the described software assert frequently.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;This reflects to some unknown reason why the software assert is occurring frequently ( Every time ) or rarely.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m going to look into the addr2line tool. I assume that it will show that the software assert is happening during the ldr of the NVIC address but double checking is time wisely spent.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best Regards,&lt;/p&gt;
&lt;p&gt;Ronny&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Provisioning Assert with 0x24A42 last call address using Softdevice 6.1.1</title><link>https://devzone.nordicsemi.com/thread/171388?ContentTypeID=1</link><pubDate>Fri, 15 Feb 2019 12:50:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e29a1393-8b3f-4d8e-b362-51cb9112e840</guid><dc:creator>Bj&amp;#248;rn Kvaale</dc:creator><description>&lt;p&gt;You can try to use the &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/25886/70-mesh-assert-at-0x00023680"&gt;addr2line tool &lt;/a&gt;to figure out where this assert occurs. Are you using a 52 DK to test this? If you have not already seen &lt;a href="https://www.youtube.com/watch?v=XthbU9NP0Yg&amp;amp;t=157s"&gt;this video&lt;/a&gt;, it may also be helpful.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>