BLE fails on connect

[H.Marske]

Hi,

It feels like i have a follow up question of my ticket here.

We are currently developing a product using the nrf54l15 using the nrf connect SDK v2.9.1 with the toolchain of the same version.

We want to include BLE with periodic advertising as well as a GATT-Server into the device. We also develop the counterpart wich wants to know if such a device is present and if so write something into a GATT service.

Sadly i found out that it is no longer possible to debug a ble-application so i resorted to print-debugging with Segger RTT.

The Advertising starts just fine and the information (e.g. the battery-status) can be updated just fine.
The Problem is when is want to connect to the device to see all GATT-Services the code fails.

FYI: System-Powerdown is currently disabled to debugging purposes, so its only the printing when the system should powerdown.
As you can see the BLE-Connection is established (the "connected" print) but the immediately shutdown due to an ASSERTION-Error in the mpsl init.

The addr2line-debugtool only tells me that this is indeed the assertion in the MPSL-init file.

As i mentioned above i thought it might be the same error as in my previous problem but we measred both the 32kHz as well as the 32mHz quartz. both are working as intended.

I also tested it with the DIS-Service example and i got the same error.
Maybe you could point me in the right direction as what might be the error here?

I figured it cannot be some clock problem as the advertising starts and works well?

If you need any additional information just tell me.

[Kazi Afroza Sultana]

Hello,

Have you tried to run the sample on Nordic DK? If it works on the nRF54L15 DK, then it could be hardware issue on your custom board.

MPSL assert error usually relates to HFXO; even though you found the crystal working ok, there may be unproperly soldered decouple capacitors (specially on pin DEC4) on the board or the load capacitor is not correct. 

There are known issues with the default HFXO latency settings on nRF54L15 series devices, which can prevent Bluetooth events running proerly. The workaround is to increase the configured HFXO startup time or the CONFIG_MPSL_HFCLK_LATENCY Kconfig option. Specifically, it is recommended to set the HFXO startup time to 1650 microseconds or increase CONFIG_MPSL_HFCLK_LATENCY by 512 microseconds to allow tuning to complete. This is especially important for nRF54L15, nRF54L10, and nRF54L05 devices Multiprotocol Service Layer (MPSL) Known Issues.