[was: Refectoring the network stack]
I’m co-leading the OpenWSN project. CC’ing the OpenWSN ML.
In 2014, the IETF 6TiSCH working group (which is standardizing how to use IEEE802.15.4e TSCH in combination with 6LoWPAN, RPL, CoAP) organized two “plugfests”:
- in London in March (https://bitbucket.org/6tisch/meetings/wiki/140306a_ietf89_london_plugfest)
- in Toronto in July (https://bitbucket.org/6tisch/meetings/wiki/140720a_ietf90_toronto_plugfest) For those events, the RIOT team (Thomas Eichinger leading the effort) developed a mechanism to use the OpenWSN protocol stack in conjunction with RIOT’s task scheduler. A very cool design, indeed!
Following this success, the OpenWSN team is re-architecting its code so that the “kernel” can be dynamically changed at compile time. Choices will be openos (the native OpenWSN scheduler), RIOT and FreeRTOS. Lead on that project is Xavi Vilajosana, details at https://openwsn.atlassian.net/browse/FW-16.
Note that the 6TiSCH WG, in conjunction with ETSI, will organize a 6TiSCH interop event during IETF93 (July 2015, Prague) around 6TISCH technology, so including IEEE802.15.4e TSCH. You (and RIOT of course!) might be interested in participating. The plan is to come up with writing the test spec by March 2015.
BTW, I happen to be giving a talk about OpenWSN in 90min (https://swarmlab.eecs.berkeley.edu/events/2014/8/22/5118/openwsn-technical-overview-status-and-road-ahead), which is streamed live online. I’ll talk about the RIOT integration, so you might be interested to listen.