Hello,
The driver is already invoked on startup to enable the LF clock for the Zephyr OS so I don't think it should be neccessary to invoke the driver in the application code. You can use the clock kconfig symbols if you wish to change the LF clock configuration (LFXO is selected by default):
CONFIG_CLOCK_CONTROL_NRF_ACCURACY
CONFIG_CLOCK_CONTROL_NRF_K32SRC_XTAL (=y by default)
CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC
You can also use the the following APIs to request and release the HFXO if you have a Bluetooth application:
mpsl_clock_hfclk_release()
But these should only be used if you need a high accuracy HF clock for a particular task. The idle current will stay at ~200 uA if you don't call mpsl_clock_hfclk_release() after you are done with it.
Best regards,
Vidar
Hello,
The driver is already invoked on startup to enable the LF clock for the Zephyr OS so I don't think it should be neccessary to invoke the driver in the application code. You can use the clock kconfig symbols if you wish to change the LF clock configuration (LFXO is selected by default):
CONFIG_CLOCK_CONTROL_NRF_ACCURACY
CONFIG_CLOCK_CONTROL_NRF_K32SRC_XTAL (=y by default)
CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC
You can also use the the following APIs to request and release the HFXO if you have a Bluetooth application:
mpsl_clock_hfclk_release()
But these should only be used if you need a high accuracy HF clock for a particular task. The idle current will stay at ~200 uA if you don't call mpsl_clock_hfclk_release() after you are done with it.
Best regards,
Vidar