设计指南5791

Tips for Writing Bulletproof Real-Time Clock Control Code


Abstract: With the use of proper device initialization and code sequencing, accurate timekeeping and clock alarm operations become a more manageable task.

Introduction

When we read a clock, as we have all done since childhood, our eyes 'take a snapshot' of the present displayed values. Someone has already gone through the effort to reorient that display for your readability. When the microprocessor needs to access the real-time clock, the 'snapshot' of the latest register values must be reoriented into a sequence of time counts that we are more familiar with.
With the use of proper device initialization and code sequencing, accurate timekeeping and clock alarm operations become a more manageable task.

Device Initialization

Upon the first power application to a new clock component, the sequence of required I/O instructions may vary, based upon that specific component. Refer to the device specification for register structuring. As a general guideline, and assuming power is stable and the I/O port is operational, it is recommended to:
  1. Enable writing to the chip (if a software write-protection option exists)
  2. Enable the 32kHz RTC oscillator (if not auto-started)
  3. Define the hardware interrupt output configuration(s) (as applicable)
  4. Load initial counter values
Enable Writing to the RTC: This unique function was added to some component designs (for example, the DS1305) to prevent inadvertent clock changes. Refer to the product specification for the write-protect (WP) bit explanation.
Enable RTC Oscillator: On some legacy designs (such as DS12887, DS1307), the RTC oscillator does not auto-start at first power-up. This operational feature was intended to prevent battery consumption during transit/storage, and must be enabled through I/O. Designs with an %-overbar_pre%EOSC%-overbar_post% bit in the Control register include a built-in oscillator auto-start function, executed upon the first power application. In some other designs like DS1685, it may also be necessary to identify the crystal load capacitance setting for proper oscillator operation.
Check 'OSF': Some RTC components contain an oscillator stop flag (OSF), allowing the user to monitor oscillator operation via periodic I/O. Upon initial power application, OSF will be set. After enabling the oscillator, clear OSF, and then periodically verify that the OSF bit remains Logic 0.
OSF may become Logic 1 based upon any of these conditions:
  1. Initial application of power
  2. Voltages on VCC and VBAT are insufficient to maintain oscillator operation
  3. %-overbar_pre%EOSC%-overbar_post% bit was set to 1, stopping the oscillator
  4. External influences upon the crystal (leakage, coupling, etc.)
Define Interrupt Output(s): Depending upon the specific component and the desired application, definition of the output functions should now be executed to prevent unintended signals from being sent to the microprocessor. Component programming options for real-time alarm(s), watchdog interrupt, square-wave output frequency, etc., should be selected to establish the desired pin/signal conditioning.
In devices with real-time alarms, every alarm register should initially be written to 00h (if binary-coded decimal (BCD)) or FFh (if binary) to prevent any inadvertent matching/interrupt generation. The alarm registers are not factory-initialized, and the associated alarm flags can appear at any time the alarm register contents match the real-time count.
Load Initial Counter (Time) Values: Again referring to the product's specification and register map, the order of counter loading or reading should be executed from least significant count to the most significant count. Figure 1 illustrates the counter orientation and carry functions for a typical BCD-formatted real-time clock component.
RTC counter chain.
Figure 1. RTC counter chain.
Whenever writing to the RTC, any write to the least significant counter byte resets the internal 1Hz chain, allowing the user one full second before any timekeeping counter bits subsequently increment. This 1Hz reset action, as well as synchronization techniques, are explained in further detail in the Time Synchronization section.
To facilitate ease of use, the registers are oriented in ascending weight and address order for your programming convenience.
BCD Format
Hundredths of a Second (if so equipped)
Seconds
Minutes
Hours
Day of Week
Date
Month
Year
Century (if so equipped)
Binary (Seconds)
00h -> FFh = 0 -> 255.
00h -> FFh = 256. -> 65535.
00h -> FFh = 65536. -> 16777215.
00h -> FFh = 16777216. -> 4294967295.

Time Synchronization

