<?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>nrf mesh Softdevice assert: 88996:0</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/71720/nrf-mesh-softdevice-assert-88996-0</link><description>Hello there, 
 we get the following assert: 
 &amp;quot;00&amp;gt; &amp;lt;t: 480881&amp;gt;, app_error_weak.c, 98, Softdevice assert: 88996:0&amp;quot; 
 
 The board is rebooting constantly after 3 ... 7 minutes of work. What could be that 88996? 
 What is in use: 
 - nrf sdk 17 
 - nrf mesh</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 22 Feb 2021 10:30:46 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/71720/nrf-mesh-softdevice-assert-88996-0" /><item><title>RE: nrf mesh Softdevice assert: 88996:0</title><link>https://devzone.nordicsemi.com/thread/295531?ContentTypeID=1</link><pubDate>Mon, 22 Feb 2021 10:30:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cedfcd62-cd31-42be-9932-8154ba93a256</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;It&amp;#39;s pretty strange that changing the tx_power in mesh can cause a softdevice assert.&amp;nbsp;&lt;br /&gt;I tried to test the same but I couldn&amp;#39;t reproduce the issue. If you test on light switch example do you see the same problem ?&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;Also I don&amp;#39;t think changing the TX_POWER in scanner.c would have any effect. Could you please test with only modification in advertiser.c ?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;In addition, could you verify that if you change the TX_POWER back to 0dbm the problem will disappear ?&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf mesh Softdevice assert: 88996:0</title><link>https://devzone.nordicsemi.com/thread/295456?ContentTypeID=1</link><pubDate>Sun, 21 Feb 2021 10:16:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b3fbf3b3-032e-44f8-90bc-842633e34a82</guid><dc:creator>Oleh</dc:creator><description>&lt;p&gt;we modified two files: advertiser.c and scanner.c&lt;/p&gt;
&lt;p&gt;as follows:&lt;/p&gt;
&lt;p&gt;&lt;img src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1613902527757v1.png" alt=" " /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf mesh Softdevice assert: 88996:0</title><link>https://devzone.nordicsemi.com/thread/295455?ContentTypeID=1</link><pubDate>Sun, 21 Feb 2021 07:07:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dfe6c191-1bd7-41f4-8794-2ab9268716aa</guid><dc:creator>ipshiv</dc:creator><description>&lt;p&gt;static inline void set_default_broadcast_configuration(broadcast_t * p_broadcast)&lt;/p&gt;
&lt;p&gt;{&lt;/p&gt;
&lt;p&gt;&amp;nbsp; &amp;nbsp; p_broadcast-&amp;gt;params.access_address = BEARER_ACCESS_ADDR_DEFAULT;&lt;/p&gt;
&lt;p&gt;&amp;nbsp; &amp;nbsp; p_broadcast-&amp;gt;params.radio_config.payload_maxlen = RADIO_CONFIG_ADV_MAX_PAYLOAD_SIZE;&lt;/p&gt;
&lt;p&gt;&amp;nbsp; &amp;nbsp; p_broadcast-&amp;gt;params.radio_config.radio_mode = RADIO_MODE_BLE_1MBIT;&lt;/p&gt;
&lt;p&gt;&amp;nbsp; &amp;nbsp; p_broadcast-&amp;gt;params.radio_config.tx_power = RADIO_POWER;&lt;/p&gt;
&lt;p&gt;}&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p style="text-align:left;"&gt;RADIO_POWER dafines at compilation. For tests neg12, for production pos8&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf mesh Softdevice assert: 88996:0</title><link>https://devzone.nordicsemi.com/thread/295454?ContentTypeID=1</link><pubDate>Sun, 21 Feb 2021 07:07:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ff89e4a4-80ac-48fd-8a65-2e1ee1aba9c8</guid><dc:creator>ipshiv</dc:creator><description>&lt;p&gt;static inline void set_default_broadcast_configuration(broadcast_t * p_broadcast)&lt;/p&gt;
&lt;p&gt;{&lt;/p&gt;
&lt;p&gt;&amp;nbsp; &amp;nbsp; p_broadcast-&amp;gt;params.access_address = BEARER_ACCESS_ADDR_DEFAULT;&lt;/p&gt;
&lt;p&gt;&amp;nbsp; &amp;nbsp; p_broadcast-&amp;gt;params.radio_config.payload_maxlen = RADIO_CONFIG_ADV_MAX_PAYLOAD_SIZE;&lt;/p&gt;
&lt;p&gt;&amp;nbsp; &amp;nbsp; p_broadcast-&amp;gt;params.radio_config.radio_mode = RADIO_MODE_BLE_1MBIT;&lt;/p&gt;
&lt;p&gt;&amp;nbsp; &amp;nbsp; p_broadcast-&amp;gt;params.radio_config.tx_power = RADIO_POWER;&lt;/p&gt;
&lt;p&gt;}&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf mesh Softdevice assert: 88996:0</title><link>https://devzone.nordicsemi.com/thread/295094?ContentTypeID=1</link><pubDate>Thu, 18 Feb 2021 12:56:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f68e3029-267a-445c-a1d2-6935705a3ae3</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Ivan,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Could you show how you change the TX Power in advertiser.c and scanner.c ?&lt;br /&gt;Could you verify if you remove those change the device works stably for a long time ?&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf mesh Softdevice assert: 88996:0</title><link>https://devzone.nordicsemi.com/thread/294970?ContentTypeID=1</link><pubDate>Thu, 18 Feb 2021 01:36:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c2efc697-c87d-4427-9720-3ae2c813caec</guid><dc:creator>ipshiv</dc:creator><description>&lt;p&gt;Good day!&lt;/p&gt;
&lt;p&gt;We&amp;#39;ve configured prio according to link. With only one difference: app timer works without scheduler (only mesh events use it). This gives us better performance during provisioning.&lt;/p&gt;
&lt;p&gt;Peripherals: TWI (APP_IRQ_PRIO_HIGH), UARTE (APP_IRQ_PRIO_LOW).&lt;/p&gt;
&lt;p&gt;The problem occurred after switching to negative tx power in advertiser.c and scanner.c&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf mesh Softdevice assert: 88996:0</title><link>https://devzone.nordicsemi.com/thread/294918?ContentTypeID=1</link><pubDate>Wed, 17 Feb 2021 15:38:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:08d1921b-c261-4a89-a185-34688658447a</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Oleh,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I assume you are using S140 v7.2.0 ?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The softdevice error 88996 suggests that it&amp;#39;s a RADIO interrupt issue. Could you give some more information about your application ?&amp;nbsp;&lt;br /&gt;I would suggest to try testing remove functionalities (reduce any traffic) and gradually add them back to see at which point the assert occurs.&amp;nbsp;&lt;br /&gt;Have you made sure you followed the priority configuration described &lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.meshsdk.v5.0.0/md_doc_user_guide_mesh_interrupt_priorities.html?cp=7_2_2_5"&gt;here &lt;/a&gt;?&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>