I am using the MESH distributor sample from the nRF Connect SDK (v2.8.0) on an nRF52840 development board. My aim is to use the RC oscillator (RC source) instead of the low-frequency crystal (X2).
However, when I remove the low-frequency crystal (X2) and enable the RC source in the prj.conf file, the application does not start properly. The Bluetooth functionality doesn't turn on, and I do not see any prints on the serial monitor.
When the low-frequency crystal (X2) is present, the application works fine.
To enable the RC source, I added the following configurations to my prj.conf file:
CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y
CONFIG_CLOCK_CONTROL_NRF_K32SRC_XTAL=n
CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC_CALIBRATION=y
CONFIG_CLOCK_CONTROL_NRF_K32SRC_500PPM=y
Steps to Reproduce:
- Remove the low-frequency crystal (X2) from the nRF52840 development board.
- Enable the RC source using the above configurations in the
prj.conffile. - Build and flash the MESH distributor sample application.
- Observe that Bluetooth does not turn on, and no logs are printed to the serial monitor.
- Replace the low-frequency crystal (X2) and reflash the same application. It works as expected.
Expected Behavior:
The application should work correctly using the RC oscillator (RC source) as the low-frequency clock, without requiring the low-frequency crystal.
Actual Behavior:
The application does not start, Bluetooth does not turn on, and no logs are observed when using the RC oscillator as the clock source.
Environment Details:
- Development Board: nRF52840 DK
- nRF Connect SDK Version: 2.8.0
- MESH Distributor Sample
Could you please assist in identifying the issue and provide a solution for using the RC source in this scenario?
Thank you!
Abdullah