MPU FAULT during gatt service discoveryhttps://devzone.nordicsemi.com/f/nordic-q-a/102505/mpu-fault-during-gatt-service-discoveryI&#39;m trying to connect to 15 BLE devices. I&#39;ve followed the code at: https://github.com/NordicMatt/multi-NUS/ but have modified it to filter by the device name and then write to a specific characteristic once it has discovered the services. I&#39;m using aen-USTelligent Community 13Fri, 13 Oct 2023 01:18:50 GMTRE: MPU FAULT during gatt service discoveryhttps://devzone.nordicsemi.com/thread/450168?ContentTypeID=1Fri, 13 Oct 2023 01:18:50 GMT137ad170-7792-4731-bb38-c0d22fbe4515:5c2c4ddd-ee9a-4e4b-aa29-5cfadcc1017ftiva4c<p>Make&nbsp;struct bt_gatt_write_params write_params global because the params should be kept&nbsp;valid, it&#39;ll solve the problem</p><div style="clear:both;"></div>RE: MPU FAULT during gatt service discoveryhttps://devzone.nordicsemi.com/thread/439842?ContentTypeID=1Fri, 04 Aug 2023 08:10:18 GMT137ad170-7792-4731-bb38-c0d22fbe4515:52dbf279-c345-41bd-90c9-f9fa617a3710Susheel Nuguru<p>This looks like a stack overflow with the call stack most likely not giving a meaningful info. But it is interesting to see this info from the fault handler<br /><br /><pre class="ui-code" data-mode="text">[00:00:13.189,788] &lt;err&gt; os: Current thread: 0x200021c0 (BT RX)</pre></p> <p>Can you try to increase the <a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/kconfig/index.html#CONFIG_BT_CTLR_RX_PRIO_STACK_SIZE">BT_CTLR_RX_PRIO_STACK_SIZE</a>&nbsp;and do a prestine build and see if it can solve the issue. I am quite confident that this seems to be one of the stack overflow issue. But which stack, that is something we need to find out by debugging.</p><div style="clear:both;"></div>