Re: [riot-devel] Border-router and multicast
2016-05-12 21:03 GMT+02:00 Baptiste Clenet : > Thanks Martine, I will try tomorrow > > 2016-05-12 14:10 GMT+02:00 Martine Lenders : >> Hi, >> >> Ah the problem seems to be that for some reason Linux elects a link-local >> address for the ping, which is of course due to the fact, that there is no >> global address assigned to the interface and that the hop limit seems to be >> set to short (it is 1). So I did the following >> >> sudo ip route add ff1e::/16 dev tap0 table local # add routing entry for >> ff1e::1 >> sudo ip addr add affe::dc53:7dff:fe99:516e/64 dev tap0 # add global unicast >> address for tap0 >> ping6 -t 2 ff1e::1 # ping with hop limit 2 >> I did try but ping6 does not receive anything Did you do any more set up? What is this address dc53:7dff:fe99:516e? #ip -6 route list table local ... ff1e::/16 dev tap0 metric 1024 ... #ifconfig tap0 tap0 Link encap:Ethernet HWaddr 26:C5:07:2F:43:E0 inet6 addr: fe80::24c5:7ff:fe2f:43e0/64 Scope:Link inet6 addr: fe80::1/64 Scope:Link inet6 addr: affe::dc53:7dff:fe99:516e/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:58 errors:0 dropped:0 overruns:0 frame:0 TX packets:326 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:4706 (4.5 KiB) TX bytes:29442 (28.7 KiB) >> Now I get one reply back, and if you add affe::/64 to the fib of the border >> router the ethos interface (wasn't able to test that) it should work. >> >> Cheers, >> Martine >> >> >> 2016-05-12 13:34 GMT+02:00 Martine Lenders : >>> >>> Hi Baptiste, >>> yeah in that case multicast seems like the best thing to go. But how about >>> using an actual global address then: (ff:1e::1 e.g.; 10 flag = >>> non-permanent, e scope = global). With the hint by Kaspar I was able to get >>> the pings through the interface, but apparently the border router does not >>> forward the address. >>> Will investigate. >>> >>> Cheers, >>> Martine >>> >>> 2016-05-12 11:39 GMT+02:00 Baptiste Clenet : Hi, Martine, what I want: My set up: |Linux + RIOT BORDER ROUTER| |RIOT gnrc_networking A| |RIOT gnrc_networking B| |RIOT gnrc_networking C| |RIOT gnrc_networking D| I run a program on Linux which sends some UDP data to A B C D nodes. I want to use multicast in my program instead of one board by one bard Is it clearer? Cheers, 2016-05-11 21:55 GMT+02:00 Kaspar Schleiser : > Hey, > > On 05/11/2016 09:42 PM, Martine Lenders wrote: >> (2) I'm not sure you add multicast routing entries this way in Linux. > > You don't. If really desired, you have to use the "local" routing > table. > > # ip -6 route list table local > > Kaspar > ___ > devel mailing list > devel@riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel -- Baptiste ___ 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 >> > > > > -- > Baptiste -- Baptiste ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] mips port
Hi Leon, I see from the riot mailing list that you are working on a mips32 port of RIOT. Let me introduce myself, I manage the RTOS / embedded group at Imagination Technologies and one of the activities my group gets involved in is helping out open source RTOSes to improve their MIPS support, for example we have recently improved the MIPS support in FreeRTOS. TBH RIOT has be off radar somewhat as there was no MIPS support at all, we have been looking at RTOSes with some MIPS support already (usually PIC32 which is a somewhat specialised mips32 implementation) and trying to get the up-to-date with modern mips features. So its great to see someone working on MIPS support for RIOT and I would like to offer my assistance, be that loaning or donation of target hardware, or engineering resource (although we are a small teams) for patch reviewing and assisting with features etc. Cheers, Neil ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] arduino-uno support
Great, I'll cleanup code, test on real hardware and let you know. Thank's -- « On ne résout pas un problème avec les modes de pensée qui l’ont engendré. » « You cannot solve current problems with current thinking. Current problems are the result of current thinking » ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] arduino-uno support
Hi! First of all: I'm really excited about this. The atmega328p is a very widely used MCU and having support for RIOT would be wonderful. Thanks for the effort and definitely +100 for sharing with the community. On Fri, May 13, 2016 at 09:04:03AM +0200, Alexandre Abadie wrote: > I have one so I'll be able to give a try and test. As a side note, the > atmega328p has very limited ressources (32KB flash, 2KB SRAM) so this will > limit the use cases with RIOT (no network stack, etc). Yes, it's true that this MCU has very limited resources and it will be challenging to create a useful application. However, I think it can be possible to run a stripped-down network application with RIOT even on this. Without any code optimization a minimalistic GNRC application (examples/gnrc_minimal) requires about 3kB on Z1 (MSP430/16 bit). Compiling the same application for arduino-mega2560 requires about 1.8kB of RAM, but without a radio driver (and thus, without allocating stack for the L2 thread). Hence, we're already close! Cheers, Oleg P.S. Of course, even if GNRC (or another network stack) fits on the device, the challenge to leave space for a meaningful application remains. ;-) -- The problem UDP jokes signature.asc Description: PGP signature ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] arduino-uno support
Hi, I have one so I'll be able to give a try and test. As a side note, the atmega328p has very limited ressources (32KB flash, 2KB SRAM) so this will limit the use cases with RIOT (no network stack, etc). Alex - Mail original - > On Thu, May 12, 2016 at 11:01 PM, Martine Lenders > wrote: > > > Hi Laurent, > > definitely! If you have a working port, provide a PR as soon as you see > > fit. I personally only have a Arduino Leonardo, but it shouldn't be hard to > > find an Arduino Uno. Also: the simulated one could be helpful for future > > testing runs. Keep us in the loop :-). > > > > +1! > Emmanuel > > > > > > Cheers, > > Martine > > > > 2016-05-12 21:34 GMT+02:00 Laurent Navet : > > > >> Hi, > >> > >> Just to let you know that I have a basic port of the arduino-uno board > >> based on an atmega328p uc. > >> My work is largely based on the atmega2560 port. > >> For now, I've managed to build the hello-world and > >> timer_periodic_wakeup examples, and to load and execute generated .elf > >> using the simavr[1] emulator. > >> > >> .. > >> main(): This is RIOT! (Version: 2016.07-devel-114-gc449-paddy-uno). > >> Hello World!. > >> You are running RIOT on a(n) arduino-uno board.. > >> This board features a(n) atmega328p MCU.. > >> > >> Let me know if you're always interested by this port as suggested in > >> the Project Idea List[2. > >> Though, It certaily needs some cleanup and tests on real hardware before > >> PR. > >> > >> Regards, > >> Laurent > >> > >> [1] https://github.com/buserror/simavr > >> [2] https://github.com/RIOT-OS/RIOT/wiki/Project-Idea-List > >> > >> -- > >> « On ne résout pas un problème avec les modes de pensée qui l’ont > >> engendré. » > >> « You cannot solve current problems with current thinking. Current > >> problems are the result of current thinking » > >> ___ > >> 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
