This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Take advantage of external RTC to avoid 32.768KHz duplicity?

Hello. I decided to use an external solution for RTC. Sometimes the RTC chip offers an buffered 32.768KHz output. Can I use this output to supply the 32.768KHz to the nRF52832 and gain a litle power saving? Thanks in advance.

Parents
  • Hi,

    In general, it’s no problem using an external 32.768 kHz clock source. But, if the external 32.768 kHz clock is only sometimes available, you would need to switch between the RC oscillator clock and the external clock.

    Unfortunately, you cannot change the SoftDevice LF clock source on the fly, since this would disrupt the protocol timing. You would therefore have to disable the SoftDevice, and enable it again with the new clock source. If you are in an active connection, you will be disconnected, and therefore have to re-connect every time you change the clock source. In most applications this would not be acceptable. The potential power saving is also very small, with the RC oscillator only using about 0.6 µA.

  • Hello Sigurd. The external RTC chip would be powered by the same power supply than the nRF, its seems not a problem to lose oscillation except at startup than can be 1s. I think the power saving can be considerable because the external RTC only needs about 200nA. Can the long startup be a problem? For the connection, I guess input is pin2 P0.00/XL1. Is correct? Thank you.

Reply
  • Hello Sigurd. The external RTC chip would be powered by the same power supply than the nRF, its seems not a problem to lose oscillation except at startup than can be 1s. I think the power saving can be considerable because the external RTC only needs about 200nA. Can the long startup be a problem? For the connection, I guess input is pin2 P0.00/XL1. Is correct? Thank you.

Children
No Data
Related