Re: [riot-devel] arduino-uno support
Hi RIOT developers, Thanks to all who helps me merging my work in master ! For information, i plan to work on adding PWM support now. Regards, Laurent. 2016-09-03 15:45 UTC+02:00, Martine Lenders : > Hi Laurent, > > usually, a force-push is fine. > > Cheers, > Martine > > 2016-09-03 15:34 GMT+02:00 Laurent Navet : >> Hi, >> >> I now have a new git branch based on recent master which supports uno >> and duemilanove models. >> all common code is in boards/arduino-common and difference lives in >> boards/arduino-uno and boards/arduino-duemilanove. >> >> Should I push -f on original PR [1] ? >> Or it is cleaner to close [1] and open a new PR ? >> >> Regards, >> Laurent >> >> [1]https://github.com/RIOT-OS/RIOT/pull/5451 >> >> 2016-05-25 22:31 UTC+02:00, Martine Lenders : >>> Hi Laurent, >>> don't want to discourage you, but you do not have to update on this >>> mailing >>> list for every step you do. Just the major ones are enough ;-). Those of >>> us >>> interested (as for example me) will most likely follow your PR anyways. >>> >>> BTW: when you write your wiki page on the board can you add a section on >>> how to use the emulator? >>> >>> Regards, >>> Martine >>> >>> 2016-05-25 22:26 GMT+02:00 Laurent Navet : >>> Hi, Shared code between atmega260 and atmega328p now live in atmega_common, except startup.c which I dont find how to move it yet, certainly due to the "export UNDEF += $(BINDIR)cpu/startup.o" directive. Tests has been done on emulator since I don't have the mega2560. Regards, Laurent https://github.com/RIOT-OS/RIOT/pull/5451/commits/e1a317f807ed12785ec8d2c53bcbb0d470964676 ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel >>> >> >> >> -- >> « 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 > -- « 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 Laurent, usually, a force-push is fine. Cheers, Martine 2016-09-03 15:34 GMT+02:00 Laurent Navet : > Hi, > > I now have a new git branch based on recent master which supports uno > and duemilanove models. > all common code is in boards/arduino-common and difference lives in > boards/arduino-uno and boards/arduino-duemilanove. > > Should I push -f on original PR [1] ? > Or it is cleaner to close [1] and open a new PR ? > > Regards, > Laurent > > [1]https://github.com/RIOT-OS/RIOT/pull/5451 > > 2016-05-25 22:31 UTC+02:00, Martine Lenders : >> Hi Laurent, >> don't want to discourage you, but you do not have to update on this mailing >> list for every step you do. Just the major ones are enough ;-). Those of us >> interested (as for example me) will most likely follow your PR anyways. >> >> BTW: when you write your wiki page on the board can you add a section on >> how to use the emulator? >> >> Regards, >> Martine >> >> 2016-05-25 22:26 GMT+02:00 Laurent Navet : >> >>> Hi, >>> >>> Shared code between atmega260 and atmega328p now live in atmega_common, >>> except startup.c which I dont find how to move it yet, certainly due >>> to the "export UNDEF += $(BINDIR)cpu/startup.o" directive. >>> >>> Tests has been done on emulator since I don't have the mega2560. >>> >>> Regards, >>> Laurent >>> >>> >>> https://github.com/RIOT-OS/RIOT/pull/5451/commits/e1a317f807ed12785ec8d2c53bcbb0d470964676 >>> ___ >>> devel mailing list >>> devel@riot-os.org >>> https://lists.riot-os.org/mailman/listinfo/devel >>> >> > > > -- > « 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
Re: [riot-devel] arduino-uno support
Hi, I now have a new git branch based on recent master which supports uno and duemilanove models. all common code is in boards/arduino-common and difference lives in boards/arduino-uno and boards/arduino-duemilanove. Should I push -f on original PR [1] ? Or it is cleaner to close [1] and open a new PR ? Regards, Laurent [1]https://github.com/RIOT-OS/RIOT/pull/5451 2016-05-25 22:31 UTC+02:00, Martine Lenders : > Hi Laurent, > don't want to discourage you, but you do not have to update on this mailing > list for every step you do. Just the major ones are enough ;-). Those of us > interested (as for example me) will most likely follow your PR anyways. > > BTW: when you write your wiki page on the board can you add a section on > how to use the emulator? > > Regards, > Martine > > 2016-05-25 22:26 GMT+02:00 Laurent Navet : > >> Hi, >> >> Shared code between atmega260 and atmega328p now live in atmega_common, >> except startup.c which I dont find how to move it yet, certainly due >> to the "export UNDEF += $(BINDIR)cpu/startup.o" directive. >> >> Tests has been done on emulator since I don't have the mega2560. >> >> Regards, >> Laurent >> >> >> https://github.com/RIOT-OS/RIOT/pull/5451/commits/e1a317f807ed12785ec8d2c53bcbb0d470964676 >> ___ >> devel mailing list >> devel@riot-os.org >> https://lists.riot-os.org/mailman/listinfo/devel >> > -- « 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 Laurent, don't want to discourage you, but you do not have to update on this mailing list for every step you do. Just the major ones are enough ;-). Those of us interested (as for example me) will most likely follow your PR anyways. BTW: when you write your wiki page on the board can you add a section on how to use the emulator? Regards, Martine 2016-05-25 22:26 GMT+02:00 Laurent Navet : > Hi, > > Shared code between atmega260 and atmega328p now live in atmega_common, > except startup.c which I dont find how to move it yet, certainly due > to the "export UNDEF += $(BINDIR)cpu/startup.o" directive. > > Tests has been done on emulator since I don't have the mega2560. > > Regards, > Laurent > > > https://github.com/RIOT-OS/RIOT/pull/5451/commits/e1a317f807ed12785ec8d2c53bcbb0d470964676 > ___ > 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] arduino-uno support
Hi, Shared code between atmega260 and atmega328p now live in atmega_common, except startup.c which I dont find how to move it yet, certainly due to the "export UNDEF += $(BINDIR)cpu/startup.o" directive. Tests has been done on emulator since I don't have the mega2560. Regards, Laurent https://github.com/RIOT-OS/RIOT/pull/5451/commits/e1a317f807ed12785ec8d2c53bcbb0d470964676 ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] arduino-uno support
2016-05-24 21:51 UTC+02:00, Kaspar Schleiser : > Hey Laurent, > > awesome work so far! Thank's > On 05/24/2016 09:19 PM, Laurent Navet wrote: >> What should I do now to get it merged ? > > I just skimmed cpu/atmega328p. It looks like a lot of code is mostly > duplicate of cpu/arduino2560. > > We used to "merge if it works, unify later" many ports, but that "later" > tends to get forgotten, with bug fixes / improvements ending up in only > half of the branches... > > Could we find a way to consolidate arduino2560 and 328p and move shared > code into atmega_common? Sure, I'll look at that! ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] arduino-uno support
Hey Laurent, awesome work so far! On 05/24/2016 09:19 PM, Laurent Navet wrote: > What should I do now to get it merged ? I just skimmed cpu/atmega328p. It looks like a lot of code is mostly duplicate of cpu/arduino2560. We used to "merge if it works, unify later" many ports, but that "later" tends to get forgotten, with bug fixes / improvements ending up in only half of the branches... Could we find a way to consolidate arduino2560 and 328p and move shared code into atmega_common? Kaspar ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] arduino-uno support
Hi, A little update on the situation[1], What I have personnaly tested on real hardware and works fine is : - hello_world - timer_periodic_wakeup - ipc_pingpong What should I do now to get it merged ? From what I've read, I need to create a wiki board page, right ? Does it need more tests ? Or should I just wait for more reviewers ? Let me know what I can do to get this job done, Kind Regards, Laurent (aka Mali on FreeNode). [1] https://github.com/RIOT-OS/RIOT/pull/5451 -- « 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
Here is the Pull Request [1] As a newbie in deep embedded world, there are certainly mistakes or errors, so this is also an RFC. I thought i had an arduino uno, but in fact it was a duemilanove (the one with an atmega328p) so very similar to the uno. I've tested the hello-world example on it and seen the "You are running RIOT on a(n) arduino-uno board. This board features a(n) atmega328p MCU." :) Regards, Laurent [1] https://github.com/RIOT-OS/RIOT/pull/5451 -- « 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
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
Re: [riot-devel] arduino-uno support
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
Re: [riot-devel] arduino-uno support
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 :-). 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
[riot-devel] arduino-uno support
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
