On 2011/04/07 15:42, Sebastien Lelong wrote:
Another comment: it's not clear when RTCC peripheral is enabled or not.
It is enabled by rtc_init()
I understand (from API point of view) rtc_init() actually enable the peripheral. But reading code, it's also enabled each time _rtc_write() is called, this means at each RTC setting (rtc_set, ...).
The datasheet says that the rtc registers should be written to only when the rtcc is disabled. Therefore the write routines contain a disable operation at entrance and a enable operation before returning.
Did you overlook something or did I? > One missing procedure would still be
one which actually disable the peripheral...
I cannot think why - once started - one would want to disable the rtcc module as a whole, but such a procedure could be added easily.
Regards, Rob. -- R. Hamerling, Netherlands --- http://www.robh.nl -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
