Hi,
On Tue, Nov 21, 2017 at 5:26 PM, Daniel Evans wrote:
> 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 a
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, a
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 — rtc
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 32khz
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 just needs a little reconf
This is not quite true. Xtimer works fine with the ultra low power 32khz
oscillator on SAMR21, it just needs a little reconfiguration. We have duty
cycling nodes working ok with gnrc.
On Nov 21, 2017 8:26 AM, "Robert Hartung" wrote:
> That's the 'only' issue. Problem: xtimer is guaranteed to hav
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 XTIMER
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 but
>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
https://lists.riot-
Issues #7743 and #7332 both discuss the problem.
Dan
> On Nov 20, 2017, at 12:13 PM, Robert Hartung wrote:
>
> Xtimer is not guaranteed to be based on timers that keep running in low power
> modes. Therefore sleeping is not supported on most devices.
>
> Am 20.11.2017 um 21:05 schrieb Franci
Xtimer is not guaranteed to be based on timers that keep running in low
power modes. Therefore sleeping is not supported on most devices.
Am 20.11.2017 um 21:05 schrieb Francisco Molina:
> >Hi,
> >
> >since the timers you mentioned are dependent on xtimer and since xtimer has
> >some known issues
>Hi,
>
>since the timers you mentioned are dependent on xtimer and since xtimer has
>some known issues with power management (what those are directly I can't
>say due to my own lack of knowledge there, some hardware person on this
>list might give you more detailed information on that) in the defau
Hi again,
After re-reading your mail, I think I misunderstood your question...
Regarding caching: no there is no possibility in GNRC to cache data for
sleeping nodes at the moment. Can you maybe describe your set-up further?
I'm particularly interested in how is the border router is notified that
Hi,
since the timers you mentioned are dependent on xtimer and since xtimer has
some known issues with power management (what those are directly I can't
say due to my own lack of knowledge there, some hardware person on this
list might give you more detailed information on that) in the default
con
Hi all,
I have some questions about the possibilities of RIOT in the network area.
First a short introduction about my work.
I am currently working on a project for a low power sensor network with an
ATSAMR21G18A from Atmel and RIOT as operating system. The idea is to connect
sleeping sensor no
15 matches
Mail list logo
