: nRF Connect SDK 3.1.0 requires CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y – possible clock impact?

[Moh]

Hi,

I’m using NCS v3.1.0 and noticed that my application does not run unless I enable:

CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y

Without this configuration, the system fails to start.

However, when this option is enabled, I observe performance-related issues. Specifically, when reading large chunks of data from external flash and displaying them on an LCD, I see display corruption. Reducing the chunk size resolves the issue, which suggests a timing or clock-related problem.

The same project built on NCS v3.0.2 does not require this configuration and runs without any corruption issues.

Could this be related to LFCLK/HFCLK configuration changes in 3.1.0? What is the recommended way to properly configure the clock source in this version?

kind regards,

Moh

[Moh]

5824.prj.conf

Hi, Also how I can make sure on sdk version 3.1.0, fast clock hclk is enabled as currently I don't see hclk clock is started. See prj.conf file attached.