<?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>BLE Mesh Sensor Example</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/97272/ble-mesh-sensor-example</link><description>I am attempting to get a BLE mesh network running using the BLE mesh sensor examples. I have one nRF52840 board and multiple Fanstel EVM-BC833 nRF52833 based boards. I have tried running both client and server examples on both boards with similar results</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 06 Mar 2023 18:05:36 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/97272/ble-mesh-sensor-example" /><item><title>RE: BLE Mesh Sensor Example</title><link>https://devzone.nordicsemi.com/thread/413631?ContentTypeID=1</link><pubDate>Mon, 06 Mar 2023 18:05:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e993e71d-3760-4c18-8b1e-17a5ed5cd784</guid><dc:creator>Hieu</dc:creator><description>&lt;p&gt;Hi Terry2,&lt;/p&gt;
&lt;p&gt;Just follow up on &lt;a href="https://github.com/zephyrproject-rtos/zephyr/commit/894275c0983c440dece51b9c9abf8474644152bc#diff-dccbb25cc34086042193126bd5b09e2b1ff09d3f24fb18da73095b6c2244560c"&gt;the fix&lt;/a&gt; that I mentioned in my last reply. It seems that it&amp;nbsp;is not in NCS v2.3.0 or NCS latest development downstream yet.&lt;/p&gt;
&lt;p&gt;It looks like the fix is not dependent on anything, so&amp;nbsp;if you encounter a problem with Bluetooth behavior while build with debug options, you could try&amp;nbsp;cherry picking the commit to your current NCS setup.&lt;/p&gt;
&lt;p&gt;Hieu&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Mesh Sensor Example</title><link>https://devzone.nordicsemi.com/thread/413337?ContentTypeID=1</link><pubDate>Fri, 03 Mar 2023 19:13:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cdd00b9a-33e9-415e-b48e-161069f66272</guid><dc:creator>Hieu</dc:creator><description>&lt;p&gt;Hi Terry2,&lt;/p&gt;
&lt;p&gt;It looks like you are building with debug options enabled. With that, the stack use will be higher than what is being set in prj.conf.&lt;/p&gt;
&lt;p&gt;I could reproduce your exact issue when I build with debug options. I tried to double the stack size and&amp;nbsp;the sample now works.&lt;/p&gt;
&lt;p&gt;Please try&amp;nbsp;the following Kconfig when you build that sample with debug options:&lt;/p&gt;
&lt;p&gt;CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=4096&lt;br /&gt;CONFIG_BT_RX_STACK_SIZE=4300&lt;/p&gt;
&lt;p&gt;This was not necessary this time, but another stack that usually has problem when&amp;nbsp;building with debug options is the main stack. That is configured by CONFIG_MAIN_STACK_SIZE.&lt;/p&gt;
&lt;p&gt;Please watch out for any unexpected behavior when testing application built with debug options. There is also an issue in the BT stack size tracked &lt;a href="https://github.com/zephyrproject-rtos/zephyr/issues/52105"&gt;here&lt;/a&gt;. It affects NCS v2.1.x&amp;nbsp;and v2.2.0 to my knowledge. A solution has been added&amp;nbsp;to&amp;nbsp;the Zephyr upstream in &lt;a href="https://github.com/zephyrproject-rtos/zephyr/pull/55062"&gt;this PR&lt;/a&gt;, but&amp;nbsp;I am not certain if it has been fixed in v2.3.0 yet. I will get back to you regarding that soon.&lt;/p&gt;
&lt;p&gt;Hieu&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>