[riot-devel] Arduino + Riot

ALESSANDRO NICOLI alessandro.nicoli at studenti.unipr.it
Mon Jun 13 19:53:06 CEST 2016


Yes, i added arduino.hpp instead of Arduino.h (or WProgram.h).
But it gives me back the "undefined reference error" to the DHT functions :


/RIOT/examples/arduino_DHT/_sketches.cpp:40: undefined reference to
`DHT::readHumidity(bool)'

RIOT/examples/arduino_DHT/_sketches.cpp:42: undefined reference to
`DHT::readTemperature(bool, bool)'

/RIOT/examples/arduino_DHT/_sketches.cpp:44: undefined reference to
`DHT::readTemperature(bool, bool)'

/RIOT/examples/arduino_DHT/_sketches.cpp:53: undefined reference to
`DHT::computeHeatIndex(float, float, bool)'

/RIOT/examples/arduino_DHT/_sketches.cpp:55: undefined reference to
`DHT::computeHeatIndex(float, float, bool)'


*saluti, *
*Alessandro*

2016-06-13 10:12 GMT+02:00 <devel-request at riot-os.org>:

> Send devel mailing list submissions to
>         devel at riot-os.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.riot-os.org/mailman/listinfo/devel
> or, via email, send a message with subject or body 'help' to
>         devel-request at riot-os.org
>
> You can reach the person managing the list at
>         devel-owner at riot-os.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of devel digest..."
>
>
> Today's Topics:
>
>    1. Running CC110x radio driver with iphc and netdev2_802154
>       (Mateusz Kubaszek)
>    2. Re: devel Digest, Vol 40, Issue 14 (ALESSANDRO NICOLI)
>    3. Working on port to SODAQ Autonomo (SAMD21) (Kees Bakker)
>    4. Re: devel Digest, Vol 40, Issue 14 (Laurent Navet)
>    5. Re: Working on port to SODAQ Autonomo (SAMD21) (Peter Kietzmann)
>    6. Re: Working on port to SODAQ Autonomo (SAMD21) (Cenk Gündogan)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 12 Jun 2016 19:37:10 +0200
> From: Mateusz Kubaszek <mathir.km.riot at gmail.com>
> To: devel at riot-os.org
> Subject: [riot-devel] Running CC110x radio driver with iphc and
>         netdev2_802154
> Message-ID: <575D9DC6.7090201 at gmail.com>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> Hello,
> Is there a possibility to run riot node with 6LoWPAN layer and IPHC
> compression with gnrc_netdev2_ieee802154 on CC110x radio driver? If yes,
> how to properly configure project?
>
> I'm making a sample mesh on my custom hardware and without the header
> compression 6LoWPAN network is senseless to make.
>
> Best regards,
> Mateusz Kubaszek
>
>
> ------------------------------
>
> Message: 2
> Date: Sun, 12 Jun 2016 20:50:17 +0200
> From: ALESSANDRO NICOLI <alessandro.nicoli at studenti.unipr.it>
> To: RIoT Dev List <devel at riot-os.org>
> Subject: Re: [riot-devel] devel Digest, Vol 40, Issue 14
> Message-ID:
>         <CAFsA-_1oH4jrx1PMeVw8gePhrQusQGuZmnGRaKDjgEyD4H=
> ADQ at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Thanks Laurent,
> I've another question about Arduino on Riot.
> How can i add third-part libraries in my arduino-riot project?
> I tried to add the DHT library (.h , .cpp) to *Rito/sys/Arduino/include/*
> but it depends on *Arduino.h *and the compile process gives me back an
> error about it (library not found).
> There is a way to specify in the Makefile the path of Arduino's libraries
> to avoid this problem?
>
> thanks and cheers,
> Alessandro
>
> *saluti, *
> *Alessandro*
>
> 2016-06-12 12:00 GMT+02:00 <devel-request at riot-os.org>:
>
> > Send devel mailing list submissions to
> >         devel at riot-os.org
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> >         https://lists.riot-os.org/mailman/listinfo/devel
> > or, via email, send a message with subject or body 'help' to
> >         devel-request at riot-os.org
> >
> > You can reach the person managing the list at
> >         devel-owner at riot-os.org
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of devel digest..."
> >
> >
> > Today's Topics:
> >
> >    1. Arduino + Riot (ALESSANDRO NICOLI)
> >    2. Re: Arduino + Riot (Laurent Navet)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Sat, 11 Jun 2016 16:30:25 +0200
> > From: ALESSANDRO NICOLI <alessandro.nicoli at studenti.unipr.it>
> > To: RIoT Dev List <devel at riot-os.org>
> > Subject: [riot-devel] Arduino + Riot
> > Message-ID:
> >         <CAFsA-_3dc1kVC_ZFO3W=
> > bD17pyVB1y5iiBP9F-Q_3da_xrjVSQ at mail.gmail.com>
> > Content-Type: text/plain; charset="utf-8"
> >
> > Hi RIOTers,
> > I saw the possibility of using Arduino code on Riot's supported boards,
> but
> > i'm wondering, the kernel still be the non RT Arduino kernel or uses the
> > Riot one (RT)?
> >
> >
> > *cheers, *
> > *Alessandro*
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> > URL: <
> >
> http://lists.riot-os.org/pipermail/devel/attachments/20160611/8f4ce6bc/attachment-0001.html
> > >
> >
> > ------------------------------
> >
> > Message: 2
> > Date: Sat, 11 Jun 2016 19:29:09 +0200
> > From: Laurent Navet <laurent.navet at gmail.com>
> > To: RIOT OS kernel developers <devel at riot-os.org>
> > Subject: Re: [riot-devel] Arduino + Riot
> > Message-ID:
> >         <
> > CAH7P7NjBHrNH5DkWSg00RTwS7ieB2og_cK5uc8VGqCdG-nqnow at mail.gmail.com>
> > Content-Type: text/plain; charset=UTF-8
> >
> > Hi alessandro,
> >
> > Arduino API is implemented upon RIOT core OS.
> > more info here :
> > https://github.com/RIOT-OS/RIOT/blob/master/sys/arduino/doc.txt
> >
> > 2016-06-11 16:30 UTC+02:00, ALESSANDRO NICOLI
> > <alessandro.nicoli at studenti.unipr.it>:
> > > Hi RIOTers,
> > > I saw the possibility of using Arduino code on Riot's supported boards,
> > but
> > > i'm wondering, the kernel still be the non RT Arduino kernel or uses
> the
> > > Riot one (RT)?
> > >
> > >
> > > *cheers, *
> > > *Alessandro*
> > >
> >
> >
> > --
> > « 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 »
> >
> >
> > ------------------------------
> >
> > Subject: Digest Footer
> >
> > _______________________________________________
> > devel mailing list
> > devel at riot-os.org
> > https://lists.riot-os.org/mailman/listinfo/devel
> >
> >
> > ------------------------------
> >
> > End of devel Digest, Vol 40, Issue 14
> > *************************************
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.riot-os.org/pipermail/devel/attachments/20160612/b450f866/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 3
> Date: Sun, 12 Jun 2016 21:14:52 +0200
> From: Kees Bakker <kees at sodaq.com>
> To: RIOT OS kernel developers <devel at riot-os.org>
> Subject: [riot-devel] Working on port to SODAQ Autonomo (SAMD21)
> Message-ID: <575DB4AC.7090802 at sodaq.com>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> Hi,
>
> This is a heads up to let you know I'm working on a port of
> RIOT to SODAQ Autonomo, which has an Atmel samd21 (like
> Arduino Zero).
>
> First I moved the existing cpu/samd21 tree to cpu/samr21. Then
> I added the samd21 CMSIS files from Arduino and the board files
> for the SODAQ Autonomo. For that, I copied several files from
> samr21-xpro.
>
> In the process I learned how to use the Atmel-ICE and how to
> debug via openocd. Nice :-)
>
> At the moment I can step through the hello world example. But
> I have no idea where the output is going. That's my next challenge.
>
> Meanwhile the changes and additions are available in my fork at
>
>      git at github.com:keestux/RIOT-OS
>
> Branch sodaq-autonomo.
>
> --
> Kees Bakker
> Founder
> SODAQ
> M. 0031617737165
> www.sodaq.com
>
>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 13 Jun 2016 09:43:03 +0200
> From: Laurent Navet <laurent.navet at gmail.com>
> To: RIOT OS kernel developers <devel at riot-os.org>
> Subject: Re: [riot-devel] devel Digest, Vol 40, Issue 14
> Message-ID:
>         <
> CAH7P7Ngrd5URq4GAug5SMqwrSS-yFGK4evthxbDrvUCB21rcBw at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> <alessandro.nicoli at studenti.unipr.it>:
> > Thanks Laurent,
> > I've another question about Arduino on Riot.
> > How can i add third-part libraries in my arduino-riot project?
> > I tried to add the DHT library (.h , .cpp) to *Rito/sys/Arduino/include/*
> > but it depends on *Arduino.h *and the compile process gives me back an
> > error about it (library not found).
>
> Have you tried include "arduino.hpp" instead ?
> it is located in sys/arduino/include
>
>
> ------------------------------
>
> Message: 5
> Date: Mon, 13 Jun 2016 09:56:10 +0200
> From: Peter Kietzmann <peter.kietzmann at haw-hamburg.de>
> To: RIOT OS kernel developers <devel at riot-os.org>
> Subject: Re: [riot-devel] Working on port to SODAQ Autonomo (SAMD21)
> Message-ID: <575E671A.9030102 at haw-hamburg.de>
> Content-Type: text/plain; charset="utf-8"; format=flowed
>
> Hi Kees,
>
> nice to see your interest in RIOT! Find some comments inline.
>
> Am 12.06.2016 um 21:14 schrieb Kees Bakker:
> > Hi,
> >
> > This is a heads up to let you know I'm working on a port of
> > RIOT to SODAQ Autonomo, which has an Atmel samd21 (like
> > Arduino Zero).
> >
> > First I moved the existing cpu/samd21 tree to cpu/samr21. Then
>
> Why? Well *if* there is a need to change the current RIOT code base, you
> should open a separate PR for that.
>
> This is a question to all: How comes the Atmel samr21-xplained pro board
> has "samd21" CPU in RIOT?
>
> > I added the samd21 CMSIS files from Arduino and the board files
> > for the SODAQ Autonomo. For that, I copied several files from
> > samr21-xpro.
>
> What was wrong with current CMSIS headers?
>
> https://github.com/RIOT-OS/RIOT/tree/master/cpu/samd21/include
>
> >
> > In the process I learned how to use the Atmel-ICE and how to
> > debug via openocd. Nice :-)
>
> Yepp :-)
>
> >
> > At the moment I can step through the hello world example. But
> > I have no idea where the output is going. That's my next challenge.
>
> By default the STDIO is mapped to UART_DEV(0) which will generally be
> the first device defined in the periph_conf.h file of the board. E.g.:
>
>
> https://github.com/RIOT-OS/RIOT/blob/master/boards/samr21-xpro/include/periph_conf.h#L108
>
> The driver used should be common for samX21 MCUs but is currently not.
>
> https://github.com/RIOT-OS/RIOT/blob/master/cpu/samd21/periph/uart.c
>
> For Kinetis there already is a great code reusability:
>
> https://github.com/RIOT-OS/RIOT/tree/master/cpu/kinetis_common/periph
>
> However, you could try to set up a different STDIO UART device and
> connect an external UART/USB converter to see if it's about conflicting
> pins.
>
> >
> > Meanwhile the changes and additions are available in my fork at
> >
> >      git at github.com:keestux/RIOT-OS
> >
> > Branch sodaq-autonomo.
> >
>
> Best
> Peter
>
> --
> 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
>
>
> ------------------------------
>
> Message: 6
> Date: Mon, 13 Jun 2016 10:11:54 +0200
> From: Cenk Gündogan <cenk.guendogan at fu-berlin.de>
> To: devel at riot-os.org
> Subject: Re: [riot-devel] Working on port to SODAQ Autonomo (SAMD21)
> Message-ID: <f1ec4431-30ed-b50c-e540-f2407ba6d1af at fu-berlin.de>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> Hey Peter,
>
> In [1] (Page 9) you can see that the samd21 is the actual microprocessor,
> while the atsamr21XXXX contains the samd21+transceiver.
> So I guess it has probably something to do with that (:
>
> Cheers,
> Cenk
>
> [1] http://www.atmel.com/Images/Atmel-42223%E2%80%93SAM-R21_Summary.pdf
>
> On 06/13/2016 09:56 AM, Peter Kietzmann wrote:
> > ...
> > This is a question to all: How comes the Atmel samr21-xplained pro
> > board has "samd21" CPU in RIOT?
> > ...
> > Best
> > Peter
> >
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> devel mailing list
> devel at riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
>
> ------------------------------
>
> End of devel Digest, Vol 40, Issue 15
> *************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/devel/attachments/20160613/1ec01eed/attachment-0001.html>


More information about the devel mailing list