MPSL ASSERT: 112, 2134; HFXO Starts but BLE advertising does not!https://devzone.nordicsemi.com/f/nordic-q-a/117669/mpsl-assert-112-2134-hfxo-starts-but-ble-advertising-does-notHi, I suddenly started getting MPSL ASSERT: 112, 2134 upon BT enable and upon research came across this post ( link ) and used following code: HFXO starts on peripheral_lbs, beacon and on my app but advertising only starts on peripheral_lbs. Howen-USTelligent Community 13Thu, 02 Jan 2025 17:17:23 GMTRE: MPSL ASSERT: 112, 2134; HFXO Starts but BLE advertising does not!https://devzone.nordicsemi.com/thread/516693?ContentTypeID=1Thu, 02 Jan 2025 17:17:23 GMT137ad170-7792-4731-bb38-c0d22fbe4515:e66f0817-2dc3-4228-b440-dc0bfbc8cd42X4ce<p>Thank you for your response.</p> <p>I thoroughly checked my custom board but don&#39;t why suddenly DEC4 and corresponding cap got isolated apparently bad soldering. I then re-soldered the chip and got BLE working.</p><div style="clear:both;"></div>RE: MPSL ASSERT: 112, 2134; HFXO Starts but BLE advertising does not!https://devzone.nordicsemi.com/thread/516626?ContentTypeID=1Thu, 02 Jan 2025 11:09:07 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c1963efe-ece0-42ac-a9ab-9cd14ddb5afbVidar Berg<p>Hello,</p> <p>Please try to request the HFXO using the&nbsp;onoff_request() function instead as&nbsp;shown in the linked post. Requesting&nbsp;HFXO&nbsp;via the onoff API ensures&nbsp;that the oscillator cannot be released by other modules.</p> <p>Did you measure the startup time of the crystal oscillator?</p> <p>Best regards,</p> <p>Vidar</p><div style="clear:both;"></div>