# Take advantage of external RTC to avoid 32.768KHz duplicity?

asked 2017-01-11 21:26:26 +0200

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.

edit retag close delete

Sort by » oldest newest most voted

answered 2017-01-12 11:36:07 +0200

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.

more

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.

( 2017-01-13 10:04:25 +0200 )editconvert to answer

P0.00/XL1 is correct. What do you mean by "its seems not a problem to lose oscillation except at startup than can be 1s ?" ? It takes 1s to start up the bufferd 32K clock ? Does the RTC chip provide a stable 32K clock after startup?

( 2017-01-13 15:13:45 +0200 )editconvert to answer

Sorry. I mean that the clock would be always available because the RTC chip would be powered by the same power supply than the nRF, but there is a time at the RTC start where the clock is not ready. From NXP datasheet: "...The oscillator is considered to be stopped during the time between power-on and stable crystal resonance. This time can be in the range of 200 ms to 2 s depending on crystal type, temperature, and supply voltage..."

( 2017-01-13 17:36:38 +0200 )editconvert to answer

In that case it should not be a problem. The SoftDevice will wait for the clock to startup. Remember to specify the correct clock accuracy, e.g. NRF_CLOCK_LF_XTAL_ACCURACY_20_PPM.

( 2017-01-16 12:46:46 +0200 )editconvert to answer

answered 2017-01-25 16:44:53 +0200

Hello Sigurd. It's OK. I will check the overall power comsumption with this solution. Thankyou.

more

Please start posting anonymously - your entry will be published after you log in or create a new account.

[hide preview]

## Recent blog posts

• ### Getting started with Nordic's Secure DFU bootloader, a step by step guide

Posted 2017-03-20 17:13:52 by Hung Bui
• ### From Nordic UART Service to MicroPython using PolyMCU and Gattlib

Posted 2017-02-27 16:40:00 by Olivier
• ### Throughput and long range demo

Posted 2017-02-28 16:48:25 by Ole Bauck
• ### nRF52840 long range demo

Posted 2017-02-14 12:46:03 by Ole Bauck
• ### Setup and Running the OpenMesh DFU on the nRF52 DK v2.0

Posted 2017-02-06 22:33:25 by martindavidb

## Recent questions

• ### Flash download failed - BLE ATT_MTU Throughput

Posted 2017-03-27 08:34:19 by Bene
• ### nRF 52832 first time programming

Posted 2017-03-27 08:20:50 by Enrique
• ### nRF5_SDK_11 incompatibility with ANT s212_nrf52_2.0.1

Posted 2017-03-27 07:50:39 by syrinx
• ### S332 BLE CONNECT IOS DEVICE

Posted 2017-03-27 05:07:33 by jwx
• ### ADC signal outlier

Posted 2017-03-27 05:04:40 by djqtsg

## Stats

Asked: 2017-01-11 21:26:26 +0200

Seen: 157 times

Last updated: Jan 25