To some users, the simple act of setting the clock (writing to the RTC) may accomplish the timekeeping accuracy goals for the real-time clock in that application. Depending upon the care taken when initializing our device, an initial clock-set error of a few seconds may be considered acceptable when weighed against the execution of the other tasks controlled by that application.
In other applications, it may be desired to synchronize the real-time clock with a known time standard, like WWV1. As previously mentioned, writing to the least significant counter byte resets the 1Hz countdown chain. Figure 2 illustrates how to reset the 1Hz countdown chain using an I2C Write sequence to the SECONDS register of a DS1340. The slave address byte (D0h), register address (00h), and 'updated Seconds value' (03h), are being transmitted to the component. Two representative examples of an asynchronous 1Hz square-wave output are shown to illustrate the resulting adjustment.
I/O-initiated clock synchronization (I2C format shown).
Figure 2. I/O-initiated clock synchronization (I2C format shown).
On the slave's acknowledgement of the data byte (27th rising edge of SCL), the slave simultaneously 1) pulls SDA low to ACK receipt of the data byte, 2) the 1Hz countdown chain is reset, and 3) the new Seconds value (03h in the Figure 2 example) is transferred into the Seconds register.
On the first 1Hz SQW waveform, the 1Hz signal was Logic 1 when the ACK occurred. SQW is immediately pulled low. Precisely 0.5 seconds after the ACK, the SQW output transitions high. Precisely 1.0 second after the ACK, SQW is pulled low, indicating 1 second has elapsed since the write completed. Reading the Seconds register now results in a content of 04h.
On the second 1Hz SQW diagram, the 1Hz signal was Logic 0 when the ACK occurred, so the SQW signal remains low until precisely 0.5 seconds after the ACK, where the 1Hz output will transition high. Precisely 1.0 second after the ACK, SQW is again pulled low, indicating 1 second has elapsed since the write completed. Reading the Seconds register now results in a content of 04h.
For products with 3-wire or SPI I/O, the equivalent trigger to the 27th SCL rising edge in Figure 2 is the next-occurring transition of either SCLK or Chip-Enable (CE or %-overbar_pre%CS%-overbar_post%, whichever input pin naming convention was used).
For products with Phantom I/O, the equivalent trigger to the 27th SCL rising edge in Figure 2 is the termination of the 72nd write cycle in the serial data packet (including the 64-cycle pattern recognition).
For products with Byte-Wide I/O, the equivalent trigger to the 27th SCL rising edge in Figure 2 would be the termination of a write cycle to the Seconds register.

Using Time-of-Day Alarms

On devices with one or more real-time alarm circuits, the user can request either periodic or non-periodic interrupt events to occur at some predetermined time. Alarms can be set up to 30 days in advance of the desired event.
Programming of the alarms suggests use of a few simple rules:
  1. Initialize all alarm registers to a known state one time (alarms are not POR-reset)
  2. Never change Real-Time Clock register settings when an alarm circuit is enabled
  3. Never change Alarm register settings when that alarm circuit is enabled
  4. Clear the associated Alarm Flag before enabling that alarm (or you may create a premature interrupt)
The most common periodic interrupt is a 'daily alarm', set to activate at 5:30AM, fully independent of the calendar content. To ignore the DAY/DATE register, we will utilize an alarm mask.
Control = 04h			;oscillator on, define %-overbar_pre%INT%-overbar_post%/SQW output function, alarms off
Alarm1 SECONDS = 00h		;0 seconds
Alarm1 MINUTES = 30h		;30 minutes
Alarm1 HOURS = 45h		;5AM in 12hr Mode
Alarm1 DAY/DATE = 80h		;alarm mask set to match on 'Hours, Minutes & Seconds'
Status = 00h			;clear both alarm flags
Control = 05h			;now enable Alarm1 (A1IE=1)
At the next occurrence of 5:30AM, the %-overbar_pre%INT%-overbar_post%/SQW pin will assert.
To clear the interrupt, leaving the alarm enabled for the following morning at the same time, clear the associated Alarm Flag (A1F).
To clear the interrupt and disable any future alarms, clear the associated Alarm Enable (A1IE).
When the associated alarm is disabled, those alarm registers can be used for general-purpose data storage.

Conclusion

Component initialization procedures, when properly sequenced, should include definitions for all of the RTC's hardware functionality required for stable system operation. If desired, the real-time clock can also be synchronized to an external time base, and a procedure for that synchronization has been outlined. Additionally, optional use of real-time clock alarms has been included, focusing upon the order of execution of I/O instructions.

References

  1. WWV is the call sign of the United States National Institute of Standards and Technology's (NIST) HF-band radio station in Fort Collins, Colorado.


