Hi all
I for one have been missing support for RTC that would enable MCU sleep and
wake up the system via ISR callback when requested. How about making a pull
request out of this and make it part of RIOT? I'm seeing the copyleft licensing
is LGPL so it should be good.
- t
> On 22 Nov 2017,
We have two xtimer-like RTC-based timers implemented on STM32L1: * https://github.com/unwireddevices/RIOT/tree/loralan-public/sys/rtctimers — rtctimers for ~1 second to 1 week delays, it uses regular RTC calendar* https://github.com/unwireddevices/RIOT/tree/loralan-public/sys/rtctimers-millis —
Hi,
I didn't say it is not working. But xtimer was designed to guarantee a
resolution of 1usec. Therefore if you use it with a different timer, you
are out of spec within RIOT ;)
On 21.11.2017 17:28, Michael Andersen wrote:
> This is not quite true. Xtimer works fine with the ultra low power
A little reconfiguration sounds like an understatement if you are truly going
into standby sleep mode?
Dan
> On Nov 21, 2017, at 8:28 AM, Michael Andersen wrote:
>
> This is not quite true. Xtimer works fine with the ultra low power 32khz
> oscillator on SAMR21, it
First, I should add that I currently have a working samd21 low power
implementation but to accomplish that I use rtt.c for my always running clock
and then standby sleep the module whenever it gets to the idle task. This is a
hack and is not a clean implementation and means you don’t use
That's the 'only' issue. Problem: xtimer is guaranteed to have 1usec of
resolution. Most low-power timers will only have 8bit resolution ->
xtimer cannot be used.
On 21.11.2017 15:07, Francisco Molina wrote:
>
>>Issues #7743 and #7332 both discuss the problem.
>>
>>Dan
>
> I saw those issues
>Issues #7743 and #7332 both discuss the problem.
>
>Dan
I saw those issues but they only refer to the fact that xtimer doesn't run
during sleep modes, is that the only issue? Cheers
Francisco
___
devel mailing list
devel@riot-os.org