[riot-devel] Question regarding CCN-lite and RIOT supported platforms

Francisco Javier Acosta Padilla francisco.acosta at inria.fr
Thu Jun 30 18:13:37 CEST 2016

Hi again!

In RIOT we have a little bit more sophisticated way to do that. Please refer to the example “gnrc_border_router”[1] which makes a network link between your linux machine and 802.15.4 motes. It uses the serial link too but it’s not SLIP.

A PR[2] is open to use a simple XBee and a native RIOT instance as a BR, but it’s not merged yet.



[1] https://github.com/RIOT-OS/RIOT/tree/master/examples/gnrc_border_router
[2] https://github.com/RIOT-OS/RIOT/pull/4448

Francisco Javier Acosta Padilla
Research Engineer at INRIA Saclay

On 30 June 2016 at 17:03:39, Adeel Mohammad Malik (adeel.mohammad.malik at ericsson.com) wrote:

Hi Paco,


Thank you for your response.


What I would really like to understand is how a sensor platform running RIOT OS on 802.15.4 can be communicated with using a computer/laptop. How do I make a laptop talk over 802.15.4 radio with a sensor platform?


I have some experience with the Contiki OS. As far as I remember, there you can achieve this by connecting an 802.15.4 enabled platform to the laptop over a UART-USB bridge. Contiki supports IP over UART. Then the 802.15.4 enabled platform connected to the computer talks to the sensor platform wirelessly over 802.15.4. The sensor platform also run IP over 802.15.4.




From: Francisco Javier Acosta Padilla [mailto:francisco.acosta at inria.fr]  
Sent: Thursday, June 30, 2016 4:17 PM
To: RIOT OS kernel developers; Adeel Mohammad Malik
Subject: Re: [riot-devel] Question regarding CCN-lite and RIOT supported platforms


Hi Adeel!


I just saw all the responses but just to add some of the XBee needs to be used with a stm32f4discovery board.


You need this file[1] on your projects root and modify it according to your settings, then to add in your makefile the right modules to use it:



USEMODULE += gnrc_nomac

XBEE_UART ?= “1”




Be careful to choice a good XBEE_UART, since it needs to differ from your STDIO, which you can define in your board.h like here[2].


Afterwards you should be able to use the XBee module as a radio interface.






[1] https://github.com/RIOT-OS/RIOT/blob/master/examples/gnrc_minimal/xbee_params.h

[2] https://github.com/RIOT-OS/RIOT/blob/master/boards/nucleo-f103/include/board.h#L33 


Francisco Javier Acosta Padilla
Research Engineer at INRIA Saclay



On 30 June 2016 at 12:08:45, Adeel Mohammad Malik (adeel.mohammad.malik at ericsson.com) wrote:

Thanks for your reply Peter and Oleg.  

My response inline.  


> -----Original Message-----  
> From: devel [mailto:devel-bounces at riot-os.org] On Behalf Of Peter  
> Kietzmann  
> Sent: Thursday, June 30, 2016 10:01 AM  
> To: RIOT OS kernel developers  
> Subject: Re: [riot-devel] Question regarding CCN-lite and RIOT supported  
> platforms  
> Hi Adeel,  
> Am 30.06.2016 um 09:42 schrieb Oleg Hahm:  
> > Hi Adeel,  
> >  
> > On Wed, Jun 29, 2016 at 07:04:43PM +0000, Adeel Mohammad Malik wrote:  
> >> Thank you for your reply. It was really helpful. I actually posted  
> >> another question on the mailing list about STM32F4Discovery and the  
> >> possibility to run CCN-lite over it with 802.15.4. You have answered that  
> question too.  
> >>  
> >> I just have a follow up question about how the setup would look like  
> >> if I use the Atmel at86rf23x transceiver with STM32F4Discovery. Does  
> >> the transceiver hook up directly to the STM32F4Discovery board?  
> >  
> > For this first question, I'm probably not the best person to answer,  
> > so maybe others (Peter, Paco, Kaspar?) can help, but AFAIK a viable  
> > way could be to buy an Openlabs adapter [1] that can be connected over  
> > SPI and plug it on the Discovery Board.  
> as Oleg already said, the easiest (and cheapest) solution would be an  
> openlabs transceiver. Unfortunately the connector configuration is not  
> compatible with the STM discovery boards but you could use cables instead.  
> The default pin configuration of the RIOT driver can be found here:  
> https://github.com/RIOT-  
> OS/RIOT/blob/master/drivers/at86rf2xx/include/at86rf2xx_params.h#L53  
> There also exist extension boards by Atmel which should work with RIOT, but  
> I assume the problem of incompatible connectors is the same with STM  
> boards (cables needed):  
> http://www.atmel.com/tools/ATZB-A-233-XPRO.aspx  
> Unfortunately the Microchip MRF24J20 driver is still not in shape but this  
> might be a cheap solution in future.  

