Recommendations for Porting RIOT

Hi,

Given the interesting features embedded in RIOT, I would like to know if the developers have defined (or at least recommend) a certain workflow for porting RIOT to new platforms. I’ve been working in a project involving porting contiki to ns-3 simulator and contiki had a relatively well defined platform dependent interfaces like the clock module, multithreading, realtime timers, network drivers …etc. and I am interesting in porting RIOT and benefit from its protocol stacks and features to simulate IOT scenarios using ns3.

So let’s say I want to to implement RIOT’s multithreading feature on top of NS-3 multithreading library, is it possible to do that without messing things up in RIOT’s core. The same thing goes for the Clock, TImers and the separation of network stacks to define which side (ns3 or riot) takes charge till which network layer.

Best regards, Taqi

Hi Takai,

I was already discussing RIOT ns-3 porting with Daniel Camara from INRIA. He proposed a Google Summer of Code project (1) for this task which I am going to apply for. At the moment I am working on porting RIOT as a UNIX process (the "native" cpu/board).

If you still want to know technical details, please say so.

Cheers, Ludwig

1) http://www.nsnam.org/wiki/index.php/GSOC2013Projects#Improve_ns-3_support_to_sensor_networks.2C_RIOT_adaptation