Starting a new thread from a BLE callbackhttps://devzone.nordicsemi.com/f/nordic-q-a/76308/starting-a-new-thread-from-a-ble-callbackI have a BLE service: BT_GATT_SERVICE_DEFINE (lres_svc, BT_GATT_PRIMARY_SERVICE ( BT_UUID_LRES ), BT_GATT_CHARACTERISTIC ( BT_UUID_LRES_STAT , BT_GATT_CHRC_NOTIFY , BT_GATT_PERM_NONE , NULL , NULL , NULL ), BT_GATT_CCC ( lec_ccc_cfg_changeden-USTelligent Community 13Mon, 14 Jun 2021 11:29:16 GMTRE: Starting a new thread from a BLE callbackhttps://devzone.nordicsemi.com/thread/315097?ContentTypeID=1Mon, 14 Jun 2021 11:29:16 GMT137ad170-7792-4731-bb38-c0d22fbe4515:0bd5de0e-93a1-499b-8714-4fa873dd61d3bachelor<p>Also this is a duplicate, because I couldnt edit the tags (which I forgot to include here). So maybe it could be deleted...</p><div style="clear:both;"></div>RE: Starting a new thread from a BLE callbackhttps://devzone.nordicsemi.com/thread/315096?ContentTypeID=1Mon, 14 Jun 2021 11:27:45 GMT137ad170-7792-4731-bb38-c0d22fbe4515:4da8dc00-c067-4f8f-a7bf-8dd34f6ae6e4bachelor<p>Found the problem now: thread_data was declared inside the callback function, so it lies at address &amp;thread_data on the Bluetooth stack . It is therefore not a valid address for other threads. As a consequence the MPU recognizes a memory access violation. When I declared it outside the callback function the problem went away.</p><div style="clear:both;"></div>