Does sd_softdevice_enable affect 32.768K crystal clock settings?

[Paul]

I am using softdevice and RTX at the same time. RTX is using RTC1, softdevice is using RTC0, so no problem there. But sd_softdevice_enable require a clock source as one of its parameters. The example code uses NRF_CLOCK_LFCLKSRC_XTAL_50_PPM.

My question is it softdevice going to reconfigure the clock settings for RTC0, which will affect RTC1?

The problem I am seeing right now is: with softdevice enabled, RTX clock goes faster by 10% to 20%.

[Asbjørn]

Yes, the softdevice use the 32 kHz source as input for it's timing. So if you enable one 32 kHz source before you enable the softdevice, you could run into a situation like you have, where you reconfigure the clock source when you enable the softdevice. The recommendation is to start the softdevice first (if this will be running most of the time) and then use the softdevice firendly commands to request the clock source you need or make sure that you enable the same clock source when you enable the softdevice.

SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_XTAL_20_PPM, true);

[Paul]

Thank you. I need to find a way of configuring the RTC1 for the RTOS after enable the soft device or somehow enable the soft device at the very beginning, or in the RTC1 configuration routine. I will report the result later.

[Paul]

Ok, Silly me mistake.

Forgot to put dead loop at the end of main(). with for (;;), everything is fine.