相关型号
DS1243 64k NV SRAM,带有隐含时钟 免费样品  
DS1244 256k NV SRAM,带有隐含时钟 免费样品  
DS1248 1024k NV SRAM,带有隐含时钟 免费样品  
DS1251 4096k NV SRAM,带有隐含时钟 免费样品  
DS1254 2M x 8 NV SRAM,带有隐含时钟  
DS12885 实时时钟 免费样品  
DS12887 实时时钟 免费样品  
DS12887A 实时时钟 免费样品  
DS12C887 实时时钟 免费样品  
DS12C887A 实时时钟 免费样品  
DS12R885 带有恒压涓流充电器的RTC 免费样品  
DS12R887 带有恒压涓流充电器的RTC  
DS1302 带涓流充电的时钟芯片 免费样品  
DS1305 带有闹钟的串行实时时钟 免费样品  
DS1306 带有闹钟的串行实时时钟 免费样品  
DS1307 64 x 8、串行、I²C实时时钟 免费样品  
DS1315 隐含时钟芯片 免费样品  
DS1318 并行接口历时计数器 免费样品  
DS1337 I²C串行实时时钟 免费样品  
DS1338 I²C RTC,带有56字节NV RAM 免费样品  
DS1339 I²C串行实时时钟 免费样品  
DS1339A 低电流I²C串行实时时钟 免费样品  
DS1339B 低电流、I2C、串行实时时钟,可配合高ESR晶振工作 免费样品  
DS1340 I²C RTC,带有涓流充电器 免费样品  
DS1341 低电流I²C RTC,可配合高ESR晶体使用 免费样品  
DS1342 低电流I²C RTC,可配合高ESR晶体使用 免费样品  
DS1343 低电流SPI/3线RTC 免费样品  
DS1344 低电流SPI/3线RTC 免费样品  
DS1347 小电流、SPI兼容实时时钟 免费样品  
DS1371 I²C、32位二进制计数器看门狗时钟 免费样品  
DS1372 I²C、32位、二进制计数时钟,具有64位ID 免费样品  
DS1374 I²C、32位二进制计数器看门狗RTC,带有涓流充电器和复位输入/输出 免费样品  
DS1375 I²C数字输入RTC,带有闹钟功能 免费样品  
DS1388 I²C RTC/监控电路,带有涓流充电器和512字节EEPROM 免费样品  
DS1390 低电压SPI/3线接口RTC,带有涓流充电器 免费样品  
DS1391 低电压SPI/3线接口RTC,带有涓流充电器 免费样品  
DS1392 低电压SPI/3线接口RTC,带有涓流充电器 免费样品  
DS1393 低电压SPI/3线接口RTC,带有涓流充电器 免费样品  
DS1394 低电压SPI/3线接口RTC,带有涓流充电器 免费样品  
DS1500 Y2K兼容、看门狗RTC,带有非易失控制  
DS1501 Y2K兼容、看门狗实时时钟 免费样品  
DS1511 Y2K兼容、看门狗实时时钟 免费样品  
DS1553 64kB非易失、Y2K兼容时钟RAM  
DS1554 256k非易失、Y2K兼容时钟RAM 免费样品  
DS1556 1M非易失、Y2K兼容时钟RAM 免费样品  
DS1557 4M非易失、Y2K兼容时钟RAM 免费样品  
DS1558 看门狗时钟,带有NV RAM控制器 免费样品  
DS1629 数字温度计及实时时钟/日历 免费样品  
DS1642 非易失时钟RAM  
DS1643 非易失时钟RAM  
DS1644 非易失时钟RAM  
DS1646 非易失时钟RAM  
DS1647 非易失时钟RAM  
DS1670 便携系统控制器 免费样品  
DS1672 I²C、32位二进制计数器RTC 免费样品  
DS1673 便携系统控制器 免费样品  
DS1677 便携系统控制器 免费样品  
DS1678 实时事件记录器 免费样品  
DS1682 历时记录器,带有闹钟功能 免费样品  
DS1683 带报警功能的历时和事件记录器 免费样品  
DS1685 3V/5V实时时钟 免费样品  
DS1687 3V/5V实时时钟 免费样品  
DS17285 3V/5V实时时钟 免费样品  
DS17287 3V/5V实时时钟 免费样品  
DS1742 Y2K兼容、非易失时钟RAM  
DS1743 Y2K兼容、非易失时钟RAM  
DS1744 Y2K兼容、非易失时钟RAM 免费样品  
DS1746 Y2K兼容、非易失时钟RAM 免费样品  
DS1747 Y2K兼容、非易失时钟RAM 免费样品  
DS17485 3V/5V实时时钟 免费样品  
DS17487 3V/5V实时时钟 免费样品  
DS17885 3V/5V实时时钟 免费样品  
DS17887 3V/5V实时时钟 免费样品  
DS3231 超高精度、I²C接口、集成RTC/TCXO/晶体  
DS3231M ±5ppm, I²C实时时钟 免费样品  
DS3232 超高精度、I²C RTC,集成晶体和SRAM  
DS3232M ±5ppm、内置SRAM的I²C实时时钟 免费样品  
DS3234 超高精度、SPI总线RTC,集成晶体和SRAM  


下一步
EE-Mail 订阅EE-Mail,接收关于您感兴趣的新文档的自动通知。
Download 下载,PDF格式 (100.3kB)  

© Mar 28, 2014, Maxim Integrated Products, Inc.
The content on this webpage is protected by copyright laws of the United States and of foreign countries. For requests to copy this content, contact us.

APP 5791: Mar 28, 2014
设计指南5791, AN5791, AN 5791, APP5791, Appnote5791, Appnote 5791