Allows easy usage of the LPC1768 RTC interrupts

Dependents:   Mini_DK_clk MakerBotServer GT-ACQUAPLUS_Consumo GT-ACQUAPLUS_Eficiencia ... more

The RTC library allows easy access to the LPC1768s interrupt sources on its RTC. There are two different interrupt sources: periodic interrupts, for example every new second, hour, etc, and an alarm, which is called at a specified time.

Time initialization

This library only allows easy usage of the RTC interrupts. You have to initialize the time functions (so the RTC) the normal way specified here: http://mbed.org/handbook/Time?action=view&revision=11592

Hello World!

#include "mbed.h"
#include "RTC.h"

DigitalOut led(LED1);

void ledFunction( void )
{
    led = 1;
    RTC::detach(RTC::Second);
}

void displayFunction( void )
{
    time_t seconds = time(NULL);
    printf("%s", ctime(&seconds));
}

void alarmFunction( void )
{
    error("Not most useful alarm function");
}

int main()
{
    set_time(1256729737); // Set time to Wed, 28 Oct 2009 11:35:37

    tm t = RTC::getDefaultTM();
    t.tm_sec = 5;
    t.tm_min = 36;

    RTC::alarm(&alarmFunction, t);
    RTC::attach(&displayFunction, RTC::Second);
    RTC::attach(&ledFunction, RTC::Minute);

    while(1);
}

Periodic interrupts

Periodic interrups can be attached by using:

RTC::attach([function], [TimeUnit]);

The TimeUnit specifies which unit should increase for the function to be called. This function is useful if you are making for example a clock: You can simply connect the display update to an RTC interrupt. Of course you can do something similar by using timer objects, but they aren't timed exactly correct, and it is nicer to do it directly on the RTC.

Alarm function

The LPC1768's RTC also allows for one alarm to be activated. The alarm goes off the first time there is a compare match on a specified time and the current time. All fields of the normal C tm structure are supported (http://www.cplusplus.com/reference/ctime/tm/), set a field at -1 for it to be ignored. The RTC::getDefaultTM() function helps with that, it returns a tm structure with every field initialized to -1, so don't care.

So if you want to make an alarm that gets called every monday, every 5 minutes and 30 seconds after the hour, you would use:

tm t = RTC::getDefaultTM();
t.tm_sec = 30;     //30 seconds
t.tm_min = 5;      //5 minute
t.tm_wday = 1;     //monday
RTC::alarm([yourFunction], t);

Attaching member functions

For compactness of the documentation attaching member functions of objects isn't included. However it works exactly the same as for example attaching one to a Ticker object: http://mbed.org/users/mbed_official/code/mbed/docs/63cdd78b2dc1/classmbed_1_1Ticker.html#af92f41ff11906b1f96fa6bbe0b17aa29

Disclaimer

Believe it or not, but I didn't test every possible combination of alarm settings / interrupts. So especially for the larger timescales there is an increased chance on bugs.

