Thanks Martine!
Will try this tomorrow!
2015-04-29 22:04 GMT+02:00 Martine Lenders :
> Hey Baptiste,
> though there is no example yet you can use the new network stack never the
> less. Just take one of the test applications for the device you want to use
> and compile them with the modules `ng_i
Hey Baptiste,
though there is no example yet you can use the new network stack never the
less. Just take one of the test applications for the device you want to use
and compile them with the modules `ng_ipv6` and `ng_udp`. If you use an
IEEE 802.15.4 device (which are currently the only ones in mas
Hi Martin!
> unfortunately I cannot attend the NTSF meeting tomorrow :(
> So I hacked some words on the current status and the future palns of the FIB
> on a wiki page [1].
Thanks for the effort and the nice overview.
Cheers,
Oleg
--
# Okay, what on Earth is this one supposed to be used for?
Hi all,
unfortunately I cannot attend the NTSF meeting tomorrow :(
So I hacked some words on the current status and the future palns of the
FIB on a wiki page [1].
Best regards,
Martin
[1] https://github.com/RIOT-OS/RIOT/wiki/NSTF:-FIB-Status-and-future-plans
_
An idea:
Create a multi-channel software watchdog that in turn pokes the hardware
watchdog when all parameters are met.
We could configure different timeouts for different channels and each
critical process can have its own channel(s) which they update
independently.
Some risks of this approach is
Thanks for your explanations. I understand why it is counter productive.
But how RIOT will make sure that the board is not stuck in a deadlock? This
is mandatory for industrial context.
Cheers,
2015-04-29 15:07 GMT+02:00 Joakim Gebart :
> It has to do with the difficulty of providing a reliable
It has to do with the difficulty of providing a reliable way of poking the
watchdog in an event driven, tickless, system such as RIOT. Maybe it is
time to start discussing a watchdog api?
In order to get any traction within industry applications I believe it will
be necessary to at least provide an
Hi,
very simple: A watchdog timer does not at all fit into the context of a
tickless-system. We want to sleep as long as possible, so waking up just
to please the WDT is very counter productive...
A WDT interface we could actually introduce, I guess just nobody did it
so far...
Cheers,
Hau
Hi,
I've got two questions concerning WDT:
- Why do we disable it on the samr21 at launch time?
- Why doesn't RIOT provide a wdt.h in drivers/include/periph?
Cheers,
--
*Clenet Baptiste*
___
devel mailing list
devel@riot-os.org
https://lists.riot-o
Dear RIOTers
more good news for our community: Inria [1] will soon open 3 engineer
positions to work full-time on RIOT development and maintenance.
These positions last 2 years, and are planned to debut this fall
(Sept-Oct).
Applicants must hold a Masters degree or equivalent. More details and l
10 matches
Mail list logo
