[riot-devel] 6LOWPAN RIOT

[Giritharan]

Hi I am new to RIOT.

 I have two SAMR21-XPRO Devices.I am using RIOT OS to 
communicate between two board.I tried RPL Routing for mesh network.I set up 
one device is parent and another is child by RPL networking.I tried this link 
to set up RPL (https://github.com/RIOT-OS/RIOT/wiki/Tutorial%3A-RIOT-and-
Multi-Hop-Routing-with-RPL).As per the above link all are working fine for 
me.
My question is i want to communicate my parent node to wifi or ethernet based 
devices.For that which device i can use.I think boarder router is used to 
convert ipv6 to ipv4 or vice versa.So for boarder router which device shall i 
use to communicate with samr21.
I am confusing over this.Please help me to find out the right solution.
Thanks in advance.






With Regards,
R.Giritharan

___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] netdev2 - some hints about the relationships between the 6lowpan protocol

[Martine Lenders]

Hi Bernhard,
that's not what I said: cc11xx is the only *radio* in master. Since netdev2
was introduced around the time we introduced Ethernet, there are also
several Ethernet devices (netdev2_tap, enc28j60, encx24j600) that support
the netdev2 interface. Our IEEE 802.15.4 radios work with the predecessor
of netdev2 that is very similar, but bound to the GNRC stack: gnrc_netdev.
PR 4646 and its dependencies introduce a glue code layer for netdev2 and
GNRC and allows thus for easy porting of gnrc_netdev devices to netdev2
(when it is merged). PR 4646 provides the port for the at86rf2xx radio as
an example.

Hope this was helpful enough. If you have further questions just ask :-)

Best regards,
Martine

2016-02-26 22:04 GMT+01:00 Bernhard Nägele :

> Hello everyone,
> that sounds not goodonly one device in master und one not yet merged!?
>
>
> Best regards,
> Bernhard
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] netdev2 - some hints about the relationships between the 6lowpan protocol

[Bernhard Nägele]

Hello everyone,
that sounds not goodonly one device in master und one not yet merged!?

Best regards,
Bernhard
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] netdev2 - some hints about the relationships between the 6lowpan protocol

[Peter Kietzmann]

Hi,

AFAIK the nrf24l01+ actually is the radio and it does not support 
netdev2, neither netdev. That proprietary transceiver has just the 
lowlevel support currently. There are plans to adapt it to netdev2 
"soon" but that device is kind of special. Thus it will be a bit 
tinkered I guess. Even if it's fun to find a way it won't be my first 
choice to transmit 6LoWPAN packets over it.


Best
Peter

Am 26.02.2016 um 12:50 schrieb Martine Lenders:

Hi,
what radio is the nrf24l01p using? The only radio in master currently 
implementing netdev2 is the cc11xx driver (all others are either 
Ethernet drivers or not merged yet). As stated before: there is a move 
to port the IEEE 802.15.4 devices (which are currently implementing 
the older GNRC-specific interface gnrc_netdev), starting with PR 4646 
[1] (with the at86rf2xx radio).


Cheers,
Martine

[1] https://github.com/RIOT-OS/RIOT/pull/4646

2016-02-26 12:43 GMT+01:00 Bernhard Nägele >:


Hello everyone,
today I compiled the example/gnrc_minimal with the nrf24l01p
module included in the boards Makefile.dep file (Riot Release
package RIOT-2015.12)
. The compile process was successful and the compiler output show
the the driver for the radio module was compiled. But when I
searched with the debugger for driver subroutines, it seems that
they are not really linked into the result.
Is there anyone who can explain me where I have to include the
driver in the makefile-structure (USEMODULES +=) that it will
be involked by the example-application? In the board makefiles? In
the application makefiles? Auto-Init? Wherelse?

Thank you very much!


Best regards,
Bernhard
___
devel mailing list
devel@riot-os.org 
https://lists.riot-os.org/mailman/listinfo/devel




___
devel mailing list
devel@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@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] netdev2 - some hints about the relationships between the 6lowpan protocol

[Martine Lenders]

Hi,
what radio is the nrf24l01p using? The only radio in master currently
implementing netdev2 is the cc11xx driver (all others are either Ethernet
drivers or not merged yet). As stated before: there is a move to port the
IEEE 802.15.4 devices (which are currently implementing the older
GNRC-specific interface gnrc_netdev), starting with PR 4646 [1] (with the
at86rf2xx radio).

Cheers,
Martine

[1] https://github.com/RIOT-OS/RIOT/pull/4646

2016-02-26 12:43 GMT+01:00 Bernhard Nägele :

> Hello everyone,
> today I compiled the example/gnrc_minimal with the nrf24l01p module
> included in the boards Makefile.dep file (Riot Release package RIOT-2015.12)
> . The compile process was successful and the compiler output show the the
> driver for the radio module was compiled. But when I searched with the
> debugger for driver subroutines, it seems that they are not really linked
> into the result.
> Is there anyone who can explain me where I have to include the driver in
> the makefile-structure (USEMODULES +=) that it will be involked by the
> example-application? In the board makefiles? In the application makefiles?
> Auto-Init? Wherelse?
>
> Thank you very much!
>
>
> Best regards,
> Bernhard
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] netdev2 - some hints about the relationships between the 6lowpan protocol

[Bernhard Nägele]

Hello everyone,
today I compiled the example/gnrc_minimal with the nrf24l01p module 
included in the boards Makefile.dep file (Riot Release package RIOT-2015.12)
. The compile process was successful and the compiler output show the 
the driver for the radio module was compiled. But when I searched with 
the debugger for driver subroutines, it seems that they are not really 
linked into the result.
Is there anyone who can explain me where I have to include the driver in 
the makefile-structure (USEMODULES +=) that it will be involked by 
the example-application? In the board makefiles? In the application 
makefiles? Auto-Init? Wherelse?


Thank you very much!

Best regards,
Bernhard
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel