And arduino due is supported on the upcoming 1.7 https://github.com/zephyrproject-rtos/zephyr/blob/v1.7-branch/boards/arm/arduino_due/doc/board.rst
On Thu, Mar 2, 2017 at 10:41 AM, Thiago Moura <thiagogcm at gmail.com> wrote: > +1 for dropping > > I don't have experince in this part but culd't support for ESP8266 be > achived in iotivity-constrained if zephyr has a FreeRTOS port? > > https://github.com/SuperHouse/esp-open-rtos > > It seems they will support Xtensa archtecture on 1.8: > https://jira.zephyrproject.org/projects/ZEP/issues/ZEP- > 1468?filter=allopenissues > > On Thu, Mar 2, 2017 at 10:09 AM, Philippe Coval < > philippe.coval at osg.samsung.com> wrote: > >> >> >> On 02/03/17 13:09, Carsten Bormann wrote: >> >>> On 24 Feb 2017, at 20:19, Dave Thaler via iotivity-dev < >>> iotivity-dev at lists.iotivity.org> wrote: >>> >>>> Arduino support >>>> >>> Arduino is a brand, >>> >> plus a collection of tools and libs, >> iotivity used "arduino" term as supported target "OS", >> which can be a bit misleading for baremetal development, >> I suggested once that we rename the ARDUINO macros to MCU >> or CONSTRAINED to ease porters jobs >> and then target more than arduino boards (such as ESPxx). >> >> >> not a platform; there are several, rather different platforms branded >>> Arduino. >>> Some of these have plenty of resources. >>> >>> What Arduino branded platforms was IoTivity addressing? >>> >> AFAIK, there were 2 : Due and mega >> >> I only have experience with Mega2560 with its Ethernet shield, >> and compatibles devices shipping Atmel's ATmega2560 >> >> https://www.arduino.cc/en/Main/arduinoBoardMega2560 >> >> http://www.atmel.com/Images/Atmel-2549-8-bit-AVR-Microcontro >> ller-ATmega640-1280-1281-2560-2561_datasheet.pdf >> >> What of these platforms are we trying to drop? >>> >> same ones.... >> >> Again I think it's good to keep avr gcc builders to "preserve our code >> quality standards", >> for runtime that's an other story, maybe arduino just could become a >> "community" supported port, >> in a branch starting from 1.2-rel. >> >> While iotivity-constrained could endorse support of those mentioned >> platforms above, >> >> Waiting for any feedback, then I will update this page: >> https://wiki.iotivity.org/hardware >> >> By the way, let me share to community more tips about prototyping using >> arduino : >> https://www.slideshare.net/SamsungOSG/iot-from-arduino-micro >> controllers-to-tizen-products-using-iotivity >> >> Hope this help >> >> -- >> >> mailto:philippe.coval at osg.samsung.com gpg:0x467094BC >> https://blogs.s-osg.org/author/pcoval/ >> >> _______________________________________________ >> iotivity-dev mailing list >> iotivity-dev at lists.iotivity.org >> https://lists.iotivity.org/mailman/listinfo/iotivity-dev >> > > > > -- > *Thiago Guedes Cunha de Moura* > Graduando em Ci?ncia da Computa??o > Instituto de Ci?ncias Exatas e Biol?gicas - Universidade Federal de Ouro > Preto > > cel.: (31)99484-9864 <(31)%2099484-9864> > > -- *Thiago Guedes Cunha de Moura* Graduando em Ci?ncia da Computa??o Instituto de Ci?ncias Exatas e Biol?gicas - Universidade Federal de Ouro Preto cel.: (31)99484-9864 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170302/a9919239/attachment.html>
