Re: [riot-devel] RIOT policy on hardware support without example board

2018-03-16 Thread Matthew Blue
Robert, I saw your port, unfortunately after I had already written mine. I did base my RTT code on your partial implementation. I thought that the PR was not active, since it has been waiting for about 6 months for PR #1610. You can see the RTT implementation here:

Re: [riot-devel] RIOT policy on hardware support without example board

2018-03-16 Thread Robert Hartung
Hi Matthew, I already ported the atmega1284p to RIOT: https://github.com/RIOT-OS/RIOT/pull/7604 Best Regards, Robert > Am 14.03.2018 um 18:49 schrieb Matthew Blue : > > Hello all, > > I am building mesh networking

Re: [riot-devel] RIOT policy on hardware support without example board

2018-03-16 Thread Matthew Blue
Hi everyone, Is it sufficient to have a RTC-only board with the ATmega1284P, and not have any example board with the other peripherals (that is, only a test application for each)? I think earlier I misinterpreted Joakim's answer to mean that there had to be a board for each peripheral rather than

Re: [riot-devel] RIOT policy on hardware support without example board

2018-03-16 Thread Bas Stottelaar
Hi all, I think this board would come close: it features the ATmega1284P with an RTC: https://www.microchip.com/DevelopmentTools/ProductDetails.aspx?PartNO=ATMEGA1284P-XPLD . Kind regards, Bas Stottelaar 2018-03-16 7:03 GMT+01:00 Joakim Nohlgård : > Hi again, > >

Re: [riot-devel] RIOT policy on hardware support without example board

2018-03-16 Thread Joakim Nohlgård
Hi again, Is there no readily available commercial dev boards which feature an RTC crystal? Generally, boards in the main repo have to be available commercially or at least accessible for a large number of users (IoT-lab boards for example are only available in the IoT-lab test sites, but they

Re: [riot-devel] RIOT policy on hardware support without example board

2018-03-15 Thread Matthew Blue
Hello Joakim, I do have such a board: the board I am developing for. I also already have it ported and passing many of the manual tests. However, my concern is that I do not anticipate this board being generally available, because of the kind of product it is going to be in. Is it okay for me to

Re: [riot-devel] RIOT policy on hardware support without example board

2018-03-15 Thread Joakim Nohlgård
Hi Matthew, Generally, everything in the main repository should be covered by the automatic compilation tests performed by the CI system, which is why all CPUs must have at least one board using them. Perhaps you have some development board which uses the same CPU that you can add a basic

[riot-devel] RIOT policy on hardware support without example board

2018-03-14 Thread Matthew Blue
Hello all, I am building mesh networking sensor arrays for agriculture, and I am working on RIOT as an operating system for them. I have a number of bits of hardware that I need to write support for and I would like to contribute that back to RIOT. However, since this is ag equipment designed to