This disclosure relates generally to electronics and more particularly to microcontroller systems.
Low power consumption is an increasingly important parameter for microcontroller systems. The active power consumption in a microcontroller system is normally dominated by switching activity in the circuit and is proportional to the clock frequency applied to digital logic. Analog modules also contribute a substantially fixed current consumption, which can dominate at low frequencies or in low-power modes. Clocked peripheral modules in the microcontroller system are typically unavailable in ultra-low power, unclocked sleep modes, forcing applications to rely on higher-power clocked modes.
Conventional power reduction solutions for saving power in a microcontroller require that the clock to the Central Processing Unit (CPU) or peripheral modules be switched off, typically by implementing one or more sleep modes in the microcontroller. This solution can be extended until all clocks and analog modules have been switched off, and only leakage current remains, which is typically several orders of magnitude less than active current. The disadvantage of this conventional approach is that the functionality of the device is reduced, since some peripherals are designed to operate with a clock running
A microcontroller system includes a power manager that is configured to, during a power saving mode, configure an interrupt delaying module to receive and hold an interrupt from an interrupt source. In response to receiving the interrupt from the interrupt source, the power manager causes the microcontroller system to exit the power saving mode. Upon exiting the power saving mode, the power manager configures the interrupt delaying module to release the interrupt.
Particular implementations of the microcontroller system can provide one or more of the following advantages: 1) the startup sequence of the microcontroller in response to an interrupt signal can be controlled with changing the design of interrupt sources or an interrupt controller; 2) the startup sequence can be controller without software intervention; 3) both synchronous and asynchronous interrupts can be supported; 4) interrupt propagation during a sleep mode is not changed or degraded; and 5) there is no metastability issue for a module eventually receiving the interrupt.
The details of one or more disclosed implementations are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, the drawings and the claims.
The power manager can configure the microcontroller system to operate in a run mode and one or more low power modes, for example, a retention mode and a sleep mode. In the sleep mode, the processor is frozen, e.g., by clock gating, and the internal voltage value (VDD) is the same as it is in the run mode.
In the retention mode, VDD is lower than in the run mode, which is useful, for example, to reduce leakage current. The reduced VDD is sufficiently large for some or all of the logic cells in the microcontroller system to retain logic values. Also, in the retention mode, the clock is frozen and a voltage regulator is drawing a limited output current.
When the power manager wakes the microcontroller system from the retention mode, there may be a delay in restoring VDD to its full value in the run mode. One or more of the power analog modules may be able to operate using the lower VDD while the microcontroller system is waking, but typically the processor (and perhaps other modules, e.g., the flash memory) are configured to wait until one or more of the power analog modules (e.g., the regulator) are stabilized and the full VDD is available.
For example, when one of the interrupt sources issues an interrupt, the startup time for some functionality of the microcontroller system can be reduced by configuring the power analog modules to start operating immediately in response to the interrupt and configuring the processor to wait. The power manager can implement this startup sequence using the interrupt delaying modules, while avoiding modifying the interrupt controller or the interrupt sources. By using the interrupt delaying module, the power manager can implement this startup sequence for both synchronous and asynchronous interrupt sources.
In operation, the power manager configures an interrupt delaying module to receive and hold an interrupt from an interrupt source while the microcontroller is in the retention mode. In response to receiving the interrupt, the power manager causes the microcontroller system to exit the retention mode. In some implementations, the microcontroller system only partially exits the retention mode, e.g., the power analog modules can be enabled while some other modules remain in the retention mode because a power source is not yet stabilized. When the power analog modules indicate that the power is ready, e.g., via a regulator ready signal, the power manager configures the interrupt delaying module to propagate the interrupt to the interrupt controller. Then the processor can be enabled and will be able to fetch code from the flash module.
The power manager includes a finite state machine 210 and a flip-flop 212, e.g., a D flip flop. The flip-flop receives an asynchronous regulator ready signal from the regulator, indicating the regulator is supply a target voltage or a substantial fraction of the target voltage. The flip flop also receives a signal from the power manage finite state machine indicating whether the microcontroller system is in the retention mode or not.
The interrupt delaying module includes first and second flip-flops 214 and 216, e.g., D flip-flops, a multiplexer 218, and first and second AND gates 220 and 222. A clock is connected to a clock input of each of the first and second flip-flops. The output of the flip-flop 212 of the power manager is coupled to an input of the first AND gate 220 and function as an asynchronous “enable” signal that causes the interrupt delaying module to hold an interrupt. The enable signal is asynchronously set to logic “1” when the regulator is ready. The enable signal is synchronously cleared when the power manager finite state machine indicates that the system is in retention mode.
The power manager finite state machine provides a synchronous output “disable_sync” signal to an input of the second AND gate 222 that causes the interrupt delaying module to release an interrupt or bypass other incoming interrupts. The disable_sync signal is set to logic “1” when the power manager finite state machine is in run mode. The disable_sync signal is cleared when the power manager finite state machine is not in run mode.
The interrupt source is coupled to the “asynchronous set” of inputs of each of the first and second flip-flops and provides an interrupt as an “in_irq” signal. The in_irq signal can be set asynchronously and cleared synchronously. An output of the first flip-flop 214 is coupled to an input of the second flip-flop 216 and to an input of the multiplexer.
An output of the second flip-flop 216 is coupled to another input of the first AND gate 220. An output of the multiplexer is coupled to another input of the first flip-flop 214. Another input of the multiplexer is coupled to a voltage representing logical “0.” A selector input of the multiplexer is coupled to the output of the second AND gate 222, which controls whether the multiplexer outputs the logical “0” or the value at the other input of the multiplexer.
The output of the first AND gate 220 provides the output interrupt as an “out_irq” signal. The output of the first AND gate 220 is also coupled to an input of the second AND gate 222. The operation of the microcontroller system will be described with reference to the example timing diagram of
The first row 304 of the timing diagram illustrates the state of the power manager finite state machine. The next row 306 illustrates the state of the clock. The next row 308 illustrates the “enable” signal from the power manager to the interrupt delaying module. The next row 310 illustrates the synchronous “disable_sync” signal from the power manager to the interrupt delaying module.
The next row 312 illustrates the “in_irq” signal that represents an interrupt from an interrupt source to the interrupt delaying module. The next row 314 illustrates the “regulator ready” signal from the regulator. The next row 316 illustrates the system voltage from the regulator, VDD.
The next row 318 illustrates an “in_irq_m” signal from the output of the second flip-flop 216 to the input of the first flip-flop 214 and the input of the multiplexer. The next row 320 illustrates an “in_irq_s” signal from the output of the first flip-flop 214 to the input of the first AND gate 220. The next row 322 illustrates the output of the first AND gate, which eventually provides the delayed interrupt to the interrupt controller.
At time t0, the power manager finite state machine has configured the microcontroller system to operate in the run mode. The clock is on and the regulator is ready and providing 1.8V. At time t1, the power manager finite state machine configures the microcontroller to enter the retention mode. The regulator drops VDD to 1.2 V and the regulator_ready, enable, and disable_sync signals all fall to a logic “0” level. The clock is frozen.
At time t2, the interrupt source generates an interrupt, and the in_irq signal rises to a logic “1” level. The in_irq_m and in_irq_s signals also rise because they are asynchronously set. The regulator begins raising VDD from 1.2V to 1.8V. The out_irq signal remains at a logic “0” level, and the interrupt delaying module is holding the interrupt and not releasing the interrupt to the interrupt controller. The clock begins waking when VDD reaches a certain voltage.
At t3, VDD reaches a substantial fraction of the 1.8V target voltage, and the regulator_ready signal rises. In response, the enable signal rises, and soon after the out_irq signal rises to release the interrupt to the interrupt controller. There is no metastability issue for the interrupt controller because the clock is still frozen. At t4, the clock wakes, the disable_sync signal rises, and then in response, the in_irq signal and the in_irq_m and in_irq_s signals fall. At t5, the out_irq signal falls, and the interrupt controller has received the interrupt.
The power manager causes the microcontroller system to enter a retention mode (402). In some implementations, the power manager freezes a system clock. In some implementations, the power manager causes a voltage regulator to provide a lower voltage.
During the retention mode, the power manager configures an interrupt delaying module to receive and hold an interrupt from an interrupt source (404). In response to receiving the interrupt, the power manager causes the microcontroller system to exit or partially exit the retention mode (406). In some implementations, the power manager causes the voltage regulator to provide a higher voltage.
Upon exiting the retention mode, the power manager configures the interrupt delaying module to release the interrupt, for example, to an interrupt controller coupled to a processor (408). In some implementations, the power manager receives a ready signal from a voltage regulator and provides an asynchronous enable signal to the interrupt delaying module in response to receiving the ready signal.
The power manager can then synchronously clear the enable signal after the clock wakes. The power manager can wake the clock in response to the ready signal. The interrupt delaying module can alternatively release the interrupt to another module, e.g., a module between the interrupt delaying module and the interrupt controller.
While this document contains many specific implementation details, these should not be construed as limitations on the scope what may be claimed, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable sub combination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can, in some cases, be excised from the combination, and the claimed combination may be directed to a sub combination or variation of a sub combination.
This application claims the benefit and priority of U.S. Provisional Application Ser. No. 61/703,998, filed Sep. 21, 2012, the entire contents of which is hereby incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
4475134 | Bowden et al. | Oct 1984 | A |
4677566 | Whittaker et al. | Jun 1987 | A |
4703486 | Bemis | Oct 1987 | A |
5579498 | Ooi | Nov 1996 | A |
5623234 | Shaik et al. | Apr 1997 | A |
6163851 | Yamazoe et al. | Dec 2000 | A |
6175891 | Norman et al. | Jan 2001 | B1 |
6255878 | Gauvin et al. | Jul 2001 | B1 |
6320717 | Feng | Nov 2001 | B1 |
6393080 | Kamoshida et al. | May 2002 | B1 |
6462830 | Negishi | Oct 2002 | B1 |
RE38108 | Chee | May 2003 | E |
6754836 | Shimizue et al. | Jun 2004 | B2 |
6848055 | Yarch | Jan 2005 | B1 |
7203855 | Chou | Apr 2007 | B2 |
7391250 | Chuang | Jun 2008 | B1 |
7444530 | Deppe | Oct 2008 | B2 |
7514958 | Zhou | Apr 2009 | B1 |
7574683 | Wilson et al. | Aug 2009 | B2 |
7770142 | Shmayovitsh | Aug 2010 | B1 |
7895458 | Kim | Feb 2011 | B2 |
7954078 | Wang | May 2011 | B1 |
7984317 | Conroy | Jul 2011 | B2 |
8190931 | Laurenti et al. | May 2012 | B2 |
8255722 | Pedersen et al. | Aug 2012 | B2 |
8683419 | Hines | Mar 2014 | B1 |
8791743 | Tang | Jul 2014 | B1 |
20030006807 | Masuda et al. | Jan 2003 | A1 |
20030177404 | Jorgenson et al. | Sep 2003 | A1 |
20030183024 | Lohberg et al. | Oct 2003 | A1 |
20030198108 | Hausmann et al. | Oct 2003 | A1 |
20040148548 | Moyer | Jul 2004 | A1 |
20040158773 | Kang | Aug 2004 | A1 |
20050083081 | Jacobson et al. | Apr 2005 | A1 |
20070260794 | Ashish et al. | Nov 2007 | A1 |
20080072094 | Hayano et al. | Mar 2008 | A1 |
20080189455 | Dreps et al. | Aug 2008 | A1 |
20080211559 | Tanaka | Sep 2008 | A1 |
20090089607 | Rodriguez | Apr 2009 | A1 |
20090089725 | Khan | Apr 2009 | A1 |
20090135751 | Hodges | May 2009 | A1 |
20090153210 | Wang et al. | Jun 2009 | A1 |
20090204835 | Smith et al. | Aug 2009 | A1 |
20090256607 | Smith et al. | Oct 2009 | A1 |
20090259863 | Williams et al. | Oct 2009 | A1 |
20100064160 | Wilson | Mar 2010 | A1 |
20100156458 | Speers | Jun 2010 | A1 |
20100192115 | Yang | Jul 2010 | A1 |
20100306570 | Uchida et al. | Dec 2010 | A1 |
20110060931 | Radhakrishnan | Mar 2011 | A1 |
20110131427 | Jorgenson et al. | Jun 2011 | A1 |
20110138200 | Tomizawa | Jun 2011 | A1 |
20110208888 | Park | Aug 2011 | A1 |
20110221483 | Liu et al. | Sep 2011 | A1 |
20110252251 | De Cesare et al. | Oct 2011 | A1 |
20110264902 | Hollingworth | Oct 2011 | A1 |
20120017099 | David | Jan 2012 | A1 |
20120047402 | Chen et al. | Feb 2012 | A1 |
20120120958 | Mahadevan et al. | May 2012 | A1 |
20120268995 | Sugimoto et al. | Oct 2012 | A1 |
20130063114 | Agrawal et al. | Mar 2013 | A1 |
20130067250 | Wu et al. | Mar 2013 | A1 |
20130073878 | Jayasimha et al. | Mar 2013 | A1 |
20130097445 | Palaniappan et al. | Apr 2013 | A1 |
20130124895 | Saha et al. | May 2013 | A1 |
20130339589 | Qawami et al. | Dec 2013 | A1 |
20140089706 | Menard et al. | Mar 2014 | A1 |
20140089707 | Jouin et al. | Mar 2014 | A1 |
20140089714 | Pedersen et al. | Mar 2014 | A1 |
20140122833 | Davis | May 2014 | A1 |
20140281648 | Russell et al. | Sep 2014 | A1 |
20140301152 | Cox et al. | Oct 2014 | A1 |
20150082093 | Sarangi | Mar 2015 | A1 |
20150095681 | Jouin et al. | Apr 2015 | A1 |
20150220678 | Srivastava | Aug 2015 | A1 |
20150378423 | Hanssen | Dec 2015 | A1 |
Entry |
---|
Non-Final Office Action dated Apr. 9, 2015; U.S. Appl. No. 13/788,366, filed Mar. 7, 2013, 15 pages. |
Non-Final Office Action dated Mar. 12, 2015, U.S. Appl. No. 13/786,042, filed Mar. 5, 2013 (14 pages). |
U.S. Appl. No. 13/785,999, non-final office action dated Mar. 25, 2015, 12 pages. |
US Non-Final Office Action in U.S. Appl. No. 12/400,690, dated Sep. 12, 2011, 7 pages. |
US Final Office Action in U.S. Appl. No. 12/400,690, dated Jan. 11, 2012, 7 pages. |
US Notice of Allowance in U.S. Appl. No. 12/400,690, dated May 9, 2012, 6 pages. |
US Notice of Allowance in U.S. Appl. No. 13/785,999, dated Sep. 10, 2015, 16 pages. |
US Non-Final Office Action in U.S. Appl. No. 14/043,445, dated Aug. 25, 2015, 12 pages. |
US Final Office Action in U.S. Appl. No. 13/786,042, dated Sep. 10, 2015, 13 pages. |
US Notice of Allowance in U.S. Appl. No. 13/788,366, dated Oct. 13, 2015, 20 pages. |
Number | Date | Country | |
---|---|---|---|
20140089708 A1 | Mar 2014 | US |
Number | Date | Country | |
---|---|---|---|
61703998 | Sep 2012 | US |