Re: [riot-devel] Raw communication between native nodes

[Alexander Aring]

Hi,

On 06/22/2016 05:28 PM, Jose Alamos wrote:
> Hi,
> 
> I was wondering if there's a way to send raw data between nodes running on
> native. I need to send OpenThread packets between nodes (through a radio
> abstraction), and I'm having problems with TAP interface since they only
> process ethernet frames.
> 
> I tried to hack a little bit (put these OT packets in ethernet frames) but
> is not working well. Basically, I need to emulate a radio device.
> 
> Is there an easy way to achieve this?
> 

some of you maybe knowing that I am working on a RIOT native 802154raw
transceiver driver which works with AF_PACKET RAW linux-wpan interfaces.

At the end it should work like the following:

First I need to describe a special virtual 802.15.4 driver, it's named
fakelb (maybe such idea can also be implemented in RIOT).

It works similar like the hwsim80211 driver in linux (but less
functionality, I also was thinking to make a better implementation of
fakelb and name it hwsim802154).

With such driver you can create "virtual phy's" in Linux.

E.g. 2 phy's,


  6LoWPAN/etc   6LoWPAN/etc
   | |
  wpan node interface  wpan node interface
   | |
   mac802154 mac802154
   | |
   wpan-phy0 <--L1(memcpy)--> wpan-phy1

Descrption:
  - mac820154: Our 802154 SoftMAC stack
  - 6LoWPAN/etc: upper layer IPv6, foo stack
  - wpan node interface: a wpan node interface which does filtering

Now with a 802154raw native RIOT driver the following would be possible:


   RIOT native (Userspace)
 AF_PACKET RAW
   |6LoWPAN/etc   6LoWPAN/etc
   || |
  wpan monitor interface  wpan node interface  wpan node interface
   || |
   |mac802154 mac802154
   || |
   wpan-phy2 <-L1(memcpy)-> wpan-phy0 <--L1(memcpy)--> wpan-phy1

In this setup you can ping from Linux IPv6 stack the RIOT Stack which
running in userspace.

I think your use case would be look like the following which is also
be possible:

   RIOT native (Userspace)   OpenThread native (Userspace)
 AF_PACKET RAW  AF_PACKET RAW
   | |
   | |
  wpan monitor interface wpan monitor interface
   | |
   | |
   | |
   wpan-phy0  wpan-phy1

Then you could connect RIOT native with openthread native over the
fakelb driver (maybe also add Linux nodes or more RIOT/OpenThread
nodes).

I know somebody is working for adding such virtual driver in OpenThread,
but I think they want to use real hardware for that (which I don't
recommend). This is just for stack testing, there exists unsolved issues
with ACK handling etc and you really don't want to bypass the great
Linux IPv6 Stack :-).

I cc the guy/girl which wants to add this stuff to OpenThread.

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

Re: [riot-devel] Raw communication between native nodes

[Martine Lenders]

Hi,
have you checked out PR 5206 [1]? It isn't raw data transfer, but it
allows you to use PCAP files (the filetype wireshark uses) for netdev
communication (since PCAP also supports IEEE 802.15.4 this should work
for that). I think where I left things actual communication isn't
possible right now, but you can write PCAP files and read them, which
might be better anyways for testing since you can very precisely
control when you receive what data ;-).

Cheers,
Martine

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

2016-06-22 17:28 GMT+02:00 Jose Alamos :
> Hi,
>
> I was wondering if there's a way to send raw data between nodes running on
> native. I need to send OpenThread packets between nodes (through a radio
> abstraction), and I'm having problems with TAP interface since they only
> process ethernet frames.
>
> I tried to hack a little bit (put these OT packets in ethernet frames) but
> is not working well. Basically, I need to emulate a radio device.
>
> Is there an easy way to achieve this?
>
> Best regards.
>
> ___
> 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

[riot-devel] Raw communication between native nodes

[Jose Alamos]

Hi,

I was wondering if there's a way to send raw data between nodes running on
native. I need to send OpenThread packets between nodes (through a radio
abstraction), and I'm having problems with TAP interface since they only
process ethernet frames.

I tried to hack a little bit (put these OT packets in ethernet frames) but
is not working well. Basically, I need to emulate a radio device.

