Many legacy applications are built on Contiki, and many papers on IoT
are written around tests done on Contiki. Contiki also has a quite
large community who work with applications on the platform.
Because of this it would be useful to have a way of running Contiki
applications and projects under R
Hi,
Just on the subject on uIP: I'm currently working on an emb6 port (in
parallel to the lwIP port), which is a proto-thread-less fork of uIP. But
as discussed in [1] and by the advantages you have given additionally, it
would definitely make sense to run Contiki in RIOT.
Cheers,
Martine
Am 19.01
Hey,
On 01/19/2016 11:58 AM, Joakim Nohlgård wrote:
I would like to hear any ideas and opinions on this list on how to
effectively implement this.
I really like the possiblity and always bragged that this way it is
possble, but running RIOT as thread within Contiki is not (in any way
that ma
Hey there,
+1 for the idea on my side too.
cheers
Emmanuel
On Tue, Jan 19, 2016 at 12:45 PM, Kaspar Schleiser
wrote:
> Hey,
>
> On 01/19/2016 11:58 AM, Joakim Nohlgård wrote:
>
>> I would like to hear any ideas and opinions on this list on how to
>> effectively implement this.
>>
>
> I really li
Dear all ,
I would like to ask you if there is any example of the drivers/saul .
Thank you in advance!
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
Hi,
That's an excellent idea!
Also as you are looking for implementation pointers,
maybe it is worthwhile to look at what the company HiKoB did:
- for their product, they modified Contiki to run on top of FreeRTOS
- a derived version is available here: https://github.com/iot-lab/contiki
(
Hello RIOTers!
I'm trying to make a small network with 3 samr21 boards, one as a border
router connected to my PC via SLIP (using the example
gnrc_border_router), and the other two as CoAP servers (using
microcoap_server example). My goal is to reach both boards from my PC
using Firefox with Coppe
Hello Francisco,
You do not need RPL for your setup:
* Start your border router application and tunslip6 (e.g. beef::1/64)
* configure beef::2/64 on interface 6 at the border router and
add beef::1 to the neighbor cache on interface 6
(these steps are outlined in the border router README)
*
