George Oikonomou 08fddb6598 Always set a valid time for the next AON RTC CH1 compare event ... The AON RTC CH1 event handler aims to schedule the next compare event on the next 512 RTC counter boundary. However, the current calculation of "now" takes place too early within the interrupt handler. In some cases, this results in the next event getting scheduled too soon in the future or on some extreme cases even in the past. AON RTC compare events cannot happen within 2 SCLK_LF cycles after a clearance (4 RTC ticks in the 16.16 format). Thus, if the next 512 boundary is too soon (5 ticks for margin), we skip it altogether. When this happens, etimers that would have expired on the skipped tick will expire 1 tick later instead. Skipping a tick has no negative impact on our s/w clock counter, since this is always derived directly from the hardware counter.		2015-11-14 02:44:04 +01:00
..
batmon-sensor.c
batmon-sensor.h
cc26xx-uart.c
cc26xx-uart.h
contiki-watchdog.c	cc26xx - added optional locking mode for WDT	2015-08-31 09:12:16 -06:00
gpio-interrupt.c
gpio-interrupt.h
oscillators.c
oscillators.h
soc-rtc.c	Always set a valid time for the next AON RTC CH1 compare event	2015-11-14 02:44:04 +01:00
soc-rtc.h	Tickless bugfixes:	2015-09-02 12:05:47 +02:00
uart1.h