Real-time clock information is maintained for devices such as computers, including information such as time and date. Real-time clock is typically maintained within and/or used by a computer's basic input/output system (BIOS). Various applications installed on the computer may use the real-time clock.
For a more complete understanding of various examples, reference is now made to the following descriptions taken in connection with the accompanying drawings in which:
Various examples described below provide for updating of a real-time clock for a device, such as a computer. The real-time clock uses information from a fuel gauge of a battery to update the timer information. The fuel gauge of a battery is provided with circuitry for a timer. A controller, such as the central processing unit (CPU) of the device, can obtain the timer information from the fuel gauge of the battery upon boot up of the device. The basic input/output system (BIOS) of the device can obtain the timer information from the fuel gauge and update the real-time clock of the device. Thus, in accordance with various examples, the real-time clock of the device does not need to be powered when the device is shut down, eliminating the need for a coin battery, for example. In some examples, the timer information from the fuel gauge of the battery may be used to supplement, synchronize or otherwise provide timer information to the real-time clock.
Referring now to
The example device 100 of
A nonvolatile memory 130 is provided on the example device 100 of
The volatile memory 120 and the non-volatile memory 130 are accessed by the CPU 110. As noted above, the CPU 110 may access the volatile memory 120 (e.g., RAM) to load and access applications while executing instructions associated with the applications, for example. The non-volatile memory 130 may be accessed by the CPU 110 to access data that may be used, for example, by the applications. For example, the iron-volatile memory 130 may store files for editing by a word processing program.
Information stored in the volatile memory 120 may be available during operation of the device 100, but may be lost when the device 100 is shut down. For example, a program loaded into the volatile memory 120 for use by the CPU 100 may require re-starting each time the device 100 is re-booted. By contrast, information in the non-volatile memory 130 may remain stored in the non-volatile memory 130 even if the device 100 is shut down. Thus, information such as documents, pictures, software or other such data may be stored in the non-volatile memory 130.
A part of the non-volatile memory 130 is used to store basic input/output system (BIOS) information. That part is illustrated in
The example device 100 of
In the example of
In various examples of the present disclosure, certain information from the fuel gauge 160 may be provided to the BIOS of the device 110. In
Referring now to
The timer 170 may be similar to a real-time clock and, in some examples, may be driven by a clock signal generated from a crystal oscillator. Those skilled in the art will appreciate that various types of timers are possible and are contemplated within the scope of the present disclosure.
Referring again to
As with the timer 170 of the battery 150, the real-time clock 210 of the BIOS 200 may take various forms. In one example, the real-time clock 210 includes circuitry driven by a clock signal generated from a crystal oscillator. As referred to herein, a real-time clock 210 is a clock which provides a timing function which supplies timing information to be used as a system time for the device or system in which the real-time clock is implemented. In various examples, the real-time clock provides timing information such as a current time and date. The real-time clock may be used to provide common timing information to multiple sub-systems or applications within the device or system.
In various example of the present disclosure, the real-time clock 210 uses information from the timer 170 in the battery 150. The real-time clock 210 can use the information from the timer 170 to update or synchronize the date and time information. In some examples, unlike real-time clock in conventional systems, the real-time clock 210 ceases operation when the device 100 is shut down. In this regard, while conventional systems include a coin battery to allow continued operation of the real-time clock, in some examples of the present disclosure, no power is provided to the real-time clock 210 when the device 100 is shut down. Thus, the need for an additional power source, such as a coin battery, is eliminated.
Referring now to
Thus, referring again to
At block 320, timer information from the timer 170 of the battery 150 (e.g., from the fuel gauge 160 of the battery 150) is obtained. The timer information from the battery 150 may be obtained by, for example, the CPU 110 of the device 100 or directly by the BIOS memory 140 of the device 100. In various examples, the timer information may include the current date and time. Additional information may be provided and is contemplated within the scope of the present disclosure.
At block 330, the timer information from the timer 170 of the battery 150 is used to update the real-time clock associated with the BIOS 200. In this regard, the BIOS 200 may re-start or synchronize the real-time clock 210 with the timer information from the timer 170. Thereafter, the real-time clock 210 can operate normally and may be used by the BIOS 200 and various other aspects of the device 100.
While
Thus, in various examples, a real-time clock may be provided without the need for a coin battery or any other power source for the real-time clock when the device is shut down. In other examples, a coin battery may be provided for operation of the real-time clock, but timer information from a timer in the device's main battery may be used for synchronization or error correction of the real-time clock.
The various examples set forth herein are described in terms of example block diagrams, flow charts and other illustrations. Those skilled in the art will appreciate that the illustrated examples and their various alternatives can be implemented without confinement to the illustrated examples. For example, block diagrams and their accompanying description should not be construed as mandating a particular architecture or configuration.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/US2014/048099 | 7/25/2014 | WO | 00 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2016/014069 | 1/28/2016 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
5542077 | Johnson | Jul 1996 | A |
7930527 | Matsuoka et al. | Apr 2011 | B2 |
20020043955 | Hansford | Apr 2002 | A1 |
20030115001 | Odaohhara | Jun 2003 | A1 |
20080104409 | Matsuoka | May 2008 | A1 |
20110302441 | Sawyers | Dec 2011 | A1 |
20110314322 | Shao | Dec 2011 | A1 |
20120275101 | Johnson et al. | Nov 2012 | A1 |
20120327749 | Tsukamoto et al. | Dec 2012 | A1 |
20130232373 | Wang et al. | Sep 2013 | A1 |
20140095897 | Ji et al. | Apr 2014 | A1 |
20140163910 | Yu et al. | Jun 2014 | A1 |
20160378135 | Larson | Dec 2016 | A1 |
Number | Date | Country |
---|---|---|
0616281 | Sep 1994 | EP |
Entry |
---|
Jinrong Qian and Michael Vega, “Host-side Gas-guage-system Design Considerations for Single-cell Handheld Applications,” Oct. 19, 2007, pp. 12-15 and Notice (1 page) Analog Applications Journal 4O 2007 Texas Instruments Incorporated. |
Number | Date | Country | |
---|---|---|---|
20170185101 A1 | Jun 2017 | US |