File content as of revision 4:691e6b38fc54:

This class provides an API to assist with low power behaviour on an STM32F437
micro. If you need to operate from battery for any significant period, or are
mains powered and don't want to take the planet down with you, you should design
your code with this in mind.

This library uses the https://developer.mbed.org/users/Sissors/code/WakeUp/
library and so could be extended to support all of the MCUs that library
supports.

The principle is that the STM32F437 is put into Stop mode (typical current
consumption 230 uA @ 1.8 V) for a specified time.  In Stop mode the main clocks
are stopped (so software timers are frozen) and the processor is running from
an internal 32 kHz oscillator. Wake-up from this state after the specified delay
is achieved using an alarm from the RTC.

In addition to this, it is possible to save significantly more power by putting
the STM32F437 into Standby mode (typical current consumption 2.8 uA @ 1.8 V).
In this mode, as well as the main clocks being stopped, all of RAM is also
powered down; only the 4 kbyte Backup SRAM is retained.  If you are able to
design your code such that none of the following need be maintained across a
low-power sleep cycle:

* RTOS timers,
* dynamically allocated variables (i.e. those on the stack or the heap, for
  instance allocated with 'new'),
* more than 4 kbytes of statically allocated variables,

...then it may be possible to use Standby mode.  Designing your code to work in
this way requires a specific design approach.  Your code will begin running
again at main() on expiry of the Standby delay and hence you will need to 
determine how to behave based on the information that you have saved in the
4 kbyes of Backup SRAM.  Given the huge saving in power, such a design approach
may well be worthwhile.

Finally, if your code has another means of retaining state across a low-power
sleep cycle then even the Backup SRAM can be powered down, reducing the typical
current consumption to 2.3 uA @ 1.8 V.

Note: these functions assume possession of Alarm A on the RTC hardware block of
the microcontroller.
Note: it is up to the application to disable any external interrupts that it has
activated, otherwise these interrupts will cause the processor to wake up from
sleep permaturely.
Note: it is not possible to make these functions threadsafe versus set_time(),
so please ensure that set_time() can never be active at the same moment as one
of these calls.