Re: [riot-devel] RIOT and Peripherals
Hi, Thanks Peter, The idea is if the pir detects something, then the speaker will produce a sound, for example for 2 minutes, then a udp message will be sent. I have some questions(as a newbie :) ) : - I didn't find the pwm.c file, maybe someone erased it during a clean up operation? -Is there any example of using the pwm lib? (mostly on the sequence of the function call) - There is a variable dev that points to the speaker device(as mentioned this lib was used with virtual devices), is there a specific integer for one device or it doesn't matter? ( void pwm_set(pwm_t dev, uint8_t channel, uint16_t value); ) -For the pir Library is it mandatory to register as a thread(?), it will be my main thread. I've seen the project of Mr. Nhat Pham, but the main idea is to use the RIOT OS as it is. Thank you in advance! Best regards, Ilias ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Notification: Biweekly virtual meeting @ Wed Oct 5, 2016 2pm - 3pm (RIOT Events)
Hey, On 10/05/2016 03:27 PM, Oleg Hahm wrote: > On Wed, Oct 05, 2016 at 03:16:11PM +0200, Martine Lenders wrote: >> >* How to prevent server problems we had at the weekend? >> > * downloads.riot-os.org was moved from kupfer to Kaspar's >> > server due to power outage at FU >> >* => Kaspar became single point of failure >> >* Solutions: >> > * More people access to kupfer >> >* Move to server at HAW (smlng can grant access to other people) >> >* More people access to Kaspar's server? > From my point of view, the most important view is getting rid of this single > point of failure Please don't get rid of me! ;) > - independent if it is hosted at FUB, HAW or Hetzner. We > should have at least one fallback server. For downloads.riot-os.org, kupfer worked fine for years without downtime. Let's have the domain point back there. My webserver can serve as backup, it is already set up. Oleg and I can set up automatic mirroring between the two, and maybe Oleg can provide access to the riot-os.org name server, so when sth like this happens the next time, we can switch more quickly. (The problem was prolonged because *noone* had a local copy of a needed file...) Kaspar signature.asc Description: OpenPGP digital signature ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] RIOT and Peripherals
Hi > - I didn't find the pwm.c file, maybe someone erased it during a clean up > operation? pwm need to be implemented for each supported platform, here is the sam3 one for example : https://github.com/RIOT-OS/RIOT/blob/master/cpu/sam3/periph/pwm.c > -Is there any example of using the pwm lib? (mostly on the sequence of the > function call) maybe here : https://github.com/RIOT-OS/RIOT/blob/master/tests/periph_pwm/main.c Hope this helps, Laurent -- « 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] Hacktoberfest
Hi Mathias, thanks for the hint! In my opinion, why not do it? Any other opinions out there? Shall we just create this label? Cheers Emmanuel On Wed, Oct 5, 2016 at 9:56 AM, Mathias Tausig < mathias.tau...@fh-campuswien.ac.at> wrote: > Hy! > > Some of you might already have seen, but GitHub and Digitalocean are > running the > "Hacktoberfest" this month[1]. To participate, one has to fix 4 issues or > start/finish 4 pull requests which have to labelled as "Hacktoberfest". If > you > succeed you get a T-shirt. > > I think that it might be a nice thing to improve participation and it > might even > be good to attract a new developer. So I'd suggest that all incoming pull > requests this month and some of the easier issues should be labeled thus. > > cheers > Mathias > > > [1]: https://hacktoberfest.digitalocean.com/ > > > ___ > 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] Hacktoberfest
Hey, On 10/07/2016 02:50 PM, Emmanuel Baccelli wrote: > Any other opinions out there? Shall we just create this label? +1. Kaspar ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Hacktoberfest
OK, I just created the label. So feel free to use it this month! We'll delete the label after our next release. Cheers, Emmanuel On Fri, Oct 7, 2016 at 2:53 PM, Kaspar Schleiser wrote: > Hey, > > On 10/07/2016 02:50 PM, Emmanuel Baccelli wrote: > > Any other opinions out there? Shall we just create this label? > > +1. > > Kaspar > ___ > 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] BIN FILES
Dear all, Is it possible to create a bin file, which includes everything and then flash the .bin file on the board? (From what I've seen RIOT OS doesn't support this, right) Thank you in advance! Best, Ilias ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] BIN FILES
Hi Ilias! On Fri, Oct 07, 2016 at 03:29:38PM +0200, Ilias Seitanidis wrote: > Is it possible to create a bin file, which includes everything and then > flash the .bin file > on the board? (From what I've seen RIOT OS doesn't support this, right) What exactly do you mean by ".bin" file? By default RIOT produces an ELF [1] file for most platforms that contain the full binary that is flashed onto the device. Cheers, Oleg [1] https://en.wikipedia.org/wiki/Executable_and_Linkable_Format -- Chuck Norris doesn't do TCP handshake - he does TCP roundhouse-kick to initiate the connection. signature.asc Description: PGP signature ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] BIN FILES
Hi, I guess you need glasses ;) If you have your target exported, then 'make' creates a binary image. 'make flash' flashes this image onto your board. Cheers, Ludwig Am 7. Oktober 2016 15:29:38 MESZ, schrieb Ilias Seitanidis : >Dear all, >Is it possible to create a bin file, which includes everything and then >flash the .bin file >on the board? (From what I've seen RIOT OS doesn't support this, >right) > >Thank you in advance! > >Best, >Ilias > > > > >___ >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] BIN FILES
If you want a binary file which is an exact byte-for-byte copy of the microcontroller ROM you can use objcopy to convert from ELF to raw binary. The RIOT build system also produces a HEX file for flashing, which is a plain-text variant of the raw binary. arm-none-eabi-objcopy -O binary myprog.elf myprog.bin You will not, however, need any of this manual handling for flashing the supported boards, `make flash` is all you need. Best regards, Joakim On Fri, Oct 7, 2016 at 3:35 PM, Oleg Hahm wrote: > Hi Ilias! > > On Fri, Oct 07, 2016 at 03:29:38PM +0200, Ilias Seitanidis wrote: > > Is it possible to create a bin file, which includes everything and then > > flash the .bin file > > on the board? (From what I've seen RIOT OS doesn't support this, > right) > > What exactly do you mean by ".bin" file? By default RIOT produces an ELF > [1] file > for most platforms that contain the full binary that is flashed onto the > device. > > Cheers, > Oleg > > [1] https://en.wikipedia.org/wiki/Executable_and_Linkable_Format > -- > Chuck Norris doesn't do TCP handshake - he does TCP roundhouse-kick to > initiate > the connection. > > ___ > 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] alternative socket-api
Hi, came across [0] today and remembers me that RIOT also plans some simple "conn" API for a bsd socket alternative. I just want to leave that on the mailinglist, maybe then RIOT can compare "conn" and [0]. - Alex [0] https://raw.githubusercontent.com/sustrik/dsock/master/rfc/sock-api-revamp-01.txt ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] RIOT and Peripherals
Hi, if you are on a samr21-xpro the pwm.c driver implementation can be found here: https://github.com/RIOT-OS/RIOT/blob/master/cpu/samd21/periph/pwm.c . The pin configurations on an Atmel samr21-xpro board are defined here: https://github.com/RIOT-OS/RIOT/blob/master/boards/samr21-xpro/include/periph_conf.h#L146 . As Laurent already said, an example lies here: https://github.com/RIOT-OS/RIOT/tree/master/tests/periph_pwm . I didn't really understand the question about the "variable dev" but probably the example will explain everything. There is no *need* to open a separate thread for the PIR but probably you want to. Did you already have a look at the PIR example under "tests": https://github.com/RIOT-OS/RIOT/tree/master/tests/driver_pir ? Best Peter Am 07.10.2016 um 12:58 schrieb Ilias Seitanidis: > Hi, > Thanks Peter, The idea is if the pir detects something, then the speaker > will produce a sound, for example for 2 minutes, then a udp message will be > sent. I have some questions(as a newbie :) ) : > - I didn't find the pwm.c file, maybe someone erased it during a clean up > operation? > -Is there any example of using the pwm lib? (mostly on the sequence of the > function call) > - There is a variable dev that points to the speaker device(as mentioned > this lib was used with virtual devices), is there a specific integer for > one device or it doesn't matter? ( > void pwm_set(pwm_t dev, uint8_t channel, uint16_t value); > ) > > -For the pir Library is it mandatory to register as a thread(?), it will be > my main thread. > > I've seen the project of Mr. Nhat Pham, but the main idea is to use the > RIOT OS as it is. > Thank you in advance! > > Best regards, > Ilias > > > > ___ > devel mailing list > devel@riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel > -- 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 ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] BIN FILES
Thank you all for your replies! @Ludwig I do wear glasses :) The problem is that I have a board based on samr21 but there is no edbg usb port, on the datasheet it mentions only reprogramming using a usb pen drive and a .bin file, I know nothing about the bootloader. 2016-10-07 15:45 GMT+02:00 Joakim Nohlgård : > If you want a binary file which is an exact byte-for-byte copy of the > microcontroller ROM you can use objcopy to convert from ELF to raw binary. > The RIOT build system also produces a HEX file for flashing, which is a > plain-text variant of the raw binary. > > arm-none-eabi-objcopy -O binary myprog.elf myprog.bin > > You will not, however, need any of this manual handling for flashing the > supported boards, `make flash` is all you need. > > Best regards, > Joakim > > On Fri, Oct 7, 2016 at 3:35 PM, Oleg Hahm wrote: > >> Hi Ilias! >> >> On Fri, Oct 07, 2016 at 03:29:38PM +0200, Ilias Seitanidis wrote: >> > Is it possible to create a bin file, which includes everything and then >> > flash the .bin file >> > on the board? (From what I've seen RIOT OS doesn't support this, >> right) >> >> What exactly do you mean by ".bin" file? By default RIOT produces an ELF >> [1] file >> for most platforms that contain the full binary that is flashed onto the >> device. >> >> Cheers, >> Oleg >> >> [1] https://en.wikipedia.org/wiki/Executable_and_Linkable_Format >> -- >> Chuck Norris doesn't do TCP handshake - he does TCP roundhouse-kick to >> initiate >> the connection. >> >> ___ >> 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] BIN FILES
Hi Ilias! On Fri, Oct 07, 2016 at 03:51:48PM +0200, Ilias Seitanidis wrote: > The problem is that I have a board based on samr21 but there is no edbg usb > port, on the datasheet it mentions only > reprogramming using a usb pen drive and a .bin file, I know nothing about > the bootloader. In this case, Joakim's advice should work. I think a similar trick is used for the mbed_lpc1768. Cheers, Oleg -- Yo mamma is so fat that she sat on a binary tree and made it a linked list in constant time. signature.asc Description: PGP signature ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
