What is the default value of CONFIG_MPSL_HFCLK_LATENCY in nRF Connect SDK v3.1.0?

[Kenta]

Hello.

I'm trying out nRF Connect SDK v3.1.0 with nRF54L15-DK.

docs.nordicsemi.com/.../release-notes-3.1.0.html
The release notes say:

Updated by increasing the default value of the CONFIG_MPSL_HFCLK_LATENCY Kconfig option to support slower crystals. See the Kconfig description for a detailed description on how to select the correct value for a given application.

However, it seems that CONFIG_MPSL_HFCLK_LATENCY in autoconf.h remains unchanged at 854.

Is there something I've overlooked?

Best regards.

[Simonr]

Hi again

This is not a bug. The Development Kit uses a lower MPSL values as we have measured the crystal used on the DK to have a lower startup time. If you build for custom boards the default CONFIG_MPSL_HFCLK_LATENCY will be 1400.

Best regards,

Simon

[Kenta]

Hi Simonr.

> This is not a bug. The Development Kit uses a lower MPSL values as we have measured the crystal used on the DK to have a lower startup time.
OK. I understand.

> If you build for custom boards the default CONFIG_MPSL_HFCLK_LATENCY will be 1400.
When building on a custom nRF54L15 SoC board,
the hfxo: startup-time-us in ncs/v3.1.0/zephyr/dts/vendor/nordic/nrf54l_05_10_15.dtsi was applied, resulting in a value of 1650.

With the nRF54H20-DK and nRF52-DK, the value was 1400.

This information can be used to report the issue to our team.
Thank you for your cooperation.

It’s okay to close this ticket.

Best regards.
- Kenta.