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

Question

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 · Accepted Answer

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 · Answer

Hello Simonr. 
 In ncs/v3.1.0/zephyr/boards/nordic/nrf54l15dk/nrf54l15dk_common.dtsi, it says: 
 &hfxo { startup-time-us = <854>; }; 
 MPSL's Kconfig states: 
 config MPSL_HFCLK_LATENCY int "HFCLK ramp-up latency in microseconds, assumed by MPSL to wait for clock availability" default $(dt_node_int_prop_int,/clocks/hfxo,startup-time-us) if $(dt_node_has_prop,/clocks/hfxo,startup-time-us) default $(dt_node_int_prop_int,/oscillators/hfxo,startup-time-us) if $(dt_node_has_prop,/oscillators/hfxo,startup-time-us) default 1400 
 Therefore, I believe you should also update startup-time-us in nrf54l15dk_common.dtsi to 1400. Best regards.

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

Top Replies