It is good to know that the MRF24J20 is still not supported, it was one of the things I wanted to know. I also looked at the Atmel option you referenced but as you said the problem of incompatible connectors exists. Thanks for that clarification.  

> >  
> >> Assuming I run CCN-lite directly on 802.15.4, how would I connect the  
> >> STM32F4Discovery board to a computer that acts as a gateway to the CCN  
> >> network?  
> >  
> > That's indeed an interesting question. I think the easiest solution would be  
> > to either plug an Ethernet module to the Discovery Board or use ethos  
> > (ETHernet Over Serial) [2] to connect to the Gateway that run a CCN-lite  
> > client with two interfaces (one with an Ethernet socket pointing to the RIOT  
> > node and one with an IP/UDP socket pointing to the rest of the world).  

I am a bit confused here. Are you talking about running CCN-lite over Ethernet? And if I was to run CCN-lite over Ethernet would I not need an Ethernet module for which RIOT has a driver? There is an extension board (STM32F4DIS-BB) for the STM32F4Discovery board that provides an Ethernet jack. What I am not sure about though is whether there is driver support in RIOT for the Ethernet interface on STM32F4DIS-BB.  

I was also thinking a bit about how easy it would be to do a similar thing but over 802.15.4 and not Ethernet. As Peter and you have pointed out, I could use wires to connect the Atmel at86rf2xx transceiver to the STM32F4Discovery board. The gateway side seems a bit problematic though. I could plug in an 802.15.4 dongle in a gateway device and run CCN-lite (without the RIOT OS) on the gateway. However, then CCN-lite should be able to run over 802.15.4. I assume that CCN-lite does not have support for that.  

One thing that could possibly be done here is to use a hardware platform of the scale of a Raspberry Pie that supports the RIOT OS for the gateway. Then I could run the CCN-lite + RIOT OS on that gateway and attach an 802.15.4 transceiver to it to communicate with the STM32F4Discovery board on one hand and interface it via UDP/IP/Ethernet to the network side on the other. But this assumes that RIOT OS support relays nodes (not just end nodes) and can run on dual stack i.e. 802.15.4 on one side and UDP/IP/Ethernet on the other. Also in the list of supported platforms on the RIOT homepage I don’t see a platform (of the scale of Raspberry Pie) that can do this. Is RIOT supported on the Raspberry Pie?  

> >  
> > In fact, this kind of bridge functionality to translate between different  
> > transports for CCN could be also done directly on a RIOT node, assuming  
> that  
> > (i) the node would have enough resources and (ii) the adaptation to IP  
> > addresses in RIOT's CCN-lite package is there.  
> >  
> > Cheers,  
> > Oleg  
> >  
> > [1] http://openlabs.co/store/Raspberry-Pi-802.15.4-radio  
> > [2] https://github.com/RIOT-OS/RIOT/tree/master/dist/tools/ethos  
> >  
> >  
> >  
> > _______________________________________________  
> > devel mailing list  
> > devel at riot-os.org  
> > https://lists.riot-os.org/mailman/listinfo/devel  
> >  
> --  
> Peter Kietzmann  
> Hamburg University of Applied Sciences  
> Dept. Informatik, Internet Technologies Group  
> Berliner Tor 7, 20099 Hamburg, Germany  
> Fon: +49-40-42875-8426  
> Web: http://www.haw-hamburg.de/inet  
> _______________________________________________  
> devel mailing list  
> devel at riot-os.org  
> https://lists.riot-os.org/mailman/listinfo/devel  
devel mailing list
devel at riot-os.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/devel/attachments/20160630/c8212eff/attachment-0001.html>

More information about the devel mailing list