• State Verified Answer
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 86 subscribers
  • Views 1090 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 350102
Options

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.

  • 0

    Hi

    As of NCS 3.1.0 the default CONFIG_MPSL_HFCLK_LATENCY is 1400, so please make sure that you do a pristine build and that you're building with the SDK and toolchain for NCS v3.1.0.

    Best regards,

    Simon

  • 0 in reply to Simonr

    Hello Simon.

    The "config MPSL_HFCLK_LATENCY" in ncs/v3.1.0/nrf/subsys/mpsl/init/Kconfig is indeed set to 1400.

    I also ran a pristin build using toolchain 3.1.0.

    However,
    GEN_ABSOLUTE_SYM_KCONFIG(CONFIG_MPSL_HFCLK_LATENCY, 854); in build/zephyr/misc/generated/configs.c,
    #define CONFIG_MPSL_HFCLK_LATENCY 854 in autoconf.h,
    and CONFIG_MPSL_HFCLK_LATENCY=854 in .config remain at 854.

    I think it changed from 1400 to 854 somewhere, but I don't know where.

    Is there a way to find out?
    Best regards.

  • 0 in reply to Kenta

    Hello Simon.
    Since DT_N_S_clocks_S_hfxo_P_startup_time_us in devicetree_generated.h was also 854, I tried adding the following to app.overlay:

    &hfxo {
    compatible = "nordic,nrf54l-hfxo";
    startup-time-us = <1400>;
    };

    The #define CONFIG_MPSL_HFCLK_LATENCY in autoconf.h also changed to 1400.

    I don't know where the original Devicetree file containing the settings is, but do I need to change it there as well?

    I'll continue looking.
    Best regards.

  • 0 in reply to Kenta

    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.

  • 0

    Hi

    Thank you for reporting that, I will forward this to our developers, and it will likely be fixed in an upcoming NCS release.

    Best regards,

    Simon

Related
Terms of service