Is there an easy way to achieve this?

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

Re: [riot-devel] Problem with UDP and SAMR21-XPRO

[Alexandre Abadie]

Hi,

> though I do not have the same setup ready for testing, I _cannot_ confirm any
> problems with UDP on latest RIOT master branch.
> 
> I just tested UDP on a SAMR21-XPRO running gnrc_networking example and
> successfully send and received UDP data from and to a RasPi with Openlabs
> transceiver running netcat on latest Raspbian-Linux.
> 
> Could you clarify which RIOT branch/commit you use?

Latest master. From what you say, the problem comes from the RIOT BR.

Cheers,

Alex


> 
> Best,
>   Sebastian
> 
> > Am 21.06.2016 um 21:42 schrieb Alexandre Abadie
> > :
> > 
> > Hi Mattia,
> > 
> > Thanks for reporting this issue.
> > 
> >> I've discovered a possible bug in RIOT. I'm working with 2 samr21-xpro: on
> >> the first is running gnrc_border_router (I'll call it A) and on the other
> >> (I'll call it B) is running gnrc_networking. I've well configured my
> >> scenario infact I can ping both my nodes from linux shell. But, when I
> >> send
> >> a UDP packet to B (with nc) it is forwarded correctly on tap interface (I
> >> seen it on wireshark) but it arrives corrupted (wrong checksum) to B and
> >> it
> >> is dropped by UDP thread. I've enabled packet dump and the packet arrives
> >> with different packet lengths in ipv6 and udp headers (fixed to 8, it is
> >> the UDP header length) and the udp payload is removed.
> > 
> > I have the exact same problem although I didn't track it as deep as you
> > did.
> > 
> >> How can I fix this problem?
> > 
> > A regression was introduced 2 or 3 weeks ago in master and you could first
> > "git bisect" to try to identify the incriminated commit.
> > 
> > Thanks,
> > 
> > Alex
> > ___
> > 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
> 
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Problem with UDP and SAMR21-XPRO

[smlng]

Hi all,

though I do not have the same setup ready for testing, I _cannot_ confirm any 
problems with UDP on latest RIOT master branch.

I just tested UDP on a SAMR21-XPRO running gnrc_networking example and 
successfully send and received UDP data from and to a RasPi with Openlabs 
transceiver running netcat on latest Raspbian-Linux.

Could you clarify which RIOT branch/commit you use? 

Best,
  Sebastian

> Am 21.06.2016 um 21:42 schrieb Alexandre Abadie :
> 
> Hi Mattia,
> 
> Thanks for reporting this issue.
> 
>> I've discovered a possible bug in RIOT. I'm working with 2 samr21-xpro: on
>> the first is running gnrc_border_router (I'll call it A) and on the other
>> (I'll call it B) is running gnrc_networking. I've well configured my
>> scenario infact I can ping both my nodes from linux shell. But, when I send
>> a UDP packet to B (with nc) it is forwarded correctly on tap interface (I
>> seen it on wireshark) but it arrives corrupted (wrong checksum) to B and it
>> is dropped by UDP thread. I've enabled packet dump and the packet arrives
>> with different packet lengths in ipv6 and udp headers (fixed to 8, it is
>> the UDP header length) and the udp payload is removed.
> 
> I have the exact same problem although I didn't track it as deep as you did.
> 
>> How can I fix this problem? 
> 
> A regression was introduced 2 or 3 weeks ago in master and you could first 
> "git bisect" to try to identify the incriminated commit.
> 
> Thanks,
> 
> Alex
> ___
> 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] RIOT, Windows, and Code Composer Studio

[Clark Leach]

I am also using the newest version.  I'm sure it's probably not difficult,
it's just that makefiles are new to me...
On Jun 22, 2016 5:30 AM, "Attilio Dona"  wrote:

> Hi Clark,
>
> What CCS version are you using?
> In the past there was problems integrating the RIOT build system with CCS.
>
> I have just successfully tested a RIOT environment on windows with the
> latest (6.1.3).
>
> It is not difficult to setup a build configuration pointing to the RIOT
> makefile.
>
> Good tweakings
> Attilio
>
> On Mon, Jun 20, 2016 at 4:55 PM, Emmanuel Baccelli <
> emmanuel.bacce...@inria.fr> wrote:
>
>> Caeveat: coma at the end url may mess up your automatic URL detection
>> thingie:
>> https://github.com/RIOT-OS/RIOT/wiki/Using-the-Eclipse-IDE-for-C-and-CPP-Developers,-
>> Howto
>> On Jun 20, 2016 4:49 PM, "Emmanuel Baccelli" 
>> wrote:
>>
>>> Hi there
>>>
>>> I don't know how complete and up to date that is but there is also:
>>>
>>> https://github.com/RIOT-OS/RIOT/wiki/Using-the-Eclipse-IDE-for-C-and-CPP-Developers,-
>>> Howto
>>>
>>> Cheers
>>> Emmanuel
>>> On Jun 20, 2016 4:39 PM, "Francisco Javier Acosta Padilla" <
>>> francisco.aco...@inria.fr> wrote:
>>>
 Hi Clark!

 I’m not using CCS but Eclipse, although I use it only for editing code,
 it is possible to use it for compiling, flashing and debugging (in
 experimental phase).

 As for today, we don’t have a very complete guide on how to do it in
 RIOT, but there is a guide[1] for Contiki, which can be extended to RIOT.
 The guide assumes the use of GCC for compiling…

 Anyone knows if we can support other compilers? IMO it’s a matter of
 changing the prefixes of the compiler in the Makefile, but maybe some flags
 can differ...

 I hope it helps.

 Cheers,


 [1] https://github.com/Zolertia/Resources/wiki/Eclipse


 --
 Francisco Javier Acosta Padilla
 Research Engineer at INRIA Saclay
 INFINE Team

 On 20 June 2016 at 16:22:03, Ludwig Knüpfer (
 ludwig.knuep...@fu-berlin.de) wrote:

 Hi Clark,

 I am not aware of anyone using CCS.
 In my perception most of us are Linux based and don't even use Eclipse.

 Cheers,
 Ludwig

 Am 20. Juni 2016 15:59:29 MESZ, schrieb Clark Leach <
 clark.le...@gmail.com>:
 >Nothing? Really?
 >
 >On Tue, Jun 14, 2016 at 2:43 PM, Clark Leach 
 >wrote:
 >
 >> I am intersted in developing with RIOT for a few different TI targets
 >and
 >> have Code Composer Studio installed on Windoze 8.1 which I have used
 >for
 >> several projects. Since CCS already has all the tool chains and
 >debugger
 >> interfaces, it seems like it would make sense to use it for these
 >projects
 >> as well.
 >>
 >> Is there any hope of making such a configuration work? Is there any
 >> guidance available? I have read the howto on using Eclipse and found
 >the
 >> information lacking and, at times, incomprehensible (what is a
 >"speaking
 >> Variable Name", anyways).
 >>
 >> Any feedback would be appreciated.
 >>
 >>
 >
 >

 >
 >
 >___
 >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


 ___
 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
>>
>>
>
> ___
> 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] RIOT, Windows, and Code Composer Studio

[Attilio Dona]

Hi Clark,

What CCS version are you using?
In the past there was problems integrating the RIOT build system with CCS.

I have just successfully tested a RIOT environment on windows with the
latest (6.1.3).

It is not difficult to setup a build configuration pointing to the RIOT
makefile.

Good tweakings
Attilio

On Mon, Jun 20, 2016 at 4:55 PM, Emmanuel Baccelli <
emmanuel.bacce...@inria.fr> wrote:

> Caeveat: coma at the end url may mess up your automatic URL detection
> thingie:
> https://github.com/RIOT-OS/RIOT/wiki/Using-the-Eclipse-IDE-for-C-and-CPP-Developers,-
> Howto
> On Jun 20, 2016 4:49 PM, "Emmanuel Baccelli" 
> wrote:
>
>> Hi there
>>
>> I don't know how complete and up to date that is but there is also:
>>
>> https://github.com/RIOT-OS/RIOT/wiki/Using-the-Eclipse-IDE-for-C-and-CPP-Developers,-
>> Howto
>>
>> Cheers
>> Emmanuel
>> On Jun 20, 2016 4:39 PM, "Francisco Javier Acosta Padilla" <
>> francisco.aco...@inria.fr> wrote:
>>
>>> Hi Clark!
>>>
>>> I’m not using CCS but Eclipse, although I use it only for editing code,
>>> it is possible to use it for compiling, flashing and debugging (in
>>> experimental phase).
>>>
>>> As for today, we don’t have a very complete guide on how to do it in
>>> RIOT, but there is a guide[1] for Contiki, which can be extended to RIOT.
>>> The guide assumes the use of GCC for compiling…
>>>
>>> Anyone knows if we can support other compilers? IMO it’s a matter of
>>> changing the prefixes of the compiler in the Makefile, but maybe some flags
>>> can differ...
>>>
>>> I hope it helps.
>>>
>>> Cheers,
>>>
>>>
>>> [1] https://github.com/Zolertia/Resources/wiki/Eclipse
>>>
>>>
>>> --
>>> Francisco Javier Acosta Padilla
>>> Research Engineer at INRIA Saclay
>>> INFINE Team
>>>
>>> On 20 June 2016 at 16:22:03, Ludwig Knüpfer (
>>> ludwig.knuep...@fu-berlin.de) wrote:
>>>
>>> Hi Clark,
>>>
>>> I am not aware of anyone using CCS.
>>> In my perception most of us are Linux based and don't even use Eclipse.
>>>
>>> Cheers,
>>> Ludwig
>>>
>>> Am 20. Juni 2016 15:59:29 MESZ, schrieb Clark Leach <
>>> clark.le...@gmail.com>:
>>> >Nothing? Really?
>>> >
>>> >On Tue, Jun 14, 2016 at 2:43 PM, Clark Leach 
>>> >wrote:
>>> >
>>> >> I am intersted in developing with RIOT for a few different TI targets
>>> >and
>>> >> have Code Composer Studio installed on Windoze 8.1 which I have used
>>> >for
>>> >> several projects. Since CCS already has all the tool chains and
>>> >debugger
>>> >> interfaces, it seems like it would make sense to use it for these
>>> >projects
>>> >> as well.
>>> >>
>>> >> Is there any hope of making such a configuration work? Is there any
>>> >> guidance available? I have read the howto on using Eclipse and found
>>> >the
>>> >> information lacking and, at times, incomprehensible (what is a
>>> >"speaking
>>> >> Variable Name", anyways).
>>> >>
>>> >> Any feedback would be appreciated.
>>> >>
>>> >>
>>> >
>>> >
>>> >
>>> >
>>> >___
>>> >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
>>>
>>>
>>> ___
>>> 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
>
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] how to use riot os in IAR embedded workbench?

[Oleg Hahm]

Hi!

On Wed, Jun 22, 2016 at 04:20:52PM +0900, 신익희 wrote:
> I want to use riot in IAR embedded workbench because it's too hard using
> linux to me
> 
> please let me know how to port riot to IAR embedded workbench

It's been a long time since the last time I worked with IAR and I cannot
remember how exactly to configure it, but have you considered using Eclipse
with GCC on Windows instead if you're not feeling comfortable with Linux?
See https://github.com/RIOT-OS/RIOT/wiki/Build-RIOT-on-Windows-OS

Cheers,
Oleg
-- 
printk("WE HAVE A BUG HERE!!! stk=0x%p\n", stk);
linux-2.6.6/drivers/block/cciss_scsi.c


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

Re: [riot-devel] Boards with MAC 802.15.4e

[Oleg Hahm]

Hi Alessandro,

On Mon, Jun 20, 2016 at 05:53:14PM +0200, ALESSANDRO NICOLI wrote:
> Between the RIoT's supported boards,  what are those that support the MAC
> 802.15.4e standard ?

in general each IEEE 802.15.4 capable transceiver can be used. However, I
would advise to use the at86rf2xx as present on iotlab-m3 or SAMR21-Xplained.

Cheers,
Oleg
-- 
The four hard things in CS are cache invalidation, naming, and off-by-one
errors.


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

[riot-devel] how to use riot os in IAR embedded workbench?

[신익희]

I want to use riot in IAR embedded workbench because it's too hard using
linux to me

please let me know how to port riot to IAR embedded workbench

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