https://devzone.nordicsemi.com/f/nordic-q-a/119611/sdc-fault-file-48-line-203-in-ble-connection-process-using-sdk-nrfxlib-without-zephyrDuring a ble connection process using a nrf54l15 as a peripheral, I get an sdc fault &quot;File 48, Line 203&quot; with this callstack: sym_476LRB5XNUARAHCHHC7ZAIGPFC5VZ4W2N4467LI@0x00006cde sym_EHBS3NH4JXNVZNMK6JERP4NH4YKKYCIBVPVFKFY@0x00009878 sym_SFR5TVV24PZRIRC5QGOHL2X436PUHKRY2QWKP5Yen-USTelligent Community 13Fri, 07 Mar 2025 13:55:09 GMThttps://devzone.nordicsemi.com/thread/526361?ContentTypeID=1Fri, 07 Mar 2025 13:55:09 GMT137ad170-7792-4731-bb38-c0d22fbe4515:7e0a78f6-7012-4f91-ad86-9920ef45ebd8cyrriuswhite<p>Thank you! Yes I am using version v2.9.0. I lowered all priorities except the one specified for the mpsl and it fixed the sdcFault.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/526298?ContentTypeID=1Fri, 07 Mar 2025 08:15:27 GMT137ad170-7792-4731-bb38-c0d22fbe4515:bce331aa-71fb-44ce-a27e-c10e41b8dd01Einar Thorsrud<p>Hi,</p> <p>I am not sure which version you are using(?), but assuming v2.9.0, the assert&nbsp;is triggered by an &quot;overstay&quot; event in the SoftDevice Controller scheduling related to BLE&nbsp;peripheral operation. Something has&nbsp;prevented&nbsp;that code from running on time. That would typically be a higher priority interrupt or thread or similar taking too long time.</p><div style="clear:both;"></div>