Revision:
0:39767ffe05e6
Child:
1:be9d058ee5c7
diff -r 000000000000 -r 39767ffe05e6 RTC.cpp
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/RTC.cpp	Wed Dec 05 21:03:44 2012 +0000
@@ -0,0 +1,183 @@
+#include "RTC.h"
+
+FunctionPointer RTC::attachCB[6];
+FunctionPointer RTC::alarmCB;
+
+bool RTC::initialRun = true;
+
+void RTC::attach(void (*function)(void), TimeUnit interval)
+{
+    //Disable IRQs, dont want them to happen while busy here
+    NVIC_DisableIRQ(RTC_IRQn);
+
+    //Set the IRQ vector
+    NVIC_SetVector(RTC_IRQn, (uint32_t)&RTC::IRQHandler);
+
+    //If this is the first time it is called, delete all interrupt sources
+    //We need to do this because RTC unit isnt affected by system resets apparently
+    if (initialRun) {
+        LPC_RTC->CIIR = 0;
+        LPC_RTC->AMR = 255;
+        initialRun = false;
+        LPC_RTC->ILR = 0x03;
+    }
+
+    //Set the function pointer
+    attachCB[interval].attach(function);
+
+
+    //Set/reset correct interrupt source
+    if (function == NULL) {
+        switch (interval) {
+            case Second:
+                LPC_RTC->CIIR &= ~1;
+                break;
+            case Minute:
+                LPC_RTC->CIIR &= ~2;
+                break;
+            case Hour:
+                LPC_RTC->CIIR &= ~4;
+                break;
+            case Day:
+                LPC_RTC->CIIR &= ~56;
+                break;
+            case Month:
+                LPC_RTC->CIIR &= ~64;
+                break;
+            case Year:
+                LPC_RTC->CIIR &= ~128;
+                break;
+        }
+    } else {
+        switch (interval) {
+            case Second:
+                LPC_RTC->CIIR |= 1;
+                break;
+            case Minute:
+                LPC_RTC->CIIR |= 2;
+                break;
+            case Hour:
+                LPC_RTC->CIIR |= 4;
+                break;
+            case Day:
+                LPC_RTC->CIIR |= 56;
+                break;
+            case Month:
+                LPC_RTC->CIIR |= 64;
+                break;
+            case Year:
+                LPC_RTC->CIIR |= 128;
+                break;
+        }
+    }
+
+    //We can always enable IRQs, since if all IRQs are disabled by the user the RTC hardware will never raise its IRQ flag anyway
+    NVIC_EnableIRQ(RTC_IRQn);
+}
+
+
+void RTC::alarm(void (*function)(void), tm time)
+{
+    //Disable IRQs, dont want them to happen while busy here
+    NVIC_DisableIRQ(RTC_IRQn);
+
+    //Set the IRQ vector
+    NVIC_SetVector(RTC_IRQn, (uint32_t)&RTC::IRQHandler);
+
+    //If this is the first time it is called, delete all interrupt sources
+    //We need to do this because RTC unit isnt affected by system resets apparently
+    if (initialRun) {
+        LPC_RTC->CIIR = 0;
+        LPC_RTC->AMR = 255;
+        initialRun = false;
+        LPC_RTC->ILR = 0x03;
+    }
+
+    //Set the function pointer
+    alarmCB.attach(function);
+    
+    //Set the alarm register
+    if ((time.tm_sec>=0) && (time.tm_sec<60)) {
+        LPC_RTC->ALSEC = time.tm_sec;
+        LPC_RTC->AMR &= ~1;
+    } else
+        LPC_RTC->AMR |= 1;
+
+    if ((time.tm_min>=0) && (time.tm_min<60)) {
+        LPC_RTC->ALMIN = time.tm_min;
+        LPC_RTC->AMR &= ~2;
+    } else
+        LPC_RTC->AMR |= 2;
+
+    if ((time.tm_hour>=0) && (time.tm_hour<24)) {
+        LPC_RTC->ALHOUR = time.tm_hour;
+        LPC_RTC->AMR &= ~4;
+    } else
+        LPC_RTC->AMR |= 4;
+
+    if ((time.tm_mday>=1) && (time.tm_mday<32)) {
+        LPC_RTC->ALDOM = time.tm_mday;
+        LPC_RTC->AMR &= ~8;
+    } else
+        LPC_RTC->AMR |= 8;        
+        
+    if ((time.tm_mon>=0) && (time.tm_mon<12)) {
+        LPC_RTC->ALMON = time.tm_mon + 1;   //Different definitions
+        LPC_RTC->AMR &= ~64;
+    } else
+        LPC_RTC->AMR |= 64;    
+
+    if ((time.tm_year>=0) && (time.tm_year<1000)) {
+        LPC_RTC->ALYEAR = time.tm_year + 1900;   //Different definitions
+        LPC_RTC->AMR &= ~128;
+    } else
+        LPC_RTC->AMR |= 128;
+        
+    //We can always enable IRQs, since if all IRQs are disabled by the user the RTC hardware will never raise its IRQ flag anyway
+    NVIC_EnableIRQ(RTC_IRQn);
+}
+
+void RTC::alarmOff( void ) {
+    LPC_RTC->AMR = 255;
+    }
+
+
+void RTC::IRQHandler( void )
+{
+    if ((LPC_RTC->ILR & 0x01) == 0x01) {
+        //Attach interrupt
+        attachCB[0].call();
+
+        //If seconds zero
+        if (LPC_RTC->SEC == 0) {
+            attachCB[1].call();
+
+            //If minutes zero
+            if (LPC_RTC->MIN == 0) {
+                attachCB[2].call();
+
+                //If hours zero
+                if (LPC_RTC->HOUR == 0) {
+                    attachCB[3].call();
+
+                    //If days zero
+                    if (LPC_RTC->DOM == 0) {
+                        attachCB[4].call();
+
+                        //If month zero
+                        if (LPC_RTC->MONTH == 0)
+                            attachCB[5].call();
+                    }
+                }
+            }
+        }
+    }
+
+    if ((LPC_RTC->ILR & 0x02) == 0x02)
+        alarmCB.call();
+
+
+
+    //Reset interrupt status
+    LPC_RTC->ILR = 0x03;
+}
\ No newline at end of file