lfclk configuration initialization

RE: lfclk configuration initialization

kizhimon — Thu, 20 May 2021 12:48:13 GMT

Thank you Einar... It's clear now, As you said it was because of starting timer before LFCLK initialization.

Thank you once again

RE: lfclk configuration initialization

Einar Thorsrud — Wed, 19 May 2021 12:50:43 GMT

The TWI or SPI has no dependency on the LFCLK, but other parts of your application might. I cannot say without knowing more about your application. Generally speaking, if you do not use the LFCLK for anything, it would not matter, as the current consumption of the clock itself is so low. Perhaps you are using an RTC and as that does not work without the LFCLK running, it causes some problem with your app. Again, I cannot really say why whiteout knowing what you need the LFCLK for in your application.

RE: lfclk configuration initialization

kizhimon — Wed, 19 May 2021 12:43:53 GMT

Hi Einar, Thank you for your reply.

If I don't start the LFCLK, it is consuming more current when I start using I2C or SPI. Why is it so ?

RE: lfclk configuration initialization

Einar Thorsrud — Wed, 19 May 2021 12:17:29 GMT

Hi,

This looks like a sensible way to start the LFCLK using the clock driver. I am not sure why you mean this will result in a lower power consumption, though. Perhaps you can elaborate on what you are doing and how you want to save power?