Re: [riot-devel] Release 2020.10

[Emmanuel Baccelli]

Congrats to all involved! Thanks Koen for managing this release!
Cheers,
--Emmanuel

On Mon, Nov 2, 2020 at 11:04 AM José Ignacio Alamos <
jose.ala...@haw-hamburg.de> wrote:

> Hi,
>
> Very nice! Congratulations to everyone! Thanks Koen!
>
> Cheers,
> José
>
>
> On 20/11/01 06:18PM, Leandro Lanzieri wrote:
> > Hi all,
> >
> > Nice! Congratulations to everyone involved, and special thanks to Koen!
> >
> > Cheers,
> > Leandro.
> >
> > On Fri, 2020-10-30 at 18:30 +0100, Koen Zandberg wrote:
> > > And hopefully this time with newlines:
> > >
> > > Dear RIOTers,
> > >
> > > We are happy to announce the 25th official release of RIOT:
> > >
> > > --- * RIOT 2020.10 * ---
> > >
> > > The 2020.10 release includes:
> > >
> > >  - Support for PicoLIBC as standard C library implementation
> > >  - A new radio abstraction layer for ieee802.15.4 radios
> > >  - Improvement to the linking of modules
> > >  - An improved algorithm for generating local unique identifiers
> > >  - Pagewise addressing support for MTD devices
> > >  - 23 additional modules supported by Kconfig
> > >  - Initial rework of the clock modelling on stm32 devices
> > >  - 5 new boards, 2 new device drivers, 7 packages updated
> > >
> > > 482 pull requests, composed of 1355 commits, have been merged since
> > > the
> > > last release, and 84 issues have been solved. 64 people contributed
> > > with
> > > code in 94 days. 2426 files have been touched with 133358 (+)
> > > insertions and
> > > 756906 deletions (-).
> > >
> > > You can download the RIOT release from Github by cloning the
> > > repository
> > > and checkout the release tag [1] or by downloading the tarball [2],
> > > and
> > > look up the release notes for further details [3].
> > >
> > > A big thank you to everybody who contributed!
> > >
> > > Best regards,
> > > Koen Zandberg
> > >
> > >
> > > [1]:https://github.com/RIOT-OS/RIOT/tree/2020.10
> > >
> > > [2]:https://github.com/RIOT-OS/RIOT/archive/2020.10.tar.gz
> > >
> > > [3]:https://github.com/RIOT-OS/RIOT/releases/tag/2020.10
> > > ___
> > > devel mailing list
> > > devel@riot-os.org
> > > https://lists.riot-os.org/mailman/listinfo/devel
> > --
> > Leandro Lanzieri Rodriguez
> > Hamburg University of Applied Sciences
> > Berliner Tor 7, 20099 Hamburg, Germany, Room 4.81c
> > Dept. Computer Science, Internet Technologies Group
> > http://inet.haw-hamburg.de/members/leandro-lanzieri
> > Phone: +49 40 42875 - 8426
>
>
>
> > ___
> > 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

[riot-devel] [RIOT Summit '20] Videos available

[Emmanuel Baccelli]

Dear all,

the RIOT Summit '20 took place last week, online.
For those who missed it, you can now check out videos of talks and
break-out sessions at:
 https://www.youtube.com/playlist?list=PLDXXQJiSjPKHpZpiPee7OYaJpUmmfV6Nh

Cheers,

--Emmanuel
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] RIOT Summit 2020 -- Sept. 14-15 -- An Online Event

[Emmanuel Baccelli]

Dear RIOTers,

The fifth RIOT Summit  will take place on
September 14-15, 2020.

The event is online. Two days feature single-track presentations,
breakout sessions, and a hands-on coding tutorial. If you
want to attend, please register as soon as possible via
https://riot-summit2020.eventbrite.com/ .

**Talks**

Keynote : "Smaller is Safer" by Andrew S. Tanenbaum.

Further talks will cover IoT Security, IoT Networking,
Energy Management, and IoT Use Cases & Applications.

More speakers: https://summit.riot-os.org/2020/#speakers

**Tutorial**

A half-day webinar will guide newcomers on Day 1
including a series of hands-on activities with RIOT.
No specific hardware necessary, attendees will
be given access to the necessary online tools,
and instructions on required preliminary setup.

**Agenda**

Full program at a glance:
https://summit.riot-os.org/2020/#program

iCal to add in your calendar:
https://calendar.google.com/calendar/ical/hulgsh6e1fvpkorg29vpd22ac4%40group.calendar.google.com/public/basic.ics

**Registration**

Participation at the RIOT Summit is free of charge. However,
registration is required: https://riot-summit2020.eventbrite.com/

**Participation**

This year, due to Covid-19, the RIOT Summit will happen online.
Remote presence & online participation will be via common tools
(e.g., in-browser video conferencing & chat, details to be announced).

**Supporters**

We thank FU Berlin, HAW Hamburg, and Inria for their support.


Looking forward to meet you all online!


-- the Organizers, on behalf of the RIOT community
Contact: sum...@riot-os.org
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Release 2020.07

[Emmanuel Baccelli]

Yay! Congrats to all involved and special thanks to Martine for managing
this release!
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] RIOT Summit 2020: second call for contributions

[Emmanuel Baccelli]

2nd CALL FOR CONTRIBUTIONS

RIOT Summit 2020

September 14-15, 2020

Participation options: online & on-site
(f2f meeting to be confirmed, at Station F, Paris, France)

https://summit.riot-os.org



The RIOT community gathers yearly at the RIOT Summit, which brings
together RIOTers, beginners, and experts, as well as people interested
in the IoT in general and decision makers who plan to deploy RIOT in the
future. The event combines plenary talks, hands-on tutorials, and demos.

A preliminary batch of talks have been announced, more to come!
Announced talks include so far talks from IETFers, Arm Ltd., Huawei,
from several SMEs and Makers from the RIOT community. Check it out:
https://summit.riot-os.org/2020/#speakers

If you want to present a talk, a tutorial, or a demo (whether online or
onsite!)
please consider our Call for Contributions, still open!

  * https://summit.riot-os.org/2020/call-for-contributions

We are looking forward to your proposals!

Every year since 2016, the RIOT Summit was successful in providing
a forum to connect. We aim to continue this tradition in 2020,
with some changes catering for online participation. We will try
our very best to create the special RIOT Summit atmosphere online,
as well as onsite (f2f to be confirmed, at French Tech Central in
Station F, Paris, France).

Best regards,
the organizers, on behalf of the RIOT community
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Release 2020.04

[Emmanuel Baccelli]

Congrats to all involved!!! And special thanks to Leandro for managing this
release!
Cheers

On Thu, Apr 30, 2020 at 1:44 PM Cenk Gündoğan 
wrote:

> My applause to the community, and my respect to Leandro for this smooth
> release (: Thanks!
>
> Cheers,
> Cenk
>
> On Thu, Apr 30 2020 at 13:25 +0200, Leandro Lanzieri wrote:
>
> > Dear RIOTers,
> >
> > We are happy to announce the 23rd official release of RIOT:
> >
> > --- * RIOT 2020.04 * ---
> >
> > The 2020.04 release includes:
> >
> > - Add support for 6LoWPAN IPv6 extension header next header compression
> > - Add support for DHCPv6 prefix delegation client
> > - Add support for kw41zrf and at86rf215 IEEE 802.15.4 radios
> > - Improvements on power management for ESP32
> > - Improvements and extensions in support of fe310 and lpc2387
> > - lwIP: provide support for asynchronous sock
> > - Improvements on xtimer module and testing
> > - Initial addition of the new timer subsystem: ztimer
> > - Migration to Kconfig - phase I: add multiple GNRC and system modules
> > - +10 new boards, +11 new drivers, +7 new packages
> >
> > 555 pull requests, composed of 1514 commits, have been merged since the
> > last release, and 22 issues have been solved. 60 people contributed
> > with code in 102 days. 3346 files have been touched with 358398 (+)
> > insertions and 184720 deletions (-).
> >
> > You can download the RIOT release from Github by cloning the repository
> > and checkout the release tag [1] or by downloading the tarball [2], and
> > look up the release notes for further details [3].
> >
> > A big thank you to everybody who contributed! And special thanks to
> > everyone who helped out during the release testing and provided bug
> > fixes!
> >
> > Best regards,
> >
> > Leandro.
> >
> >
> > [1]:https://github.com/RIOT-OS/RIOT/tree/2020.04
> >
> > [2]:https://github.com/RIOT-OS/RIOT/archive/2020.04.tar.gz
> >
> > [3]:https://github.com/RIOT-OS/RIOT/releases/tag/2020.04
> >
> > ___
> > 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

[riot-devel] RIOT Summit 2020: Call for Contributions

[Emmanuel Baccelli]

CALL FOR CONTRIBUTIONS

RIOT Summit 2020

September 14-15, 2020

Participation options: online & on-site
(f2f meeting to be confirmed, at Station F, Paris, France)

https://summit.riot-os.org



The RIOT community gathers yearly at the RIOT Summit, which brings
together RIOTers, beginners, and experts, as well as people interested
in the IoT in general and decision makers who plan to deploy RIOT in the
future. The event combines plenary talks, hands-on tutorials, and demos.

Every year since 2016, the RIOT Summit was successful in providing
a forum to connect. We aim to continue this tradition in 2020,
with some changes catering for online participation. We will try
our very best to create the special RIOT Summit atmosphere online,
as well as onsite (f2f to be confirmed, at French Tech Central in
Station F, Paris, France).

The organizers of the RIOT Summit call for contributions that relate to
RIOT and the Internet of Things. If you want to present a talk, a
tutorial, or a demo (whether online or onsite!) please consider the Call
for Contributions:

  * https://summit.riot-os.org/2020/call-for-contributions


Best regards,
the organizers, on behalf of the RIOT community
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] RIOT sprint day

[Emmanuel Baccelli]

On Fri, Mar 20, 2020 at 1:45 PM Kaspar Schleiser 
wrote:

> Hey Martine,
>
> On 3/19/20 11:39 AM, Martine Sophie Lenders wrote:
> > So you judge this as a hen and egg then? There is no interest, since not
> > many people know about it, so there is no advertisement for it since not
> > enough interest was generated.
>
> Well, I had pitched the idea on maintainers@, and noone but Francisco
> replied. We then started the thing, and announced that again at the VMA
> [1], with zero feedback. I thought at this point at least every
> maintainer is aware of it happening and who to contact if there's
> further interest.
>

(adding missing ref ;)
[1]
https://github.com/RIOT-OS/RIOT/wiki/VMA-2020-02-minutes#riot-sprint-day-kaspar



> > However, IMHO with more advertisement and
> > more transparency this could be easily resolved.
>
> Totally, let's just do that. It was the plan anyways. From now on, we'll
> send invitations on maintain...@riot-os.org, either a day early or on
> Tuesdays in the morning. We'll also start writing up how the workflow
> looks like, probably on some wiki page.
> There's also the Github Project [2] for anyone interested in watching
> the progress.
>
> We've discussed a bit, and came to the conclusion that the format is not
> really suitable for non-maintainers. The idea is that people both review
> and get reviewed (their PRs that is). So for now, the Sprint Day will be
> maintainers only. Everyone else, please come join the monthly Hack'n'Acks!
>
> Happy hacking,
> Kaspar
> [2] https://github.com/RIOT-OS/RIOT/projects/26
> ___
> 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] Release 2020.01

[Emmanuel Baccelli]

On Mon, Feb 3, 2020 at 11:15 PM Kaspar Schleiser 
wrote:

>
> On 2/3/20 10:02 PM, Francois-Xavier Molina wrote:
> > We are happy to announce the 22nd official release of RIOT:
>
> Congrats everyone!
>
> Awesome job managing the release, Francisco!
>

+1

cheers!

--Emmanuel
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Release 2019.10

[Emmanuel Baccelli]

Yay! Congrats to all involved, and thanks a bunch Ken for managing this
release!
Cheers
Emmanuel

On Thu, Oct 31, 2019 at 2:17 PM Ken Bannister  wrote:

> Dear RIOTers,
>
> We are happy to announce the 21st official release of RIOT:
>
> --- * RIOT 2019.10 * ---
>
> The 2019.10 release includes:
>
>   - initial support for SUIT firmware updates
>   - USB CDC-ACM serial communication
>   - complete rewrite of TI CC110x radio driver
>   - initial support for IPv6 fragmentation
>   - DTLS support in the sock networking stack
>   - complete blockwise messaging for gcoap and nanocoap
>   - as always, bug fixes and documentation updates
>
> About 460 pull requests, composed of 950 commits, have been merged since
> the
> last release, and about 60 issues have been solved. 57 people
> contributed with
> code in 105 days. Approximately 2000 files have been touched with 129000
> insertions and 25000 deletions.
>
> You can download the RIOT release from Github by cloning the repository
> and checkout the release tag [1] or by downloading the tarball [2], and
> look up the release notes for further details [3].
>
> A big thank you to everybody who contributed! Special thanks to previous
> release managers @miri64, @MrKevinWeiss, and @PeterKietzmann for offline
> advice. Many thanks also to release testers @aabadie, @cladmi, @fjmolinas,
> @jia200x, @leandrolanzieri, and @smlng.
>
> Your friendly neighborhood release manager,
> Ken Bannister
>
>
> [1] https://github.com/RIOT-OS/RIOT/tree/2019.10
>
> [2] https://github.com/RIOT-OS/RIOT/archive/2019.10.tar.gz
>
> [3] https://github.com/RIOT-OS/RIOT/releases/tag/2019.10
>
> ___
> 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] Leaving the project

[Emmanuel Baccelli]

Hi Gaetan

thanks for your intense commitment so far, and all the best for your next
adventures!

Cheers

Emmanuel


On Fri, Oct 18, 2019, 12:27 Gaëtan Harter 
wrote:

> Hi RIOT developers,
>
> I will am leaving my job today so will most likely disappear from the
> RIOT project. I was hoping to finish more reviews but the last weeks
> were quite busy. Feel free to take over the issues and changes you are
> interested in.
>
> If you want to stay in contact in the future, use my private email
> address hartergae...@gmail.com.
>
> Cheers,
> Gaëtan @cladmi
>
>
> ___
> 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] [riot-users] Release 2019.07

[Emmanuel Baccelli]

Belated yay! Congrats to all involved and thanks Kevin for managing this
release!
Cheers
Emmanuel

On Mon, Jul 29, 2019 at 9:48 AM Gaëtan Harter 
wrote:

> Hi,
>
> Congratulations!
>
> Gaëtan
>
> On 7/25/19 12:37 PM, Martine Lenders wrote:
> > Hi,
> >
> > Congretulations!
> >
> > Cheers,
> > Martine
> >
> > Am Do., 25. Juli 2019 um 11:46 Uhr schrieb Kevin Weiss <
> > kevin.we...@haw-hamburg.de>:
> >
> >> Dear RIOTers,
> >>
> >> we are happy to announce the 20th official release of RIOT:
> >>
> >> --- * RIOT 2019.07 * ---
> >>
> >> The 2019.07 release includes a number of new features including many new
> >> boards and cpu, riotboot added to many new and old boards, USB is now
> available,
> >> BLE improvements, Ethernet on stm32 platforms, as well as many bug
> fixes and
> >> documentation updates. Testing has also improved with both On-Target
> Testing
> >> increasing and now Hardware Assisted Automated Tests being run.
> >>
> >> About 300 pull requests with about 659 commits have been merged since
> the last
> >> release and about 50 issues have been solved. 26 people contributed
> with code
> >> in 106 days. Approximately 1377 files have been touched with 181993
> insertions
> >> and 19668 deletions.
> >>
> >> You can download the RIOT release from Github by cloning the repository
> >> and checkout the release tag [1] or by downloading the tarball [2], and
> >> look up the release notes for further details [3].
> >>
> >>
> >> A big thank you to everybody who contributed!
> >>
> >> Best regards,
> >> Kevin Weiss
> >>
> >>
> >> [1]:https://github.com/RIOT-OS/RIOT/tree/2019.07
> >>
> >> [2]:https://github.com/RIOT-OS/RIOT/archive/2019.07.tar.gz
> >>
> >> [3]:https://github.com/RIOT-OS/RIOT/releases/tag/2019.07
> >>
> >> ___
> >> users mailing list
> >> us...@riot-os.org
> >> https://lists.riot-os.org/mailman/listinfo/users
> >>
> >
> >
> > ___
> > 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] Incorporating OMG Data-Distribution Service for Real-Time Systems (DDS)

[Emmanuel Baccelli]

Hi Brenton

I do not know of such effort currently taking place. There was some work in
this direction in the past, but it was discontinued, as fas as I know.

Best,

Emmanuel

On Tue, Jul 2, 2019, 14:15 Brenton Chetty  wrote:

> Hi Guys
>
> Is anyone currently working on incorporating DDS into RIOT?
>
> With regards
> Brenton
> ___
> 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] Embench: benchmark for class 1 IoT devices / MCUs

[Emmanuel Baccelli]

Hi there,

I just stumbled over this, which I thought some of you might find of
interest:

Some people (from the RISC-V crowd, apparently) have started to set up a de
facto standard benchmark for Class 1  IoT devices / microcontrollers.

They explicitly target devices with typically Flash ≤64 KiB and RAM ≤16
KiB, and aim to benchmark characteristics including Code Size, Context
Switching Time, Interrupt Latency , Power.

https://www.sigarch.org/embench-recruiting-for-the-long-overdue-and-deserved-demise-of-dhrystone-as-a-benchmark-for-embedded-computing/

Cheers,

Emmanuel
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] CC2538dk Riotboot support

[Emmanuel Baccelli]

FYI I opened a PR adding a WIP porting guide:
https://github.com/RIOT-OS/RIOT/pull/11597

On Mon, May 27, 2019 at 2:43 PM Gaëtan Harter 
wrote:

> On 5/27/19 2:36 PM, Emmanuel Baccelli wrote:
> > Seems to me that a quick riotboot porting guide could be useful somewhere
> > in the wiki.
> >
>
> More in the `riotboot` documentation in the repository I would say.
>
> >
> > On Mon, May 27, 2019 at 2:30 PM Gaëtan Harter <
> gaetan.har...@fu-berlin.de>
> > wrote:
> >
> >> Hi Brenton,
> >>
> >> if you only use the default `riotboot/flash` or `flash` in
> >> `tests/riotboot` targets, you do not need flasher changes.
> >> But you should not use `riotboot/flash-slot0` and `riotboot/flash-slot1`
> >> targets for the moment.
> >>
> >> To have the support declared and merged in RIOT, it also needs to
> >> support flashing the `slot-` firmwares alone. These require having
> >> flasher that can flash with an offset`.
> >>
> >> For `cc2538-bsl.py` it looks like there is the `-a` option for this.
> >>
> >> Maybe changing it to use `IMAGE_OFFSET` if set would be enough.
> >> An example is in
> >>
> >>
> https://github.com/RIOT-OS/RIOT/blob/8fe12bc82cfbb83a90efd018e11c044d0a40696b/makefiles/tools/edbg.inc.mk#L14-L15
> >>
> >> The `flash.sh` is currently using `jlink` without using the common
> >> `jlink` scripts thing, it is in my todo list after
> >> https://github.com/RIOT-OS/RIOT/pull/11554 to migrate to use the common
> >> one where applicable.
> >>
> >> Cheers,
> >> Gaëtan
> >>
> >> On 5/24/19 2:32 PM, Francisco Acosta wrote:
> >>> Hi Brenton!
> >>>
> >>> So far I remember we didn't take it into account, and I don't know if
> >>> someone is taking care of it.
> >>>
> >>> As far as I know, there are two ways of supporting that CPU:
> >>>
> >>> 1. The way we do it now, which is linking the image in another start
> >>> address so the bootloader can recognise it and boot it.
> >>>
> >>> 2. Modify the start address on the CC2538 register dedicated to this.
> >>> This might be a bit tricky but also interesting for the sake of
> research
> >>> and compatibility.
> >>>
> >>> However, I'd advice the first option to have the full benefits of the
> >>> bootloader and struggling less with the particular settings on that
> >>> chip.
> >>>
> >>> Overall, the steps would be the following:
> >>>
> >>> 1. Adapt the linker scripts to succeed tests/cortexm_common_ldscript.
> >>> This consists on making the linker scripts on cpu/cc2838/ldscripts
> >>> comply with cpu/cortexm_common/ldscrpts/cortexm.ld. You might take a
> >>> look how is it done for stm32 or sam0 families.
> >>>
> >>> 2. Provide the length and start variables to link slots correctly:
> >>> - ROM_LEN
> >>> - RAM_LEN
> >>> - ROM_START_ADDR
> >>> - RAM_START_ADDR
> >>>
> >>> Again, take a look on the supported CPUs as examples.
> >>>
> >>> 3. Make tests/riotboot pass
> >>>
> >>> 4. Perform a firmware update or flash different firmwares with
> different
> >>> versions so the bootloader choses the newest.
> >>>
> >>> Optionally you might want to test if the WIP SUIT update format works.
> >>>
> >>> Don't hesitate to make more questions if you have some!
> >>>
> >>> Cheers,
> >>>
> >>> Paco.
> >>>
> >>>
> >>> On 24/05/2019 13:43, Brenton Chetty wrote:
> >>>> Hey guys, has anyone succeeded in providing riotboot support for the
> >>>> cc2538dk board as yet?
> >>>>
> >>>> ___
> >>>> 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
> >
> ___
> 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] Notification: Hack'n'ACK @ Tue May 28, 2019 5pm - 10pm (CEST) (RIOT Events)

[Emmanuel Baccelli]

Some of us are already on Jitsi at https://meet.jit.si/riot-hacknack
Cheers!
Emmanuel


On Mon, May 27, 2019 at 5:11 PM Martine Lenders 
wrote:

> Hi,
>
> this is a reminder or maybe new information for some: The Hack'n'ACK this
> month will start in Berlin (and Paris?) tomorrow already at 3pm. If we see
> a success in the number of attendance, this might become a regular thing.
>
> Kind regards,
> Martine
>
> Am Mo., 27. Mai 2019 um 17:01 Uhr schrieb Google Calendar <
> calendar-notificat...@google.com>:
>
>> more details »
>> 
>> Hack'n'ACK
>> https://meet.jit.si/riot-hacknack
>> 
>> *When*
>> Tue May 28, 2019 5pm – 10pm Central European Time - Berlin
>>
>> *Where*
>> FU Berlin; HAW Hamburg (map
>> )
>>
>> *Calendar*
>> RIOT Events
>>
>> *Who*
>> •
>> Martine Lenders - creator
>>
>> Invitation from Google Calendar 
>>
>> You are receiving this email at the account peterschme...@gmail.com
>> because you are subscribed for notifications on calendar RIOT Events.
>>
>> To stop receiving these emails, please log in to
>> https://www.google.com/calendar/ and change your notification settings
>> for this calendar.
>>
>> Forwarding this invitation could allow any recipient to send a response
>> to the organizer and be added to the guest list, or invite others
>> regardless of their own invitation status, or to modify your RSVP. Learn
>> More .
>> ___
>> 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] CC2538dk Riotboot support

[Emmanuel Baccelli]

Seems to me that a quick riotboot porting guide could be useful somewhere
in the wiki.


On Mon, May 27, 2019 at 2:30 PM Gaëtan Harter 
wrote:

> Hi Brenton,
>
> if you only use the default `riotboot/flash` or `flash` in
> `tests/riotboot` targets, you do not need flasher changes.
> But you should not use `riotboot/flash-slot0` and `riotboot/flash-slot1`
> targets for the moment.
>
> To have the support declared and merged in RIOT, it also needs to
> support flashing the `slot-` firmwares alone. These require having
> flasher that can flash with an offset`.
>
> For `cc2538-bsl.py` it looks like there is the `-a` option for this.
>
> Maybe changing it to use `IMAGE_OFFSET` if set would be enough.
> An example is in
>
> https://github.com/RIOT-OS/RIOT/blob/8fe12bc82cfbb83a90efd018e11c044d0a40696b/makefiles/tools/edbg.inc.mk#L14-L15
>
> The `flash.sh` is currently using `jlink` without using the common
> `jlink` scripts thing, it is in my todo list after
> https://github.com/RIOT-OS/RIOT/pull/11554 to migrate to use the common
> one where applicable.
>
> Cheers,
> Gaëtan
>
> On 5/24/19 2:32 PM, Francisco Acosta wrote:
> > Hi Brenton!
> >
> > So far I remember we didn't take it into account, and I don't know if
> > someone is taking care of it.
> >
> > As far as I know, there are two ways of supporting that CPU:
> >
> > 1. The way we do it now, which is linking the image in another start
> > address so the bootloader can recognise it and boot it.
> >
> > 2. Modify the start address on the CC2538 register dedicated to this.
> > This might be a bit tricky but also interesting for the sake of research
> > and compatibility.
> >
> > However, I'd advice the first option to have the full benefits of the
> > bootloader and struggling less with the particular settings on that
> > chip.
> >
> > Overall, the steps would be the following:
> >
> > 1. Adapt the linker scripts to succeed tests/cortexm_common_ldscript.
> > This consists on making the linker scripts on cpu/cc2838/ldscripts
> > comply with cpu/cortexm_common/ldscrpts/cortexm.ld. You might take a
> > look how is it done for stm32 or sam0 families.
> >
> > 2. Provide the length and start variables to link slots correctly:
> >- ROM_LEN
> >- RAM_LEN
> >- ROM_START_ADDR
> >- RAM_START_ADDR
> >
> > Again, take a look on the supported CPUs as examples.
> >
> > 3. Make tests/riotboot pass
> >
> > 4. Perform a firmware update or flash different firmwares with different
> > versions so the bootloader choses the newest.
> >
> > Optionally you might want to test if the WIP SUIT update format works.
> >
> > Don't hesitate to make more questions if you have some!
> >
> > Cheers,
> >
> > Paco.
> >
> >
> > On 24/05/2019 13:43, Brenton Chetty wrote:
> >> Hey guys, has anyone succeeded in providing riotboot support for the
> >> cc2538dk board as yet?
> >>
> >> ___
> >> 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] [riot-maintainer] Release 2019.04

[Emmanuel Baccelli]

Nice! Congrats to all involved! And thanks Dan for managing this one!
Cheers
Emmanuel

On Thu, May 2, 2019 at 11:31 AM Kaspar Schleiser 
wrote:

> Hey everyone,
>
> On 4/29/19 4:01 PM, Daniel Petry wrote:
> > we are happy to announce the 19th official release of RIOT:
>
> congratulations and big thanks to everyone involved!
>
> Special thanks to Dan. Good job managing the release and I'm sorry to
> see you leave!
>
> Kaspar
> ___
> Maintainer mailing list
> maintai...@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/maintainer
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Checkpoining and Prague

[Emmanuel Baccelli]

Hi Gero

On Fri, Mar 22, 2019 at 8:49 AM Gero Müller  wrote:

>
> For now we use the MSP430FR5969 platform (see
> https://github.com/RIOT-OS/RIOT/pull/11012) but we plan to include /
> switch to RISC-V in future. Maybe a port of our checkpointing to RISC-V
> would be a valid topic for the hackathon?
>

Interesting topic!
The IETF hackathon is typically more about network protocol stuff *but*
since checkpointing is indirectly tied with sleeping node management,
it's not completely out of scope and I guess you will indeed find some
RIOTers to talk to.
Join the SUIT / RIOT tables, you'll meet people.

See you tomorrow,

Emmanuel
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Coordination for oxidize conference (Berlin, ~2019-04-27)

[Emmanuel Baccelli]

Hi Christian,

thanks for the heads up! Looks interesting. We could indeed organize such
that some RIOTers (whom exactly is t.b.d) would attend to give a talk and
answer Q

Best,

Emmanuel

On Wed, Jan 30, 2019 at 9:35 AM chrysn  wrote:

> Hi,
>
> there will be a conference event embedded systems and IoT development in
> Rust in Berlin 2019-04-26 to -29 called oxidize[1]. I'm about to enter a
> presentation on using RIOT as an operating system with Rust applications
> built atop of it at its CFP.
>
> Given the event, according to the CFP description, "cover[s] broader
> embedded topics", this might be an interesting event for not directly
> Rust related embedded operating system development. Therefore:
>
> Would anyone here be interested in coming there, and possibly to help
> out with general RIOT questions that come up in Q, or even to join me
> for a (30' rather than the 15' I'm planning) combined "*What is RIOT,
> and* how can it be used with Rust" talk?
>
> Best regards
> Christian
>
> [1]: https://oxidizeconf.com/
>
> --
> There's always a bigger fish.
>   -- Qui-Gon Jinn
> ___
> 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] [riot-users] RIOT-os meet-up at FOSDEM

[Emmanuel Baccelli]

Hi Koen,
I won't be at FOSDEM, but based on recent email exchanges, it seems Daniele
will be around.
(and maybe you could have happy discussions about bootloaders, SUIT etc. ;)
Cheers
Emmanuel

On Tue, Jan 29, 2019 at 1:30 PM Koen  wrote:

> Hi all,
>
> As I will be visiting FOSDEM again this year, I was wondering if there
> are more people from the RIOT-os community attending. From what I've
> read, there won't be a RIOT-os stand this year, but if there is some
> interest for a small meet-up anyway, I can try to get us a timeslot in
> one of the BoF rooms.
>
> Please let me know if you would like to meet up at FOSDEM and whether
> you have a strong preference for either saturday or sunday for the meet-up.
>
> Cheers,
> Koen
>
>
> ___
> users mailing list
> us...@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/users
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] wolfSSL package and secure-boot demo

[Emmanuel Baccelli]

Hi Daniele,

thanks a lot for sharing! Looks very interesting.
A propos: I suppose you also have seen this other recent bootloader
riotboot [1] fly by?

>From what I understand, the applicability and approach are similar, except
the HAL itself is provided by a minimal version of RIOT.
We used riotboot for our SUIT-based secure firmware update demo over CoAP
and low-power radio last summer [2] [3].
A PR in the pipe for the SUIT parser...

Possible next steps I see: extend your demo to also enable the use of
CoAP+radio?
(and extend the riotboot demo to also enable the use of USB for transport ;)

Cheers!

Emmanuel

[1] https://github.com/RIOT-OS/RIOT/tree/master/bootloaders/riotboot
[2]
https://github.com/suit-wg/Hackathon-Interim-Berlin/blob/master/README.md
[3]
https://github.com/suit-wg/Hackathon-Interim-Berlin/blob/master/SUIT-Berlin-Hackathon-recap.pdf


On Mon, Jan 28, 2019 at 9:08 AM Daniele Lacamera  wrote:

> Dear RIOTers,
>
> I've recently modified PR #10308 to update wolfSSL/wolfCrypt version and
> include support for single-precision math, in order to improve
> performance and reduce resource requirements for TLS/DTLS.
>
> We confirm our intention to support and maintain our port in the future,
> if there is interest from the community to include the package in the
> RIOT-OS distribution. Please let us know if we can help with the code
> review process, and/or there are still actions required from our side to
> finalize the inclusion.
>
> Moreover, we've been working on a off-tree secure-boot and update demo
> GPL application, using our mcu bootloader (wolfBoot) in combination with
> RIOT-OS. This demo targets samr21-xpro board, but should be relatively
> easy to port the full secure boot to other targets as well.
>
> The bootloader is integrated through a set of makefile rules contained
> in wolfboot.mk. Some automation to re-link the application at the given
> address has been inspired by the work previously done by Francisco to
> showcase a similar solution with mcuboot.
>
> Links:
>
> The open PR:
> https://github.com/RIOT-OS/RIOT/pull/10308
>
> wolfBoot secure bootloader:
> https://github.com/wolfSSL/wolfBoot
>
> wolfBoot+RIOT-OS demo:
> https://github.com/wolfSSL/wolfBoot-examples/tree/master/riotOS-samr21
>
> Hope to see (some of) you at FOSDEM next weekend!
>
> Have a nice day,
>
> --
> Daniele
> ___
> 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] PhyNode connecting to Raspberry Pi

[Emmanuel Baccelli]

Hi Anna,

if I am not mistaken,  your PhyNode is communicating via a IEEE 802.15.4
radio transceiver.
So for your raspberryPi to be able to communicate with it, you need to add
a IEEE 802.15.4 transceiver to your  Pi as described in [1], for instance
with an Openlab module  [2].

Emmanuel


[1]
https://github.com/RIOT-OS/RIOT/wiki/How-to-install-6LoWPAN-Linux-Kernel-on-Raspberry-Pi#raspberrypi-with-openlabs-raspberry-pi-802154-radio
[2] https://openlabs.co/OSHW/Raspberry-Pi-802.15.4-radio


On Mon, Jan 21, 2019 at 9:14 AM Aïcha Diack 
wrote:

> Dear Developers,
>
> My question is about the connecting possibilities with the PhyNode Board
> Kw 2x. I found it on your list and I was able to flash the board with Riot
> os. Now my problem is to connect it to my raspberryPi3 which has an
> raspberry pi radio modul. I need the Accelerometer values on my raspberry
> to work with them.
> I would be really happy if someone could give me a hint of which code I
> need or how I can realize my project.
>
> Sincerely
> Anna
> ___
> 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] Embedded World 2019

[Emmanuel Baccelli]

Hi Federico,

last year we had a RIOT booth at FOSDEM, but this year we do not.
However, maybe some RIOTers attend and could meet nevertheless?
(Personally I can't attend this year, unfortunately).

Cheers,

Emmanuel

On Sun, Jan 13, 2019 at 6:34 AM Federico Pellegrin 
wrote:

> Hi,
> Very nice, sadly I'm on work trip that week so will not be at EW.
>
> On the similar topic I was already wondering from some time: is any
> RIOTer attending (and/or presenting something) at FOSDEM
> (https://fosdem.org/2019/) in Brussels (2nd and 3rd February) maybe?
>
> Cheers,
> Federico
>
>
> Il giorno sab 12 gen 2019 alle ore 13:28 Matthias Waehlisch
>  ha scritto:
> >
> > Dear RIOTers,
> >
> >   just to let you know: Some of the RIOT maintainers will present RIOT
> > at the Embedded World 2019 (https://www.embedded-world.de/en).
> >
> > When
> > * February 26-28, 2019
> >
> > Where
> > * Hall 4, stand 4-168 (OSADL booth)
> > * Nuremberg, Germany
> >
> >
> >   That might be a perfect chance to meet your fellow RIOTers f2f.
> >
> >   If you are an exhibitor who shows something that is based on RIOT,
> > please share!
> >
> >
> >
> >
> > Thanks
> >   matthias
> >
> >
> > --
> > Matthias Waehlisch
> > .  Freie Universitaet Berlin, Computer Science
> > .. http://www.cs.fu-berlin.de/~waehl
> > ___
> > 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

[riot-devel] Feature freeze for Release 2019.01

[Emmanuel Baccelli]

Dear RIOTers,

the feature freeze (for major impact new features) will be effective at
midnight.

As a gentle reminder: the final feature freeze (for other PRs) is January
18th.

Wishing you a happy code/polish/review/merge sprint,

Cheers,

Alex & Emmanuel



>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Cortex M33 support

[Emmanuel Baccelli]

A crucial feature about this new arch is the availability of secure vs
non-secure execution environment within the same chip.
=> we need to design how to leverage these 2 environments (simultaneously)
with RIOT.

On Wed, Oct 17, 2018 at 4:43 PM Juan Ignacio Carrano 
wrote:

>
>
> On 10/17/18 4:19 PM, Alexandre Abadie wrote:
> > Hi,
> >
> > Not M33, but Microchip is also selling an evaluation board with an M23.
> >
> > See
> https://uk.farnell.com/microchip/dm320205/kit-eval-xplained-pro-32-bits/dp/2901261
> >
> > Alex
> >
> > PS: I'm not working on it.
> >
>
> Excellent. The basic CPU support for box cortex should be roughly the
> same (something like "armv8_common"), am I right?
>
> I wonder how many of the new features are usable in RIOT. The stack
> limit seems interesting.
>
> Regards,
>
> Juan.
> ___
> 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] Binding in Javascript

[Emmanuel Baccelli]

Hi Manar,

FYI, complementing this PR, some additional work was done
providing more bindings e.g. CoAP bindings
as reported in this paper: https://hal.inria.fr/hal-01766610/document

If you look at the code in this branch [1]
you should be able to find code that does just that.

Best,

Emmanuel

[1]
https://github.com/emmanuelsearch/RIOT/tree/riot.js.demo.iotlab/examples/javascript

On Wed, Sep 26, 2018 at 1:19 PM Juan Ignacio Carrano 
wrote:

> Hi Manar,
>
> On 9/26/18 12:12 PM, Manar Zaboub wrote:
> > Hello,
> >
> > using the provided example[1] I was able to run Javascript engine
> > (Jerryscript) on RIOT.
> >
> > I want to now bind additional functions to Javascript, for example to be
> able to start TCP communication using Javascript code.
> >
>
> Great! We would greatly appreciate if you contributed the bindings.
>
> > Can you please refer me to any examples or tutorials where binding
> functions in Javascript with RIOT is taking place?
>
> See https://github.com/RIOT-OS/RIOT/pull/7796/ . The PR is unmerged, but
> it contains what you are looking for.
>
> Regards,
>
> Juan.
> ___
> 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] Driver design rules in RIOT

[Emmanuel Baccelli]

Hi there,

based on this exchange,
is there matter for a wiki page on this?
(Or for alternative documentation,
e.g. reviving the concept of RDM [1] ?)

Best

Emmanuel

[1] https://github.com/RIOT-OS/RIOT/pull/6191


On Wed, Sep 26, 2018 at 11:38 AM Gunar Schorcht  wrote:

> Hi Hauke,
>
> many thanks for your comprehensive and clearifying answers. Most of them
> met my thoughts about driver design.
>
> >> - Should a driver support at least data-ready interrupts (if possible at
> >> all) to realize event-driven data retrieval?
> > If the driver comes with a 'full/extra' configuration, this is part of
> > it anyway, right? In the simples 'basic' configuration I don't think
> > this needs to be part of I would say.
>
> Agreed.
>
> >> - Should a driver always return normalized/converted data, or rather
> >> return the raw data and the application needs to convert them? The
> >> conversion is sometimes quite complex. I saw both approaches of them for
> >> similar sensors.
> > My opinion is quite clear: I am always in favor of returning
> > normalized/converted data. In 90% of the cases the conversion is not
> > expensive, so just do it. In those rare cases, where the conversions is
> > actually relatively expensive, we can always fall back by providing
> > additional `xx_read_raw()` or similar functions, that allow to access
> > the data before conversion.
>
> Agreed. All the drivers I wrote til now, either return
> normalized/converted and raw data with same read function or offer an
> additional read_raw function.
>
> >> The design rules that are clear to me are:
> >>
> >> - Drivers have to provide an interface for polling with init and read
> >> that is compatible with SAUL.
> > that is a nice to have, but not a MUST.
>
> Ok.
>
> >> - Output are always 16 bit integers.
> > Not quite true. The SAUL interface is build around 16-bit integers, and
> > at least when reading/writing data via SAUL the data needs to be
> > converted. But the driver specific interface can always use other data
> > types/lengths. If it is however easily possible to use int16, one should
> > use it.
>
> Ok.
>
> >> What else?
> > All this information should go into the 'device driver guide'
> > (
> https://github.com/RIOT-OS/RIOT/wiki/Guide:-Writing-a-device-driver-in-RIOT
> ).
> > This guide needs however still work - and I will not have the time to do
> > it. So it would be nice if other people can help here :-)
>
> Agreed.
>
> Regards
> Gunar
>
> --
> Wenn du laufen willst, lauf eine Meile. Wenn du ein neues Leben
> kennenlernen willst, dann lauf Marathon. (Emil Zatopek)
>
> ___
> 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] [riot-maintainer] CI news

[Emmanuel Baccelli]

Nice! Thanks Martine!
Was last night's build supposed to show up too, at this point?
Cheers
Emmanuel

On Sun, Sep 9, 2018 at 6:04 PM Kaspar Schleiser  wrote:

> Hey everyone,
>
> thanks to Martine we now have a nice new view for our nightly builds:
>
> https://ci.riot-os.org/nightlies.html
>
> There are many more improvements to Murdock and the accompanying
> scripts, but they're under the hood and thus more or less invisible. But
> they'll allow for more nice features and visual improvements in the future.
>
> Thanks Martine!
>
> Kaspar
> ___
> Maintainer mailing list
> maintai...@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/maintainer
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Proposal for sys folder

[Emmanuel Baccelli]

Hi José,

thanks for tackling this!

On Wed, Aug 29, 2018 at 11:16 AM Jose  wrote:

>
>1. Move the `net` folder to the RIOTBASE folder (`sys/net` -> `sys`):
>
> I suppose you mean '/sys/net' ->'/net'
This idea has been floating around for a while, and I think there was
consensus at some point on doing that.
Just never got to be done ;)
+1 from my side.


>
>1. Add a `lib` folder in the RIOTBASE:
>   1. Move cryptos, serializers, parsers, math, etc. to this `lib`
>   folder.
>   2. Keep RIOT sys related stuff in the `sys` folder. This could be,
>   for instance, stuff in direct communication with the RIOT kernel and 
> layers
>   interacting with periphs (auto_init, xtimer, power management, maybe 
> file
>   systems).
>
>
> Sounds sensible to me, but others may have more informed opinions.

Cheers

Emmanuel


> Looking forward to your comments.
>
> Cheers,
>
> José
>
> [1]: http://doc.riot-os.org/group__net.html
> [2]:
> https://courses.linuxchix.org/kernel-hacking-2002/08-overview-kernel-source.html
> ___
> 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] Release 2018.07

[Emmanuel Baccelli]

Yeah! Congrats to all involved, and thanks Gaëtan for managing this release!
Cheers
Emmanuel

On Tue, Aug 14, 2018 at 8:11 AM Gaëtan Harter 
wrote:

> Dear RIOTers,
>
> we are happy to announce the 16th official release of RIOT:
>
> --- * RIOT 2018.07 * ---
>
> The 2018.07 release includes new features, like NimBLE (ble stack),
> a MQTT-SN client, SHA-1 based PRNG, an UUID implementation. The RISC-V
> CPU architecture support used by the hifive1 board.
> Effort was done on refactoring, documentation, test improvements and bug
> fixes.
>
> During the last release, maintainers contributed by running the
> automated test suites on their boards. This gave valuable feedback on
> the board support state, test reliability and where to focus effort to
> make testing easier and more reliable.
>
> About 380 pull requests with about 675 commits have been merged since
> the last release and about 27 issues have been solved. 45 people
> contributed with code in 93 days. Approximately 1678 files have been
> touched with 147122 insertions and 16060 deletions.
>
> You can download the RIOT release from Github by cloning the repository
> and checkout the release tag [1] or by downloading the tarball [2], and
> look up the release notes for further details [3].
>
> Many thanks to all of you contributing in so many different ways to make
> RIOT worthwhile!
>
> Best Regards,
> Gaëtan - @cladmi
>
> [1]: https://github.com/RIOT-OS/RIOT/tree/2018.07
> [2]: https://github.com/RIOT-OS/RIOT/archive/2018.07.tar.gz
> [3]: https://github.com/RIOT-OS/RIOT/releases/tag/2018.07
> ___
> 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] Save the date: RIOT Summit 2018

[Emmanuel Baccelli]

Hi Carsten,

yes, hotels seem to be mostly filled up, unfortunately.
Nevertheless, that are still some things left:
I was able to book something OK-ish on booking.com today.
Else, it seems some things still pop up on airbnb, for those who use that.

Emmanuel



On Mon, Aug 6, 2018 at 4:51 PM Carsten Bormann  wrote:

> Guten Tag Matthias,
>
> wir wollten gerade mal die Hotels für den RIOT-Summit buchen.
>
> Denkste.  https://show.ibc.org
>
> Das nächste mal nehmt Ihr Hannover während der HMI?
> Berlin während der Grünen Woche oder der ITB?
>
> Ich befürchte, das wird diesmal ohne uns stattfinden.
> Sorry, das mir das nicht früher aufgefallen ist…
>
> Grüße, Carsten
>
>
> > On Mar 14, 2018, at 11:34, Matthias Waehlisch 
> wrote:
> >
> > Dear RIOTers,
> >
> >  after very successful RIOT Summits in 2016 and 2017, the third RIOT
> > Summit is scheduled for September 13-14, 2018 in Amsterdam.
>
>
> ___
> 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] Low power options for STM32 (L432) boards

[Emmanuel Baccelli]

Hi Patrick,

welcome to RIOT!
I'm not the best specialist of the topic, maybe others will have
complementary advice (or may correct me).
Can you scan through the wikipage on this topic [1] ?

For the L4, pm is not there yet.
What you could do is look at [2] an consider extending for L4.
Then if you mimic what is done for the L0 [3] by activating the pm_layered
module,
you will have access to the api: if you activate pm_layered, you have
access to pm_set for manual setting (or you can let pm_layered autopilot
the pm).
There are some use cases with GPIO or UART which require special care /
manual settings.

And: contributions are welcome!

Cheers

Emmanuel

[1] https://github.com/RIOT-OS/RIOT/wiki/Power-Management
[2] https://github.com/RIOT-OS/RIOT/blob/master/cpu/stm32_common/periph/pm.c
[3] https://github.com/RIOT-OS/RIOT/blob/master/cpu/stm32l0/Makefile.include

On Thu, May 24, 2018 at 8:43 AM, Patrick Ciccone 
wrote:

> Hello All,
> We are looking at possibly using RIOT for a product we are developing, and
> so far we really like how well RIOT functions.  One thing that is crucial
> for us is to minimize power usage down to the absolute minimum allowable.
> I have been looking into this and am having a hard time find documentation
> on the PM section.  I was wondering what level of effort it would take to
> implement the sleep, or standby function, and how well RIOT plays with
> that. Any pointers or example implementation of board specific low power
> modules or documentation would be greatly appreciated.
>
> Thank you,
>
>
> --
> [image: sensemetrics]  *Patrick Ciccone*
> Hardware Engineer
> 619.485.0575 |  San Diego, CA
> www.sensemetrics.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] [riot-users] Release 2018.04

[Emmanuel Baccelli]

Yeehah!
Thanks to everyone involved and to Kaspar for managing this release!
Cheers
Emmanuel

On Fri, May 11, 2018 at 6:09 PM, Kaspar Schleiser 
wrote:

> Dear RIOTers,
>
> we are happy to announce the 15th official release of RIOT:
>
> --- * RIOT 2018.0 * ---
> The 2018.04 release includes major progress in support for current
> crypto libraries. A lot of work has gone into updating drivers to RIOT's
> unified configuration scheme. Support for ten new boards has been added.
> In our quest to improve and automate testing, many test scripts have
> been fixed and improved, and RIOT's CI now runs many tests on real
> hardware during its nightly build testing. And as usual, many tiny fixes
> and improvements have been merged.
>
> About 390 pull requests with about 1073 commits have been merged since
> the last release and about 54 issues have been solved. 44 people
> contributed with code in 98 days. Approximately 1491 files have been
> touched with 208426 insertions.
>
> You can download the RIOT release from Github by cloning the repository
> and checkout the release tag [1] or by downloading the tarball [2], and
> look up the release notes for further details [3].
>
> Many thanks to all of you contributing in so many different ways to make
> RIOT worthwhile!
>
> Kaspar
>
> [0]: https://github.com/RIOT-OS/RIOT/blob/master/CODE_OF_CONDUCT.md
> [1]: https://github.com/RIOT-OS/RIOT/tree/2018.04
> [2]: https://github.com/RIOT-OS/RIOT/archive/2018.04.tar.gz
> [3]: https://github.com/RIOT-OS/RIOT/releases/tag/2018.04
> ___
> users mailing list
> us...@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/users
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Porting RIOT to ESP8266

[Emmanuel Baccelli]

Hi Gunar,


On Sat, Apr 14, 2018 at 10:22 AM, Gunar Schorcht 
wrote:

> That's true, it uses its own toolchain. But, at least some parts of the
> source code, e.g., thread and interrupt handling, could be reused.
> Handling of peripherals like GPIO, UART, SPI, I2C, timers a.s.o. are
> propably completely different. And, of course ESP32 is a dual core chip.
>
> I will try the port to ESP32 once my ESP8266 port is stable enough.
>
>
+1
FYI at FOSDEM this year, one of the most frequent question we got was "when
will RIOT be ported to ESP32"?

cheers

Emmanuel


> On 13.04.2018 23:54, Hawkboy wrote:
> > I don't think so.
> >
> > ESP32 would need its own port since it uses a different xtensa
> toolchain...
> >
> >
> > On 12/04/2018 11:56, Mathias Tausig wrote:
> >> Du you know, if your port will work on the ESP32 (the successor of the
> ESP8266),
> >> too?
> >>
> >> cheers
> >> Mathias
> >>
> >> On Mon, 2018-02-26 at 13:00 +0100, Gunar Schorcht wrote:
> >>> Hi,
> >>>
> >>> I just want to let the community to know that I'm trying an ESP8266
> >>> port. At the moment
> >>>
> >>> - the core's thread interface is implemented and tested,
> >>> - the core's irq interface is implemented and tested,
> >>> - GPIO handling module periph_gpio is implemented and tested,
> >>> - small applications like ipc_pingpong with interrupts and some I/O are
> >>> already working.
> >>>
> >>> My next steps are to implement perihph_timer module (I'm currently
> >>> working on), periph_uart module, periph_spi module and some networking.
> >>>
> >>> I started with two different approaches that are both working until now
> >>>
> >>> - a bare metal implementation, and
> >>> - an implementation on top of the community SDK esp-open_sdk.
> >>>
> >>> I really like the bare-metal implementation and would prefer this
> >>> approach since it gives more control over the hardware, requires less
> >>> resources and fits better RIOT-OS's core implementation approach.
> >>> Furthermore, it is generic enough that it might run on other Xtensa
> >>> processors.
> >>>
> >>> However, once networking using the proprietary WIFI hardware is needed,
> >>> it becomes unfortunately necessary to use proprietary SDK components.
> So
> >>> it seems, that I will continue the SDK approach first.
> >>>
> >>> Implementing RIOT-OS on top of the SDK is a bit tricky because the SDK
> >>> already uses tasks to control the hardware timers, the WIFI hardware,
> >>> the network connectivity, and so on. Therefore, it is necessary to give
> >>> away the task control to the SDK from time to time to keep the SDK
> tasks
> >>> alive. This is done by reimplementing the ets_run function, which is
> >>> executed each time before the idle task of the RIOT-OS and after the
> >>> timer interrupt handling.
> >>>
> >>> One of the two hardware timers is used in the SDK, the other hardware
> >>> timer is needed for PWM outputs. Therefore, RIOT OS timers are
> >>> implemented as SDK software timers, which results in an pure accuracy
> of
> >>> around 500 us.
> >>>
> >>> That's the status for now and I hope that it might become interesting
> >>> for someone. I will publish my changes at
> >>> https://github.com/gschorcht/RIOT-Xtensa-ESP8266 and submit a pull
> >>> request once I made some more progress.
> >>>
> >>> Regards
> >>> Gunar
> >>>
> >>>
> >>> ___
> >>> 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
> >
>
>
> --
> Dr. Gunar Schorcht
>
> Mission Level Design GmbH
> Langewiesener Strasse 22
> 98693 Ilmenau
>
> schor...@mldesigner.de
>
> Sitz der Gesellschaft:
> Lohmühlenweg 2
> 99310 Arnstadt
>
> Amtsgericht Jena: HRB 111384
> Geschäftsführung: Dipl.-Inf. Tino Jungebloud
>
>
> ___
> 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] Notification: Monthly RIOT developer meeting @ Mon Feb 26, 2018 5pm - 6pm (CET) (RIOT Events)

[Emmanuel Baccelli]

Hi Paco,

so the meeting is at 4PM (now) right?
What is the exact zoom.us meeting point?

Best,

Emmanuel

On Mon, Feb 26, 2018 at 11:03 AM, Martine Lenders 
wrote:

> Hi,
>
> when are we finally moving up the meeting to 16:00 CET? I'll need to leave
> again at 17:30.
>
> Best,
> Martine
>
> 2018-02-25 20:08 GMT+01:00 Francisco Acosta :
>
>> Hi devs!
>>
>> Just a gentle reminder for our next developers meeting which will take
>> place this Monday February 26th at 17:00 CET.
>>
>> Proposed agenda:
>>
>> - Next release goals
>> - Testing the RIOT
>>
>> As always, you're invited to propose topics you'd like to discuss. I'll
>> open a pad asap for the meeting notes and to list the topics.
>>
>> Thanks in advance for you attendance!
>>
>> Best,
>>
>> Francisco.
>>
>>
>>
>> On 25 February 2018 16:59:58 CET, Google Calendar <
>> calendar-notificat...@google.com> wrote:
>> >This is a notification for:
>> >
>> >Title: Monthly RIOT developer meeting
>> >When: Mon Feb 26, 2018 5pm – 6pm Berlin
>> >Where: Online
>> >Calendar: RIOT Events
>> >Who:
>> > * Martine Lenders - creator
>> >
>> >Event details:
>> >https://www.google.com/calendar/event?action=VIEW=NnFpM
>> Gh0a2RpajN0OWQ3bjhoa3VmdWdiMTFfMjAxODAyMjZUMTYwMDAwWiBrM3FsO
>> HNldHY3bDQ4b2Zub2wwdGZ1dTZ0c0Bn
>> >
>> >Invitation from Google Calendar: https://www.google.com/calendar/
>> >
>> >You are receiving this email at the account peterschme...@gmail.com
>> >because
>> >you are subscribed for notifications on calendar RIOT Events.
>> >
>> >To stop receiving these emails, please log in to
>> >https://www.google.com/calendar/ and change your notification settings
>> >for
>> >this calendar.
>> >
>> >Forwarding this invitation could allow any recipient to modify your
>> >RSVP
>> >response. Learn more at
>> >https://support.google.com/calendar/answer/37135#forwarding
>> ___
>> 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] [riot-maintainer] Release 2018.01

[Emmanuel Baccelli]

Indeed, thanks to Sebastian for managing this release, and congrats to all
involved parties!

On Thu, Feb 1, 2018 at 9:18 AM, Emmanuel Baccelli <
emmanuel.bacce...@gmail.com> wrote:

> Indeed, thanks to Sebastian for managing this release, and congrats to all
> involved parties!
>
> On Jan 31, 2018 23:55, "Cenk Gündoğan" <mail+r...@gundogan.net> wrote:
>
>> congratulations to everyone involved!
>>
>> ... and kudos to Sebastian for managing this release so elegantly (:
>>
>> Cheers,
>> Cenk
>>
>> On 18-01-31 17:26:03, Meiling, Sebastian wrote:
>> > Dear RIOTers,
>> >
>> > we are happy to announce the 14th official release of RIOT:
>> >
>> > --- * RIOT 2018.01 * ---
>> >
>> > The 2018.01 release includes major progress in RIOTs network
>> communication
>> > capabilities, i.e., rewrite of GNRC's neighbour discovery, confirmable
>> messages
>> > in (g)CoAP, LoRa, and GoMacH as well as updates on CCN-lite and LWIP.
>> > Furthermore, RIOT contributes to _IKEA-Hacking_ by bringing support for
>> > the smart home lighting system TRADFRI (note: this will void the
>> warranty).
>> > Needless to say that this release also adds and updates support for
>> several
>> > platforms, drivers, and of course lots of enhancements to the
>> documentation
>> > as well as numerous bug fixes. Last but not least, RIOT now has an
>> official
>> > code of conduct [0].
>> >
>> > More than 442 pull requests with about 865 commits have been merged
>> since the
>> > last release and about 96 issues have been solved. 54 people
>> contributed with
>> > code in 96 days. Approximately 2370 files have been touched with 223970
>> insertions
>> > and 181409 deletions.
>> >
>> > You can download the RIOT release from Github by cloning the repository
>> and
>> > checkout the release tag [1] or by downloading the tarball [2], and
>> look up
>> > the release notes for further details [3].
>> >
>> > And finally, many thanks to all of you contributing in so many
>> different ways
>> > to make RIOT worthwhile!
>> >
>> > Keep on RIOTing ... best,
>> >   Sebastian
>> >
>> > [0]: https://github.com/RIOT-OS/RIOT/blob/master/CODE_OF_CONDUCT.md
>> > [1]: https://github.com/RIOT-OS/RIOT/tree/2018.01
>> > [2]: https://github.com/RIOT-OS/RIOT/archive/2018.01.tar.gz
>> > [3]: https://github.com/RIOT-OS/RIOT/releases/tag/2018.01
>>
>>
>>
>> > ___
>> > devel mailing list
>> > devel@riot-os.org
>> > https://lists.riot-os.org/mailman/listinfo/devel
>>
>>
>> --
>> Cenk Gündoğan
>>
>> Hamburg University of Applied Sciences
>> Dept. of Computer Science / Internet Technologies Group
>> Berliner Tor 7, 20099 Hamburg, Germany
>> Fon: +49 40 42875 - 8426
>> Mail: cenk.guendo...@haw-hamburg.de
>> Web: https://www.inet.haw-hamburg.de/
>>
>> ___
>> Maintainer mailing list
>> maintai...@riot-os.org
>> https://lists.riot-os.org/mailman/listinfo/maintainer
>>
>>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] [riot-maintainer] Release 2018.01

[Emmanuel Baccelli]

Indeed, thanks to Sebastian for managing this release, and congrats to all
involved parties!

On Jan 31, 2018 23:55, "Cenk Gündoğan"  wrote:

> congratulations to everyone involved!
>
> ... and kudos to Sebastian for managing this release so elegantly (:
>
> Cheers,
> Cenk
>
> On 18-01-31 17:26:03, Meiling, Sebastian wrote:
> > Dear RIOTers,
> >
> > we are happy to announce the 14th official release of RIOT:
> >
> > --- * RIOT 2018.01 * ---
> >
> > The 2018.01 release includes major progress in RIOTs network
> communication
> > capabilities, i.e., rewrite of GNRC's neighbour discovery, confirmable
> messages
> > in (g)CoAP, LoRa, and GoMacH as well as updates on CCN-lite and LWIP.
> > Furthermore, RIOT contributes to _IKEA-Hacking_ by bringing support for
> > the smart home lighting system TRADFRI (note: this will void the
> warranty).
> > Needless to say that this release also adds and updates support for
> several
> > platforms, drivers, and of course lots of enhancements to the
> documentation
> > as well as numerous bug fixes. Last but not least, RIOT now has an
> official
> > code of conduct [0].
> >
> > More than 442 pull requests with about 865 commits have been merged
> since the
> > last release and about 96 issues have been solved. 54 people contributed
> with
> > code in 96 days. Approximately 2370 files have been touched with 223970
> insertions
> > and 181409 deletions.
> >
> > You can download the RIOT release from Github by cloning the repository
> and
> > checkout the release tag [1] or by downloading the tarball [2], and look
> up
> > the release notes for further details [3].
> >
> > And finally, many thanks to all of you contributing in so many different
> ways
> > to make RIOT worthwhile!
> >
> > Keep on RIOTing ... best,
> >   Sebastian
> >
> > [0]: https://github.com/RIOT-OS/RIOT/blob/master/CODE_OF_CONDUCT.md
> > [1]: https://github.com/RIOT-OS/RIOT/tree/2018.01
> > [2]: https://github.com/RIOT-OS/RIOT/archive/2018.01.tar.gz
> > [3]: https://github.com/RIOT-OS/RIOT/releases/tag/2018.01
>
>
>
> > ___
> > devel mailing list
> > devel@riot-os.org
> > https://lists.riot-os.org/mailman/listinfo/devel
>
>
> --
> Cenk Gündoğan
>
> Hamburg University of Applied Sciences
> Dept. of Computer Science / Internet Technologies Group
> Berliner Tor 7, 20099 Hamburg, Germany
> Fon: +49 40 42875 - 8426
> Mail: cenk.guendo...@haw-hamburg.de
> Web: https://www.inet.haw-hamburg.de/
>
> ___
> Maintainer mailing list
> maintai...@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/maintainer
>
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Whether RIOT can achieve wireless ICN communication

[Emmanuel Baccelli]

Hi there,

RIOT supports CCN-lite and NDN stacks, which are both offering ICN
capabilities over low-power wireless networks as demonstrated in [1][2][3]
among others.

For preliminary instructions/tutorial on how to use these stacks see [4]
[5].

The boards supported by RIOT are listed there [6]. Obviously, pick a board
that has a radio.
For starters you could use open access testbeds such as IoT-lab [7] [8].

Cheers,

Emmanuel

[1] https://arxiv.org/pdf/1406.6608.pdf
[2] https://named-data.net/wp-content/uploads/2017/03/ndn-
0043-2-ndn-riot.pdf
[3] https://pdfs.semanticscholar.org/768f/ead874324f3d1d5179ce42ad5b8c80
7710b8.pdf
[4] see task 8 in https://github.com/RIOT-OS/Tutorials
[5] https://github.com/named-data-iot/ndn-riot
[6] https://github.com/RIOT-OS/RIOT/tree/master/boards
[7] https://www.iot-lab.info
[8] https://www.researchgate.net/profile/Emmanuel_Baccelli/
publication/282667659_FIT_IoT-LAB_A_large_scale_open_
experimental_IoT_testbed/links/569d138608ae78356e563f23.pdf

On Tue, Dec 12, 2017 at 9:05 AM, 侯 宁博  wrote:

> Hi，I start to learn RIoT just now.
>
> I want to apply it in real environment. So I want to know whether RIOT can
> achieve wireless ICN communication.
>
> Besides,what hardware RIoT support? Do I need configure the
> hardware clock on my own when I develop programs, or just need write C
> program like in linux?
>
> Thanks a lot.
>
>
>
>
>
> 发送自 Windows 10 版邮件 应用
>
>
>
> ___
> 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] [riot-users] Release 2017.10

[Emmanuel Baccelli]

Yay!! Congrats to all involved parties and thanks Hauke for managing this
release.
Cheers!
Emmanuel

On Oct 27, 2017 12:38 PM, "Hauke Petersen" 
wrote:

> Dear RIOTers,
>
> we are happy to announce the 13th official release of RIOT:
>
> --- * RIOT 2017.10 * ---
>
> This release provides fixes, code cleanup and improved documentation,
> as well as enhancements.
>
> Most notable, this release is bringing RIOT a step closer to supporting
> over-the-air-updates by containing initial support for MCUBoot.
> Furthermore, it adds support for some new platforms (e.g. arduino-mkzero,
> nucleos, and frdm-k22f), drivers (e.g. my9221, apa102, ds1307), and of course
> a large number of bug fixes (e.g. `make buildtest` now working properly,
> various fixes to `xtimer`).
>
> About 230 pull requests with about 442 commits have been merged since
> the last release and about 13 issues have been solved. 45 people
> contributed with code in 56 days. 1395 files have been touched with
> 211720 insertions and 65729 deletions.
>
> You can download the RIOT release from Github by cloning the repository
> [1] or by downloading the tarball [2], and look up the release notes for
> further details [3].
>
> Again, a big thank you to all the people who helped getting this release
> on its way and who constantly work on making RIOT a better OS.
>
> Keep on RIOTing and cheers,
> Hauke
>
> [1] https://github.com/RIOT-OS/RIOT/releases/tag/2017.10
> [2] https://github.com/RIOT-OS/RIOT/archive/2017.10.tar.gz
> [3] https://github.com/RIOT-OS/RIOT/blob/2017.10-branch/release-notes.txt
>
>
> ___
> users mailing list
> us...@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/users
>
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Ahoi SANE

[Emmanuel Baccelli]

Hi Thomas,

thanks for letting us know! Is there any pointer/URL or preliminary
documentation that is available already concerning this project?

Cheers,

Emmanuel

On Wed, Oct 11, 2017 at 1:57 PM, Thomas C. Schmidt  wrote:

> Dear RIOTers,
>
> this is to announce SANE, a new project initiative and collaboration with
> the University of Hamburg - one of four flagship projects chosen to advance
> the digital strategy of the state of Hamburg.
>
> SANE - "Smart Networks for Urban Citizen Participation" will integrate and
> deploy smart private sensor based on RIOT in a distributed urban sensing
> system based on JADEX
> --
>
> Prof. Dr. Thomas C. Schmidt
> ° Hamburg University of Applied Sciences   Berliner Tor 7
>  °
> ° Dept. Informatik, Internet Technologies Group20099 Hamburg, Germany °
> ° http://www.haw-hamburg.de/inet   Fon: +49-40-42875-8452
> °
> ° http://www.informatik.haw-hamburg.de/~schmidtFax: +49-40-42875-8409
> °
> ___
> 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] Commercial products based of RIOT

[Emmanuel Baccelli]

Hi Samir,

for this, I suggest you take a look at the companies that have given a talk
at the last RIOT Summit. See:
http://summit.riot-os.org/2017/#speakers and
http://summit.riot-os.org/2017/blog/2017/10/06/slides/

Some examples of products and deployments using RIOT that I have seen
recently (available or announced) range from environmental sensors bundled
with cloud backend services [1] [2], to smart board diagnostic in the
automotive industry [3], and from IoT business logic orchestration [4] to
low-cost low-power communication modules [5].

There is certainly more out there (feel free to chip in with additional
info!).

Best,

Emmanuel

[1] https://hamiltoniot.com
[2]
http://riot-os.org/files/RIOT-Summit-2017-slides/6-2-Network-Session-DropWatcher.pdf
[3]
http://riot-os.org/files/RIOT-Summit-2017-slides/6-1-Network-Session-OTAkeys-CAN.pdf
[4]
http://riot-os.org/files/RIOT-Summit-2017-slides/4-3-Virtualization-Session-Fujitsu.pdf
[5] https://www.unwireddevices.com/products/


On Wed, Oct 11, 2017 at 10:05 AM, SKS  wrote:

> Dear All
>
>
> I am doing a literature survey on the commercial applicability of RIOT
> rtos.
> Can you please help me with some relevant pointers on Commercial products
> which are based of RIOT rtos ?
>
> Thanks and regards
> Samir
>
>
> ___
> 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] RIOT Summit 2017: slides & recap

[Emmanuel Baccelli]

Dear RIOTers,

The RIOT Summit 2017 was a success, with talks, break-sessions and lively
interactions for 2 days, with over 100 participants from Europe, North- and
South-America, as well as Asia.

The slides for the presentations of day 1 of the Summit are now available
online at http://riot-os.org/slides-summit-2017.html

A big thanks to the community and to all those who helped make this happen.

See you next year for the RIOT Summit 2018!

Cheers,

The organizers
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Help testing Kinetis dev boards

[Emmanuel Baccelli]

Hi Joakim,

FYI I just got hold of some kw41z boards.
gnrc_networking compiles on both OS X and Ubuntu (Vagrant).
Now I am trying to debug some trouble with jlink (can't flash the board
yet).

Cheers

Emmanuel

On Thu, Jun 8, 2017 at 1:09 PM, Emmanuel Baccelli <
emmanuel.bacce...@inria.fr> wrote:

> Hi Joakim
>
> just the other day, we ordered a couple frdm-kw41z at Inria, so we should
> be able to test here soon.
>
> Cheers,
>
> Emmanuel
>
> On Thu, Jun 8, 2017 at 11:32 AM, Joakim Nohlgård <
> joakim.nohlg...@eistec.se> wrote:
>
>> Dear developers,
>> Eistec have begun adding support for more Kinetis Freedom development
>> boards (frdm-k22f [1], frdm-kw41z [2]), to improve RIOT's hardware
>> coverage.
>>
>> I would be thankful if anyone with access to these boards would test it
>> and comment in the PRs with the results of their tests.
>>
>> I have opened a tracker issue [3] on GitHub for viewing the progress of
>> this effort.
>>
>> [1]: https://github.com/RIOT-OS/RIOT/pull/6994
>> [2]: https://github.com/RIOT-OS/RIOT/pull/6995
>> [3]: https://github.com/RIOT-OS/RIOT/issues/7154
>>
>> Best regards,
>> Joakim Nohlgård
>> Eistec AB
>>
>> ___
>> 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] Help testing Kinetis dev boards

[Emmanuel Baccelli]

Hi Joakim

just the other day, we ordered a couple frdm-kw41z at Inria, so we should
be able to test here soon.

Cheers,

Emmanuel

On Thu, Jun 8, 2017 at 11:32 AM, Joakim Nohlgård 
wrote:

> Dear developers,
> Eistec have begun adding support for more Kinetis Freedom development
> boards (frdm-k22f [1], frdm-kw41z [2]), to improve RIOT's hardware
> coverage.
>
> I would be thankful if anyone with access to these boards would test it
> and comment in the PRs with the results of their tests.
>
> I have opened a tracker issue [3] on GitHub for viewing the progress of
> this effort.
>
> [1]: https://github.com/RIOT-OS/RIOT/pull/6994
> [2]: https://github.com/RIOT-OS/RIOT/pull/6995
> [3]: https://github.com/RIOT-OS/RIOT/issues/7154
>
> Best regards,
> Joakim Nohlgård
> Eistec AB
>
> ___
> 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] [riot-maintainer] Release 2017.04

[Emmanuel Baccelli]

Yay! Thanks Kaspar for being the Release Manager this time around!
Best,
Emmanuel

On Wed, May 10, 2017 at 1:04 PM, Kaspar Schleiser 
wrote:

> Dear RIOTers,
>
> we are happy to announce the 11th official release of RIOT:
>
> --- * RIOT 2017.04 * ---
>
> This release provides a lot of new features, fixes and enhancements.
> Among these has been a huge cleanup regarding cppcheck and
> documentation, and we're pleased to announce that all remaining doxygen
> and cppcheck warnings have been fixed.
> We're also proud to present a Virtual File System layer and integration
> of the SPIFFS file system.
> A lot of work has gone into support for STMicroelectronics's Nucleo
> family, with RIOT now supporting 28 (up from 13) Nucleo boards. And as
> always, there was a lot of under-the-hood cleanup, bug fixing and
> documentation work.
>
> About 200 pull requests with about 562 commits have been merged since
> the last release and about 23 issues have been solved. 32 people
> contributed with code in 91 days. 2697 files have been touched with
> 716950 insertions and 492623 deletions.
>
> You can download the RIOT release from Github by cloning the repository
> [1] or by downloading the tarball [2], and look up the release notes for
> further details [3].
>
> Thanks everyone for your contributions, discussions, testing efforts,
> and keep RIOTing!
>
> Happy hacking,
> Kaspar
>
> [1] https://github.com/RIOT-OS/RIOT/releases/tag/2017.04
> [2] https://github.com/RIOT-OS/RIOT/archive/2017.04.tar.gz
> [3] https://github.com/RIOT-OS/RIOT/blob/2017.04-branch/release-notes.txt
> ___
> Maintainer mailing list
> maintai...@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/maintainer
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] RIOT Research Seminar: a short report

[Emmanuel Baccelli]

Hi Ken,
this is planned for the summer. We discussed with Thomas, and the rough
plan was to propose this topic for the IETF hackathon [1] in Prague this
summer, whereby some RIOTers and some OpenWSN people would attend and
hammer it out. Until then, OpenWSN Fresh is getting ready AFAIK.

[1] https://www.ietf.org/hackathon/99-hackathon.html

On Sat, Apr 29, 2017 at 3:22 PM, Ken Bannister <kb...@runbox.com> wrote:

> Emmanuel, Thomas:
>
> Thanks for the links! I was very interested to see Thomas's slides on
> OpenWSN "fresh" [1]. It would be valuable to have a 6TiSCH implementation
> in RIOT. Are there any more details available on this project?
>
> Thanks,
> Ken
>
> http://riot-os.org/files/RIOT-Seminar-2017/RIOT-Spring-
> Seminar-Watteyne.pdf
>
> On 04/28/2017 06:26 AM, Emmanuel Baccelli wrote:
>
> Hi everyone,
>
> there was a seminar organized earlier this month in Paris. The goal of
> that seminar was to gather various research teams working (or considering
> to work) around RIOT at Inria.
>
> The agenda + slides are available at http://riot-os.org/seminar-2017.html
>
> Some synopsis/highlights below:
>
> - Securing IoT is important now. (see slides from C. Bormann)
> - Formally verified open source IoT software is desirable and some is
> already available today (see slides from K. Bhargavan)
> - Public key crypto is the hardest part of IoT crypto, but significant
> performance improvements are on the horizon (see slides from B. Smith)
> - Industrial IoT deployments are already happening. (see slides from T.
> Watteyne)
> - Object security, and content-centric networking can be used for
> security. (see slides from M. Enguehard)
> - Need public experimental infrastructure & open data for IoT. (see slides
> from E. Fleury)
> - Large open source project need tools/languages to (i) flexibly express
> how code should be and (ii) automate code transformation (see slides from
> J. Lawall)
> - OS adaptation and programming abstractions are needed for intermittently
> powered IoT devices, and peripherals restoration is the hard part (see
> slides from G. Salagnac)
> - IoT software components and component dynamic updates are desirable.
> (see slides from J. Bourcier)
>
> If you have comments or questions, just ask here and/or contact the
> authors directly!
>
> Cheers
>
> Emmanuel
>
>
>
> ___
> devel mailing 
> listdevel@riot-os.orghttps://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

[riot-devel] RIOT Research Seminar: a short report

[Emmanuel Baccelli]

Hi everyone,

there was a seminar organized earlier this month in Paris. The goal of that
seminar was to gather various research teams working (or considering to
work) around RIOT at Inria.

The agenda + slides are available at http://riot-os.org/seminar-2017.html

Some synopsis/highlights below:

- Securing IoT is important now. (see slides from C. Bormann)
- Formally verified open source IoT software is desirable and some is
already available today (see slides from K. Bhargavan)
- Public key crypto is the hardest part of IoT crypto, but significant
performance improvements are on the horizon (see slides from B. Smith)
- Industrial IoT deployments are already happening. (see slides from T.
Watteyne)
- Object security, and content-centric networking can be used for security.
(see slides from M. Enguehard)
- Need public experimental infrastructure & open data for IoT. (see slides
from E. Fleury)
- Large open source project need tools/languages to (i) flexibly express
how code should be and (ii) automate code transformation (see slides from
J. Lawall)
- OS adaptation and programming abstractions are needed for intermittently
powered IoT devices, and peripherals restoration is the hard part (see
slides from G. Salagnac)
- IoT software components and component dynamic updates are desirable. (see
slides from J. Bourcier)

If you have comments or questions, just ask here and/or contact the authors
directly!

Cheers

Emmanuel
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] IoT Software Update IETF mailing list

[Emmanuel Baccelli]

Hi everyone,

those concerned with software updates in RIOT should probably consider
registering to this new mailing list to follow and/or participate in
related discussions: https://www.ietf.org/mailman/listinfo/fud

Cheers,

Emmanuel
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] waspmote + xbee + shell

[Emmanuel Baccelli]

Hi François,

you could first try the below, assuming you have some other board with
802.15.4 lying around (e.g. a SAMR21):
- use gnrc_minimal on your waspmote
- compile/flash/term the gnrc_networking example on the other board
- ping6 on the board running the gnrc_networking example to check that
connectivity is there.

Once you are this works, you could try to use a slightly modified
gnrc_minimal example adding an automatic call to ping on one waspmote the
address of the other waspmote (I suppose you could do that
with _icmpv6_ping which is what the ping6 shell command).

(Note: The shell takes some memory, so on the waspmote where the memory is
very tight, it is not a perspective to activate it together with the
network stack).

My 2c.

Cheers,

Emmanuel



On Tue, Apr 11, 2017 at 11:09 AM, François Despaux <
francois.desp...@loria.fr> wrote:

> Hi everybody,
>
> I'm writing to you because I'm having some problems when trying to test
> the xbee module.
>
> What I want to do is to be able to comunicate two waspmotes by means of
> the xbee module.
> I took a look at the driver_xbee test in order to have something to start
> from. However, when running ifconfig for this example, the ip address I
> obtain is as follows:
>
> Iface 4 HWaddr: 00:00
> Long HWaddr: 00:00:00:00:00:00:00:00
>
>
> I tried to add the gnrc_ipv6 to the Makefile but when doing this, shell is
> no longer available.
>
> I moved then to the gnr_minimal example and after setting up the Makefile
> for considering the Xbee module, I'm able to display the mote's ip address.
> Nevertheless, I'm not able to run the shell within this example.
>
> Do you have any idea how can I set up un example in which both ipv6 and
> shell modules are available (and thus to be able to get the waspmote
> ipaddress and to be able to send messages from the shell (txtsend)) ??
>
> Thanks,
>
> François
>
> ___
> 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] RIOT Summit?

[Emmanuel Baccelli]

Hi Ken,

yes there is. It is planned in September, in Berlin.

The dates are not 100% set in stone, but very probably it will be Sept.
29th and 30th, in conjunction with ACM ICN conference [1].

We will announce it soon.

Would you be able to come by? Would be great.

Cheers,

Emmanuel

[1] http://conferences.sigcomm.org/acm-icn/2017/

On Thu, Mar 2, 2017 at 5:00 PM, Ken Bannister  wrote:

> Is there any thought ongoing toward a second RIOT Summit this year?
>
> Thanks,
> Ken
> ___
> 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] about RIOT-os porting

[Emmanuel Baccelli]

Hi Chen,

RIOT targets primarily low-end IoT devices, e.g. see devices defined in RFC
7228 [1].

At first sight, it seems to me your hardware is rather high-end in
comparison: what are the RAM/ROM specs? What architecture? If it can run
Linux, why don't you want to use Linux?

This does not mean that RIOT cannot run on your hardware, but high-end IoT
devices are not (our) priority at the moment.
However, you are invited to look at the porting guide [2] to get an initial
idea of the steps towards RIOT running on your hardware.

Best,

Emmanuel

[1] https://tools.ietf.org/html/rfc7228
[2] https://github.com/RIOT-OS/RIOT/wiki/Porting-Guide

On Sun, Feb 5, 2017 at 10:46 AM, che...@rock-chips.com <
che...@rock-chips.com> wrote:

> Dear sir,
> I come from a Chinese company named Rockchip.(http://www.rock-
> chips.com/a/en/index.html)
> There is a dsp of CEVA-xm4 in our 1608-chip,and now, we want to
> porting the RIOT-os to this dsp.
> Can you support us? and tell us what we need to do?
> At the same time,We can provide you with the appropriate hardware, related
> document of the dsp.and so on.
> Looking forward to your reply.
> Thanks & Best regards
>
> ***
> Chen Shiqin
>
> Fuzhou Rockchip Electronics Co.Ltd
>
> Addr : No. 21 Building, A District, No.89,software Boulevard
> Fuzhou,Fujian,PRC
>
> Tel   : 15280423908
> ***
>
> ___
> 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] [RFC 6719] MRHOF - Objective Function for RPL

[Emmanuel Baccelli]

Hi Rafał

On Thu, Jan 5, 2017 at 2:15 PM, Rafał Rzatkiewicz <
rafal.rzatkiew...@gmail.com> wrote:

>
>
> https://github.com/RIOT-OS/RIOT/issues/2493
>
> Of course this checklist is related to the previous implementation of RIOT
> OS and long before the gnrc network stack which is included in recent
> releases.
>
>
Yes, this list of issues is outdated.



> However, it sounds to me like there are couple issues which are not
> trivial in terms of MRHOF, ETX-metric and DAG Metrc Container
> implementation within RIOT OS.
>
>
Can you elaborate on why you have this impression, more in details?

Best,

Emmanuel
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] wolfSSL port to RIOT OS

[Emmanuel Baccelli]

Hi Larry, Hi Kaleb

great! I did not see any pull-request yet to RIOT's master branch? Can we
expect one soonish?

Cheers

Emmanuel

On Fri, Dec 9, 2016 at 1:41 AM, la...@wolfssl.com <la...@wolfssl.com> wrote:

> Kaleb,
>
> Can you write up a blog post to let our community know that this is
> available?
>
> Please include the details you shared below.
>
> Finally, include the caveat that we did not enable Fastmath, unless you
> fixed that.
>
> Emmanuel,
>
> Can you share the announcement with your community?
>
> Thanks!
>
> LS
>
> > On Dec 8, 2016, at 8:39 AM, kaleb himes <ka...@wolfssl.com> wrote:
> >
> > Hi Emmanuel,
> >
> > I am building on Mac OS X initially. Everything is working great. I have
> three examples that build and run with RIOT_OS. A benchmark application, a
> cryptographic test application and a TLS client/server + cryptographic test
> application. These three example applications demonstrate running on the
>  only for now.
> >
> > Next steps will to be building on Linux, and building for one of the
> embedded platforms that RIOT supports. The only real change required on Mac
> OS X was to include  instead of  when
> building with RIOT_OS.
> >
> >
> > Warm Regards,
> >
> > Kaleb Himes
> > Software Engineer
> > www.wolfssl.com
> >
> >> On Dec 8, 2016, at 09:13, Emmanuel Baccelli <emmanuel.bacce...@inria.fr>
> wrote:
> >>
> >> Hi Larry,
> >>
> >> great! looking forward to your PR.
> >> What hardware are you testing this on initially?
> >>
> >> Cheers
> >>
> >> Emmanuel
> >>
> >> On Thu, Dec 1, 2016 at 1:17 AM, la...@wolfssl.com <la...@wolfssl.com>
> wrote:
> >> Our initial build pretty much just works!  Our next step is to look at
> a few warnings we’re kicking out.
> >>
> >> LS
> >>
> >> > On Nov 30, 2016, at 3:35 PM, Matthias Waehlisch <
> m.waehli...@fu-berlin.de> wrote:
> >> >
> >> > Hi Kaleb,
> >> >
> >> >
> >> >  +1 -- in particular, if you plan to continue the maintenance of the
> >> > port!
> >> >
> >> >
> >> >
> >> > Cheers
> >> >  matthias
> >> >
> >> >
> >> > On Wed, 30 Nov 2016, Thomas Eichinger wrote:
> >> >
> >> >>
> >> >> Hi Kaleb,
> >> >>
> >> >> Personally I would be very much stoked to see a port of wolfSSL to
> RIOT and I think many others think
> >> >> the same.
> >> >>
> >> >> Let us know how we can help with it and I'm sure we will figure
> something out!
> >> >>
> >> >> Best, Thomas
> >> >>
> >> >> On 30 Nov 2016, at 13:09 PST(-0800), kaleb himes wrote:
> >> >>
> >> >>  Hi @RIOT_OS developers,
> >> >> @wolfSSL is considering doing a port to the Revolutionary Internet
> of Things Operating System. We
> >> >> wanted to reach out to the RIOT_OS developers group to see if this
> is something that interests
> >> >> you.
> >> >>
> >> >> Please let us know your thoughts, we look forward to hearing from
> you!
> >> >>
> >> >> i...@wolfssl.com
> >> >> supp...@wolfssl.com
> >> >>
> >> >> Regards,
> >> >>
> >> >> Kaleb and the wolfSSL Team
> >> >>
> >> >> ___
> >> >> devel mailing list
> >> >> devel@riot-os.org
> >> >> https://lists.riot-os.org/mailman/listinfo/devel
> >> >>
> >> >>
> >> >>
> >> >
> >> >
> >> > --
> >> > Matthias Waehlisch
> >> > .  Freie Universitaet Berlin, Computer Science
> >> > .. http://www.cs.fu-berlin.de/~waehl
> >> >
> >>
> >> Larry Stefonic
> >> Founder and CEO
> >> www.wolfssl.com
> >> Skype:  Stefonic
> >> http://twitter.com/wolfSSL
> >> +1 206 369 4800
> >>
> >> ___
> >> 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
> >
>
> Larry Stefonic
> Founder and CEO
> www.wolfssl.com
> Skype:  Stefonic
> http://twitter.com/wolfSSL
> +1 206 369 4800
>
> ___
> 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] SiLabs Gecko

[Emmanuel Baccelli]

Hi Akshay
It seems that SiLabs uses the terms of a zlib license [1] for its code (see
[2]).
If this is correct indeed, zlib is recognized by FSF and compatible with
LGPL, so no issues there, I guess.
Cheers
Emmanuel


[1] https://en.wikipedia.org/wiki/Zlib_License
[2]
https://siliconlabs.github.io/Gecko_SDK_Doc/ezr32lg/html/ezradio__comm_8c.html


On Thu, Dec 8, 2016 at 10:56 AM, Hauke Petersen  wrote:

> Hi again,
>
> On 08.12.2016 10:49, Akshay Mishra wrote:
>
> I have located the track. Now the license question --
>
> Is it ok to use bits of code from the Silicon Labs driver here (
> https://siliconlabs.github.io/Gecko_SDK_Doc/ezr32lg/html/ez
> radio__comm_8c_source.html) as per RIOT-OS licensing norms ?
>
> In general yes, but it depends which license SiLabs has put on the code,
> so as long as it is compatible to LGPL you could use it. But if that is the
> most elegant solution is something of personal taste... :-)
>
> Cheers,
> Hauke
>
>
>
>
> On 8 December 2016 at 14:58, Akshay Mishra  wrote:
>
>> Thanks Martine,
>> It is possible that there is no RF support (I thought so but was not
>> sure.). I can look at porting it if there can be pointers.
>>
>> The example used was gnrc_networking on the latest git clone.
>>
>> One confession, :-|, is that the EZR32WG is supported and I worked on the
>> basic examples only modifying the WG to LG which changes it from Cortex-M4
>> to Cortex-M3.
>>
>> *Akshay Mishra*
>>
>> On 8 December 2016 at 14:31, Martine Lenders < 
>> m...@martine-lenders.eu> wrote:
>>
>>> Hi Akshay,
>>> I fear you have to be a bit more specific than that. What application
>>> are you using e.g., which network stack? Also, I might be mistaking
>>> but it seems like there is no RF support for the EZR32LG in master
>>> yet. Maybe that is the problem?
>>>
>>> Cheers,
>>> Martine
>>>
>>> 2016-12-08 8:34 GMT+01:00 Akshay Mishra :
>>> > Hello,
>>> > I tried it on the SLWSTK6220a with the EZR32LG. While I was
>>> able to
>>> > get riot-os working on it, the ipv6 address does not get assigned.
>>> >
>>> > How does the interface get enabled ? I did not enable any tap on the
>>> host.
>>> >
>>> > Thanks,
>>> > Akshay
>>> >
>>> >
>>> > ___
>>> > 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 
> listdevel@riot-os.orghttps://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] wolfSSL port to RIOT OS

[Emmanuel Baccelli]

+1 here! This would be a great addition to RIOT.
Cheers,
Emmanuel

On Dec 1, 2016 12:38 AM, "Matthias Waehlisch" 
wrote:

> Hi Kaleb,
>
>
>   +1 -- in particular, if you plan to continue the maintenance of the
> port!
>
>
>
> Cheers
>   matthias
>
>
> On Wed, 30 Nov 2016, Thomas Eichinger wrote:
>
> >
> > Hi Kaleb,
> >
> > Personally I would be very much stoked to see a port of wolfSSL to RIOT
> and I think many others think
> > the same.
> >
> > Let us know how we can help with it and I'm sure we will figure
> something out!
> >
> > Best, Thomas
> >
> > On 30 Nov 2016, at 13:09 PST(-0800), kaleb himes wrote:
> >
> >   Hi @RIOT_OS developers,
> > @wolfSSL is considering doing a port to the Revolutionary Internet of
> Things Operating System. We
> > wanted to reach out to the RIOT_OS developers group to see if this is
> something that interests
> > you.
> >
> > Please let us know your thoughts, we look forward to hearing from you!
> >
> > i...@wolfssl.com
> > supp...@wolfssl.com
> >
> > Regards,
> >
> > Kaleb and the wolfSSL Team
> >
> > ___
> > devel mailing list
> > devel@riot-os.org
> > https://lists.riot-os.org/mailman/listinfo/devel
> >
> >
> >
>
>
> --
> Matthias Waehlisch
> .  Freie Universitaet Berlin, Computer Science
> .. http://www.cs.fu-berlin.de/~waehl
> ___
> 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] RIOT Release 2016.10

[Emmanuel Baccelli]

Yay! Thanks a bunch Martine for taking on the role of manager for this
release.
Congrats to everyone for all the work!
Emmanuel

On Fri, Nov 11, 2016 at 4:21 PM, Kaspar Schleiser 
wrote:

> Hey,
>
> congratulations to everyone and thanks for all the hard work!
>
> On 11/11/2016 04:07 PM, Martine Lenders wrote:
> > nanocoap
>
> As the release notes are not clear on this:
>
> Nanocoap not only provides CoAP header parsing/building and is used for
> that as backend for gcoap. It also provides easy to use server and
> client functionality.
>
> 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

Re: [riot-devel] IoTivity pkg for RIOT

[Emmanuel Baccelli]

Hi Mattia,

I would say: make the PR and we will feedback then. Two comments at first
sight, though:

- to remain clean, Apache licensed files should not be PRed directly to be
located in the RIOT/example/
Instead, can't you pull them (+ whatever you need) along with your pkg?

- the files you wrote should be licensed such as for instance see header of
[1] just replace your name and affiliation.

Best,

Emmanuel

[1] https://github.com/RIOT-OS/RIOT/blob/master/examples/
gnrc_networking/main.c


On Fri, Nov 4, 2016 at 3:28 PM, MATTIA ANTONINI  wrote:

> Dear all,
> I have created a Pkg that allows to use IoTivity on RIOT easily. It is
> based on IoTivity-constrained[1]. This version of IoTivity is designed for
> constrained nodes and it contains also the glue code for RIOT. The pkg can
> be included like other pkgs (e.g. microcoap, etc).
>
> It is available here[2].
>
> In particular under:
> - /pkg/iotivity : there are makefiles of the pkg
> - /examples/iotivity-examples : there are some working examples (with a
> brief tutorial)
>
> Any feedback will be appreciated.
>
> Cheers,
> Mattia Antonini
>
> p.s. before to submit the PR, I have to understand if there are or not
> some issue from the licensing point of view.
>
> [1] https://github.com/iotivity/iotivity-constrained
> [2] https://github.com/mattiantonini/RIOT/tree/pkg/iotivity
>
> ___
> 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] LoRaWAN implementation under RIOT

[Emmanuel Baccelli]

Hello again Cr0s,

Great. I was asking this because some RIOTers in Chile are about to start
to port LoRaWAN to RIOT, hence your SX1276 driver would be great for them,
I guess.

Looking forward to your PR!

One last question: are you using your SX1276 on a STM32L1 of some sort?

Cheers

Emmanuel

On Wed, Oct 26, 2016 at 5:34 PM, Anon Anonymous 
wrote:

> Good day to all RIOT folks.
>
> Thank you guys for interesting that topic! And thanks to Akshay for the
> donation proposal, but I, personally, has a plenty of sx1276-based modules
> done by my company and they're work well so far.
>
> I finished my sx1276 driver and need about a week to port it onto newest
> version of RIOT due to some API changes and to fix some possible issues
> with that. On LoRaWAN support, it's planned in near future and will be
> implemented soon or later, of course, but if somebody needs a point to
> start with - just wait for my driver's PR and use it to implement LoRaWAN
> above it.
>
> To summarize:
> 1. SX1276 support is done and used in production as well, so the PR in
> RIOT it's just a matter of time. Hopefully I will do this until the end of
> a week.
> 2. LoRaWAN layer isn't done by me personally, but if somebody is willing
> to start on this direction, my SX1276 driver that will be published soon is
> good starting point
>
> 2016-06-20 16:20 GMT+03:00 Anon Anonymous :
>
>> Hi, RIOTers!
>>
>> After a couple of months I've finished a Semtech's SX1276 LoRa
>> transceiver driver (physical level, RX and TX) under RIOT (pull request
>> coming soon!) and the next step is a LoRaWAN MAC level implementation.
>>
>> My question is:
>> Which RIOT interfaces should I choose to implement next to introduce
>> LoRaWAN MAC level as seamlessly as possible into existing RIOT's networking
>> stacks?
>>
>> Thanks in advance for any help and clarifications!
>>
>> Best regards.
>>
>
>
> ___
> 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] LoRaWAN implementation under RIOT

[Emmanuel Baccelli]

Hi there,

Any news on this?
Is there a branch available somewhere?

Best,

Emmanuel

On Mon, Jun 20, 2016 at 3:20 PM, Anon Anonymous 
wrote:

> Hi, RIOTers!
>
> After a couple of months I've finished a Semtech's SX1276 LoRa transceiver
> driver (physical level, RX and TX) under RIOT (pull request coming soon!)
> and the next step is a LoRaWAN MAC level implementation.
>
> My question is:
> Which RIOT interfaces should I choose to implement next to introduce
> LoRaWAN MAC level as seamlessly as possible into existing RIOT's networking
> stacks?
>
> Thanks in advance for any help and clarifications!
>
> Best regards.
>
> ___
> 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

[Emmanuel Baccelli]

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 <kas...@schleiser.de>
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] Next from Arduino

[Emmanuel Baccelli]

Hi everyone,

I just stumbled across this.

Seems Arduino is going for easier hardware modularity and cloudification.

https://techcrunch.com/2016/09/29/arduino-unleashes-a-serious-internet-of-things-system-for-hardware-hackers/

Emmanuel
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] RIOT Core Development Project

[Emmanuel Baccelli]

Hi Srivignessh,

improving x86 support in RIOT is a not such a bad idea, in my opinion.
If you are interested in this however, instead of the Galileo board, I
would suggest working on support for Arduino 101 [1].
The first step would be to provide initial support i.e. to have the bare
minimum for the RIOT shell to work, which means have context switching,
timer, UART.

FYI, there is support for x86 through the QEMU support [2] but this is
likely outdated and would have to be overhauled to be harmonized somewhat
with current ARM, AVR, and MSP430 support.

@Kijewski care to comment on that latest statement?

Cheers

Emmanuel

[1] https://www.arduino.cc/en/Main/ArduinoBoard101
[2] https://github.com/RIOT-OS/RIOT/tree/master/cpu/x86

On Wed, Sep 21, 2016 at 5:44 AM, Pss Srivignessh 
wrote:

> Sir,
>
> I am Srivignessh Pss, MS CE Arizona State University.
> I am looking for a development project of RIOT for my Advanced Operating
> Systems course.
>
> Can you suggest me few domains to work. I found currently it is not
> supported on Intel Galileo Board. Is it a good area to start with
>
> Thank you
> Srivignessh Pss
> ASU
>
> ___
> 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] C.H.I.P

[Emmanuel Baccelli]

Hi Arash,
at first sight Linux can run on C.H.I.P.
So why not use Linux?
RIOT targets devices which cannot run Linux (or derivatives/equivalents).
Hence: there are no plans to support CHIP
best,
Emmanuel

On Wed, Jul 20, 2016 at 10:29 AM, Arash Shafiei  wrote:

> Hi, I was wondering if there is any plan to support C.H.I.P ?
>
> https://getchip.com/pages/chip
>
>
>
> ___
> 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] Skimpy make-do streaming of RIoT summit plenary

[Emmanuel Baccelli]

Hi everyone,
some more slides sorted per session are available at
https://www.dropbox.com/sh/wdz2nwzxzarqzq6/AABVgMer9yZYzXDqCD9p2bKLa?dl=0
Best,
Emmanuel

On Fri, Jul 15, 2016 at 10:55 AM, Joakim Nohlgård <joakim.nohlg...@eistec.se
> wrote:

> Thank you!
> /Joakim
>
> On Fri, Jul 15, 2016 at 10:44 AM, Oleg Hahm <oliver.h...@inria.fr> wrote:
>
>> +1
>>
>> On Fri, Jul 15, 2016 at 09:35:06AM +0200, Emmanuel Baccelli wrote:
>> > Thanks Carsten!
>> >
>> > On Jul 15, 2016 9:30 AM, "Carsten Bormann" <c...@tzi.org> wrote:
>> >
>> > >
>> > > https://hangouts.google.com/hangouts/_/bomthsflordmhfhplund2imm64e
>> > >
>> > > You cannot see the slides there; copies of the slides are slowly
>> > > gathering at http://www.tzi.de/~cabo/riot-summit/
>> > >
>> > > If you join the hangout, please send feedback to #riot=os
>> > > (irc.freenode.net).
>> > >
>> > > Grüße, Carsten
>> > > ___
>> > > 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
>>
>>
>> --
>> I'd make a joke about UDP, but I don't know if anyone's actually
>> listening...
>>
>> ___
>> 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] Skimpy make-do streaming of RIoT summit plenary

[Emmanuel Baccelli]

Thanks Carsten!

On Jul 15, 2016 9:30 AM, "Carsten Bormann"  wrote:

>
> https://hangouts.google.com/hangouts/_/bomthsflordmhfhplund2imm64e
>
> You cannot see the slides there; copies of the slides are slowly
> gathering at http://www.tzi.de/~cabo/riot-summit/
>
> If you join the hangout, please send feedback to #riot=os
> (irc.freenode.net).
>
> Grüße, Carsten
> ___
> 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] Web and IoT discussion

[Emmanuel Baccelli]

Hi again,
for the CoAP session on Saturday, there may be a remote participation
organized based on Google Hangouts or some other WebRTC scheme.  Stay
tuned... Carsten will make the announcement will be on #riot-os
Cheers
Emmanuel

On Thu, Jul 14, 2016 at 7:47 PM, Emmanuel Baccelli <
emmanuel.bacce...@inria.fr> wrote:

> Hi Ken
> Let me enquire. It would be great if you could participate indeed.
> Cheers
> Emmanuel
>
> On Jul 14, 2016 7:12 PM, "Ken Bannister" <kb...@runbox.com> wrote:
>
>> I read that Ari Keränen and Carsten Bormann plan to lead a discussion on
>> Saturday at the RIOT Summit on the Web and IoT, including better support
>> for CoAP in RIOT. I am the author of a work-in-progress CoAP implementation
>> [1].
>>
>> I am very interested in this discussion; however, I am unable to attend
>> in person. Is there any plan for remote access or streaming? If not, I
>> would appreciate a summary of the discussion.
>>
>> Thanks,
>> Ken
>>
>> [1] https://github.com/RIOT-OS/RIOT/pull/5598
>> ___
>> 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] Web and IoT discussion

[Emmanuel Baccelli]

Hi Carsten,
Great. Thanks,
Emmanuel

On Thu, Jul 14, 2016 at 10:47 PM, Carsten Bormann <c...@tzi.org> wrote:

> Emmanuel Baccelli wrote:
> > The CoAP discussion is going to be a break-out session on Saturday, with
> > a relatively small number of participants, so remote participation would
> > be easier to organize.
>
> We will try to get something going for the T2TRG/RIOT session, probably
> based on Google Hangouts or some other WebRTC scheme.  Stay tuned...
> Announcement will be on #riot-os.
>
> Grüße, Carsten
> ___
> 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] Web and IoT discussion

[Emmanuel Baccelli]

Hi Joakim,

unfortunately, there is no such plan concerning the whole event...

The CoAP discussion is going to be a break-out session on Saturday, with a
relatively small number of participants, so remote participation would be
easier to organize.

Best,

Emmanuel

On Thu, Jul 14, 2016 at 10:08 PM, Joakim Nohlgård  wrote:

> I would also like to hear the presentations, but I will not be able to
> attend. Will the presentations be recorded and available online after the
> event?
>
> Best regards,
> Joakim
>
> Den 14 jul 2016 19:13 skrev "Ken Bannister" :
>
>> I read that Ari Keränen and Carsten Bormann plan to lead a discussion on
>> Saturday at the RIOT Summit on the Web and IoT, including better support
>> for CoAP in RIOT. I am the author of a work-in-progress CoAP implementation
>> [1].
>>
>> I am very interested in this discussion; however, I am unable to attend
>> in person. Is there any plan for remote access or streaming? If not, I
>> would appreciate a summary of the discussion.
>>
>> Thanks,
>> Ken
>>
>> [1] https://github.com/RIOT-OS/RIOT/pull/5598
>> ___
>> 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] Web and IoT discussion

[Emmanuel Baccelli]

Hi Ken
Let me enquire. It would be great if you could participate indeed.
Cheers
Emmanuel

On Jul 14, 2016 7:12 PM, "Ken Bannister"  wrote:

> I read that Ari Keränen and Carsten Bormann plan to lead a discussion on
> Saturday at the RIOT Summit on the Web and IoT, including better support
> for CoAP in RIOT. I am the author of a work-in-progress CoAP implementation
> [1].
>
> I am very interested in this discussion; however, I am unable to attend in
> person. Is there any plan for remote access or streaming? If not, I would
> appreciate a summary of the discussion.
>
> Thanks,
> Ken
>
> [1] https://github.com/RIOT-OS/RIOT/pull/5598
> ___
> 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] RIOT, Windows, and Code Composer Studio

[Emmanuel Baccelli]

Caeveat: coma at the end url may mess up your automatic URL detection
thingie:
https://github.com/RIOT-OS/RIOT/wiki/Using-the-Eclipse-IDE-for-C-and-CPP-Developers,-
Howto
On Jun 20, 2016 4:49 PM, "Emmanuel Baccelli" <emmanuel.bacce...@inria.fr>
wrote:

> Hi there
>
> I don't know how complete and up to date that is but there is also:
>
> https://github.com/RIOT-OS/RIOT/wiki/Using-the-Eclipse-IDE-for-C-and-CPP-Developers,-
> Howto
>
> Cheers
> Emmanuel
> On Jun 20, 2016 4:39 PM, "Francisco Javier Acosta Padilla" <
> francisco.aco...@inria.fr> wrote:
>
>> Hi Clark!
>>
>> I’m not using CCS but Eclipse, although I use it only for editing code,
>> it is possible to use it for compiling, flashing and debugging (in
>> experimental phase).
>>
>> As for today, we don’t have a very complete guide on how to do it in
>> RIOT, but there is a guide[1] for Contiki, which can be extended to RIOT.
>> The guide assumes the use of GCC for compiling…
>>
>> Anyone knows if we can support other compilers? IMO it’s a matter of
>> changing the prefixes of the compiler in the Makefile, but maybe some flags
>> can differ...
>>
>> I hope it helps.
>>
>> Cheers,
>>
>>
>> [1] https://github.com/Zolertia/Resources/wiki/Eclipse
>>
>>
>> --
>> Francisco Javier Acosta Padilla
>> Research Engineer at INRIA Saclay
>> INFINE Team
>>
>> On 20 June 2016 at 16:22:03, Ludwig Knüpfer (ludwig.knuep...@fu-berlin.de)
>> wrote:
>>
>> Hi Clark,
>>
>> I am not aware of anyone using CCS.
>> In my perception most of us are Linux based and don't even use Eclipse.
>>
>> Cheers,
>> Ludwig
>>
>> Am 20. Juni 2016 15:59:29 MESZ, schrieb Clark Leach <
>> clark.le...@gmail.com>:
>> >Nothing? Really?
>> >
>> >On Tue, Jun 14, 2016 at 2:43 PM, Clark Leach <clark.le...@gmail.com>
>> >wrote:
>> >
>> >> I am intersted in developing with RIOT for a few different TI targets
>> >and
>> >> have Code Composer Studio installed on Windoze 8.1 which I have used
>> >for
>> >> several projects. Since CCS already has all the tool chains and
>> >debugger
>> >> interfaces, it seems like it would make sense to use it for these
>> >projects
>> >> as well.
>> >>
>> >> Is there any hope of making such a configuration work? Is there any
>> >> guidance available? I have read the howto on using Eclipse and found
>> >the
>> >> information lacking and, at times, incomprehensible (what is a
>> >"speaking
>> >> Variable Name", anyways).
>> >>
>> >> Any feedback would be appreciated.
>> >>
>> >>
>> >
>> >
>> >
>> >
>> >___
>> >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] RIOT, Windows, and Code Composer Studio

[Emmanuel Baccelli]

Hi there

I don't know how complete and up to date that is but there is also:
https://github.com/RIOT-OS/RIOT/wiki/Using-the-Eclipse-IDE-for-C-and-CPP-Developers,-
Howto

Cheers
Emmanuel
On Jun 20, 2016 4:39 PM, "Francisco Javier Acosta Padilla" <
francisco.aco...@inria.fr> wrote:

> Hi Clark!
>
> I’m not using CCS but Eclipse, although I use it only for editing code, it
> is possible to use it for compiling, flashing and debugging (in
> experimental phase).
>
> As for today, we don’t have a very complete guide on how to do it in RIOT,
> but there is a guide[1] for Contiki, which can be extended to RIOT. The
> guide assumes the use of GCC for compiling…
>
> Anyone knows if we can support other compilers? IMO it’s a matter of
> changing the prefixes of the compiler in the Makefile, but maybe some flags
> can differ...
>
> I hope it helps.
>
> Cheers,
>
>
> [1] https://github.com/Zolertia/Resources/wiki/Eclipse
>
>
> --
> Francisco Javier Acosta Padilla
> Research Engineer at INRIA Saclay
> INFINE Team
>
> On 20 June 2016 at 16:22:03, Ludwig Knüpfer (ludwig.knuep...@fu-berlin.de)
> wrote:
>
> Hi Clark,
>
> I am not aware of anyone using CCS.
> In my perception most of us are Linux based and don't even use Eclipse.
>
> Cheers,
> Ludwig
>
> Am 20. Juni 2016 15:59:29 MESZ, schrieb Clark Leach  >:
> >Nothing? Really?
> >
> >On Tue, Jun 14, 2016 at 2:43 PM, Clark Leach 
> >wrote:
> >
> >> I am intersted in developing with RIOT for a few different TI targets
> >and
> >> have Code Composer Studio installed on Windoze 8.1 which I have used
> >for
> >> several projects. Since CCS already has all the tool chains and
> >debugger
> >> interfaces, it seems like it would make sense to use it for these
> >projects
> >> as well.
> >>
> >> Is there any hope of making such a configuration work? Is there any
> >> guidance available? I have read the howto on using Eclipse and found
> >the
> >> information lacking and, at times, incomprehensible (what is a
> >"speaking
> >> Variable Name", anyways).
> >>
> >> Any feedback would be appreciated.
> >>
> >>
> >
> >
> >
> >
> >___
> >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] RIOT Vs Iotivity, AllJoyn, Thread

[Emmanuel Baccelli]

Hi Ivan,
it would be great to have it as a pkg indeed!
That's the standard way third-party stacks are integrated in RIOT.
Looking forward to that,
Emmanuel

On Wed, Jun 8, 2016 at 3:41 PM, Iván Briano <ivan.bri...@intel.com> wrote:

> On Wed, 08 Jun 2016 09:46:31 +0200, Baptiste Clenet wrote:
> > Thanks for your answers.
> > Could we integrate Soletta OIC implementation part as a pkg in RIOT?
> >
>
> The OIC implementation is tightly integrated to the core of Soletta, so
> you need the whole thing in. I'll look into making sure the pkg and
> build are in good condition and send it as a pull request.
>
> > 2016-06-07 12:58 GMT+02:00 Emmanuel Baccelli <emmanuel.bacce...@inria.fr
> >:
> >
> > > Hi Gustavo, Hi Ivan,
> > > ok I see. thanks for your answers.
> > > That's too bad. It would have been great to gather OIC/OCF people in
> the
> > > same room with W3C, IETF and OpenThread people (who are attending the
> RIOT
> > > Summit) to discuss various IoT network stack approaches, and various
> IoT
> > > open source software approaches. Pitching Intel's approach to IoT in
> this
> > > context would also have been a good occasion, in the opinion of many
> among
> > > us.
> > > If there's anything we can do to help you or someone else from your
> > > community attend/present, let us know.
> > > Else, maybe next time.
> > > Cheers,
> > > Emmanuel
> > >
> > > On Mon, Jun 6, 2016 at 11:26 PM, Gustavo Lima Chaves <
> > > gustavo.lima.cha...@intel.com> wrote:
> > >
> > >> Hi,
> > >>
> > >> > Sorry, I was under the assumption that this had been settled in
> private
> > >> > conversations already, but now I see that's not the case (and the
> person
> > >> > involved is not even copied).
> > >> >
> > >> > Soletta has an implementation of OIC, the protocol that IoTivity
> > >> > implements, but there's nothing about AllJoyn or Thread.
> > >> >
> > >> > I'm in no position to talk about anything now, so I have to decline
> the
> > >> > invitation, but maybe some of the others listed that have been more
> > >> > involved with Soletta and OIC can respond.
> > >> >
> > >> > On Mon, 06 Jun 2016 22:40:34 +0200, Baptiste Clenet wrote:
> > >> > > Could some of you answer please?
> > >> > > Thanks
> > >> > >
> > >> > > Baptiste
> > >> > >
> > >> > > 2016-05-31 17:30 GMT+02:00 Thiago Macieira <
> thiago.macie...@intel.com
> > >> >:
> > >> > >
> > >> > > > Hello Baptiste, Emmanuel
> > >> > > >
> > >> > > > I'll let the people more familiar (in cc) with it reply.
> > >> > > >
> > >> > > > On terça-feira, 31 de maio de 2016 16:05:22 BRT Emmanuel
> Baccelli
> > >> wrote:
> > >> > > > > Hi Thiago,
> > >> > > > > basically, we are interested in learning more about it.
> > >> > > > > And in particular, we were wondering whether it could be a
> good
> > >> idea to
> > >> > > > > present this at the RIOT Summit [1].
> > >> > > > > What do you think about this idea?
> > >> > > > > Best,
> > >> > > > > Emmanuel
> > >>
> > >> Oh, sorry, I was also in the private thread (was going to respond
> > >> soon, but now let's do it here). I have to say that I'm not very
> > >> comfortable to do a skype-based presentation. Given that the changes
> > >> of getting funds to travel to the summit are vague now, maybe I'll
> > >> have to decline as well, unfortunately.
> > >>
> > >> [...]
> > >>
> > >> > > > > >>>> Hi!
> > >> > > > > >>>>
> > >> > > > > >>>> On Mon, May 30, 2016 at 09:16:17AM +0200, Baptiste Clenet
> > >> wrote:
> > >> > > > > >>>> > - Iotivity would be great in RIOT, Soletta project [1]
> > >> imported it
> > >> > > > > >>>> > for
> > >> > > > > >>>> > RIOT, I haven't tried it but it seems to work. I think
> > >> Riot should
> > >> > > > > >>>>
> > >> > > > > >>>> have an
> > >> > > > > >>>>
> > >> > > > > >>>> > implementation of Iotivity directly in its repo
> (package)
> > >> so it
> > >> > > > will
> > >> > > > > >>>>
> > >> > > > > >>>> be
> > >> > > > > >>>>
> > >> > > > > >>>> > better maintain.
> > >>
> > >> If all of OIC/OCF is to be supported, that's quite a bit of code and
> > >> using Soletta is a much simpler path.
> > >>
> > >> --
> > >> Gustavo Lima Chaves
> > >> Intel - Open Source Technology Center
> > >>
> > >
> > >
> >
> >
> > --
> > Baptiste
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] RIOT Vs Iotivity, AllJoyn, Thread

[Emmanuel Baccelli]

Hi Gustavo, Hi Ivan,
ok I see. thanks for your answers.
That's too bad. It would have been great to gather OIC/OCF people in the
same room with W3C, IETF and OpenThread people (who are attending the RIOT
Summit) to discuss various IoT network stack approaches, and various IoT
open source software approaches. Pitching Intel's approach to IoT in this
context would also have been a good occasion, in the opinion of many among
us.
If there's anything we can do to help you or someone else from your
community attend/present, let us know.
Else, maybe next time.
Cheers,
Emmanuel

On Mon, Jun 6, 2016 at 11:26 PM, Gustavo Lima Chaves <
gustavo.lima.cha...@intel.com> wrote:

> Hi,
>
> > Sorry, I was under the assumption that this had been settled in private
> > conversations already, but now I see that's not the case (and the person
> > involved is not even copied).
> >
> > Soletta has an implementation of OIC, the protocol that IoTivity
> > implements, but there's nothing about AllJoyn or Thread.
> >
> > I'm in no position to talk about anything now, so I have to decline the
> > invitation, but maybe some of the others listed that have been more
> > involved with Soletta and OIC can respond.
> >
> > On Mon, 06 Jun 2016 22:40:34 +0200, Baptiste Clenet wrote:
> > > Could some of you answer please?
> > > Thanks
> > >
> > > Baptiste
> > >
> > > 2016-05-31 17:30 GMT+02:00 Thiago Macieira <thiago.macie...@intel.com
> >:
> > >
> > > > Hello Baptiste, Emmanuel
> > > >
> > > > I'll let the people more familiar (in cc) with it reply.
> > > >
> > > > On terça-feira, 31 de maio de 2016 16:05:22 BRT Emmanuel Baccelli
> wrote:
> > > > > Hi Thiago,
> > > > > basically, we are interested in learning more about it.
> > > > > And in particular, we were wondering whether it could be a good
> idea to
> > > > > present this at the RIOT Summit [1].
> > > > > What do you think about this idea?
> > > > > Best,
> > > > > Emmanuel
>
> Oh, sorry, I was also in the private thread (was going to respond
> soon, but now let's do it here). I have to say that I'm not very
> comfortable to do a skype-based presentation. Given that the changes
> of getting funds to travel to the summit are vague now, maybe I'll
> have to decline as well, unfortunately.
>
> [...]
>
> > > > > >>>> Hi!
> > > > > >>>>
> > > > > >>>> On Mon, May 30, 2016 at 09:16:17AM +0200, Baptiste Clenet
> wrote:
> > > > > >>>> > - Iotivity would be great in RIOT, Soletta project [1]
> imported it
> > > > > >>>> > for
> > > > > >>>> > RIOT, I haven't tried it but it seems to work. I think Riot
> should
> > > > > >>>>
> > > > > >>>> have an
> > > > > >>>>
> > > > > >>>> > implementation of Iotivity directly in its repo (package)
> so it
> > > > will
> > > > > >>>>
> > > > > >>>> be
> > > > > >>>>
> > > > > >>>> > better maintain.
>
> If all of OIC/OCF is to be supported, that's quite a bit of code and
> using Soletta is a much simpler path.
>
> --
> Gustavo Lima Chaves
> Intel - Open Source Technology Center
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] RIOT Vs Iotivity, AllJoyn, Thread

[Emmanuel Baccelli]

Hi Thiago,
basically, we are interested in learning more about it.
And in particular, we were wondering whether it could be a good idea to
present this at the RIOT Summit [1].
What do you think about this idea?
Best,
Emmanuel


[1] summit.riot-os.org

On Tue, May 31, 2016 at 3:52 PM, Baptiste Clenet <bapcle...@gmail.com>
wrote:

> Not really but I saw him answering some post on Iotivity and Soletta
> project for people asking to port Iotivity to constraint object.
>
> Thiago, could you explain Soletta Project and the relation with OIC and
> RIOT please?
>
> 2016-05-30 21:07 GMT+02:00 Emmanuel Baccelli <emmanuel.bacce...@inria.fr>:
>
>> Hi Baptiste,
>>
>> Thanks for the clarification.
>>
>> Have you already been in contact personally with Thiago?
>>
>> It may be interesting if they attend and/or present something on this
>> topic at the upcoming RIOT Summit [1].
>>
>> Cheers,
>>
>> Emmanuel
>>
>> [1] summit.riot-os.org
>> On May 30, 2016 4:19 PM, "Baptiste Clenet" <bapcle...@gmail.com> wrote:
>>
>>> Hi, I correct what I said, Soletta Project is not an implementation of
>>> Iotivity but an implementation of OIC specification (Iotivity too) so
>>> Iotivity and Soletta project can communicate together since they use same
>>> specification.
>>>
>>> Intel Open Source is in charge of this project and you can ask
>>> thiago.macie...@intel.com for more information.
>>>
>>> Cheers,
>>>
>>> 2016-05-30 10:41 GMT+02:00 Oleg Hahm <oliver.h...@inria.fr>:
>>>
>>>> Hi!
>>>>
>>>> On Mon, May 30, 2016 at 09:16:17AM +0200, Baptiste Clenet wrote:
>>>> > - Iotivity would be great in RIOT, Soletta project [1] imported it for
>>>> > RIOT, I haven't tried it but it seems to work. I think Riot should
>>>> have an
>>>> > implementation of Iotivity directly in its repo (package) so it will
>>>> be
>>>> > better maintain.
>>>>
>>>> Very interesting and good to know. I was not aware of this project (and
>>>> I
>>>> think most of the RIOT maintainers weren't either). And yes, for
>>>> maintainability a package in RIOT might make sense. We just need a
>>>> maintainer
>>>> willing to do so. ;-)
>>>>
>>>> Baptiste, do you know the people behind Soletta?
>>>>
>>>> Cheers,
>>>> Oleg
>>>>
>>>> --
>>>> printk("Entering UltraSMPenguin Mode...\n");
>>>> linux-2.2.16/arch/sparc64/kernel/smp.c
>>>>
>>>> ___
>>>> devel mailing list
>>>> devel@riot-os.org
>>>> https://lists.riot-os.org/mailman/listinfo/devel
>>>>
>>>>
>>>
>>>
>>> --
>>> Baptiste
>>>
>>> ___
>>> 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
>>
>>
>
>
> --
> Baptiste
>
> ___
> 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] Unifying the interfaces of the digest functions

[Emmanuel Baccelli]

On Wed, May 11, 2016 at 12:26 PM, Oleg Hahm  wrote:

> Hi Matthias!
>
> On Wed, May 11, 2016 at 12:12:42PM +0200, Mathias Tausig wrote:
> > The interafces used by the cryptographic digest functions sha256, sha1
> and md5
> > (xx_init, xx_update, xx_final) are very inconsistent at the moment.
> > Would a patch which would consolidate this situation be desirable?
>
> Anything that makes the API more consistent is desirable! Please go ahead!
>
> +1



> Cheers,
> Oleg
> --
> if(ct<0)
> ct=2;/* Shit happens.. */
> linux-2.6.6/drivers/net/wan/z85230.c
>
> ___
> 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] PowerProfiler

[Emmanuel Baccelli]

Hi Michael,
thanks for the proposal. It seems there is interest. When are you back
approximately?
I'm asking because some of us are working on a deadline (beginning of May)
for which energy measurements might be very welcome ;)
cheers,
Emmanuel

On Thu, Apr 21, 2016 at 4:16 PM, Michael Andersen <mich...@steelcode.com>
wrote:

> I would be more than happy to start it up again and maintain it if it
> would be of use to the community. I'll do so as soon as I finish my
> post-IPSN Vienna tour :)
> On Apr 21, 2016 3:46 PM, "Emmanuel Baccelli" <emmanuel.bacce...@inria.fr>
> wrote:
>
>> Great, and overlooked indeed.
>> Is this setup still up and running?
>> Cheers,
>> Emmanuel
>>
>> On Thu, Apr 21, 2016 at 3:43 PM, Oleg Hahm <oliver.h...@inria.fr> wrote:
>>
>>> Dear really-low-power IOTlers,
>>>
>>> reading through https://github.com/RIOT-OS/RIOT/pull/2309 I stumbled
>>> across
>>> Michael Andersen's PowerProfiler [1] and was literally shocked that such
>>> a
>>> nice tool/setup has been gone unnoticed for so long. At least I was not
>>> aware
>>> of this setup and checking with some other people on IM, it seems that
>>> I'm not
>>> alone.
>>>
>>> This looks like a really cool and promising solution to get an
>>> understanding
>>> of the power consumption for RIOT applications. Great work, Michael!
>>>
>>> Cheers,
>>> Oleg
>>>
>>> [1] https://github.com/PowerProfiler/TestApplications
>>> --
>>> panic("Yeee, unsupported cache architecture.");
>>> linux-2.6.6/arch/mips/mm/cache.c
>>>
>>> ___
>>> 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] IoT technology survey

[Emmanuel Baccelli]

Hi Michael,
Yes, the results are somewhat puzzling.
Maybe the people who answered the survey were probably of the
"rasberryPi=IoT" type, which might explain some results.
With this in mind, there is probably something to get out of the results.
Best,
Emmanuel

On Fri, Apr 15, 2016 at 2:43 PM, Michael Frey <f...@informatik.hu-berlin.de>
wrote:

> Hi,
>
> Am Di, 15.03.2016, 11:15, schrieb Emmanuel Baccelli:
>
> > https://www.surveymonkey.com/r/AGILEIoT
>
> so, here are (if I see this correctly) are the results
>
>
> https://ianskerrett.wordpress.com/2016/04/14/profile-of-an-iot-developer-results-of-the-iot-developer-survey/
>
> I'm a bit puzzled about the 11.2 % considering php an IoT programming
> language (and apparently using it) - on the other hand there are 73 % who
> consider Linux an IoT operating system. Anyway, maybe it's worthwhile for
> somebody to read it during hers/his lunch break.
>
> Best,
>  Michael
> --
> Dipl.-Inf. (FH), M. Sc. Michael Frey
> Humboldt-Universität zu Berlin
> Department of Computer Science
> Rudower Chaussee 25
> 12489 Berlin, Germany
>
> ___
> 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] [riot-users] Certificates on RIOT pages

[Emmanuel Baccelli]

Thanks Oleg! Now we're super legit ;)

On Fri, Mar 18, 2016 at 4:16 PM, Oleg Hahm  wrote:

> Dear requesting IOTlers,
>
> good things come to those who wait: we finally got our letsencrypt [1]
> sponsored certificates for the self-hosted RIOT related pages.
> For https://lists.riot-os.org you should get the following fingerprints:
>
> SHA256
> Fingerprint=4B:90:0F:E4:A8:2A:CE:29:F5:11:17:32:20:63:86:CF:4A:FD:07:7F:84:F6:79:06:9D:AB:24:06:86:81:2D:C8
> MD5 Fingerprint=E2:02:35:D4:92:7F:9A:77:DC:EE:83:AA:23:0B:52:7B
>
> For https://riot-os.org or https://summit.riot-os.org you should get:
>
> SHA256
> Fingerprint=CB:B8:E0:CC:48:4A:D5:54:77:E9:A9:DA:78:58:6B:8C:66:46:66:A8:6C:7A:49:6B:43:F7:88:92:50:A4:3D:E9
> MD5 Fingerprint=E3:8A:41:F5:88:B6:3F:A2:05:5A:DC:59:F1:62:27:23
>
> Cheers,
> Oleg
>
> [1] https://letsencrypt.org/
> --
> DPRINTK("FAILURE, CAPUT\n");
> linux-2.6.6/drivers/net/tokenring/ibmtr.c
>
> ___
> users mailing list
> us...@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/users
>
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] IoT technology survey

[Emmanuel Baccelli]

Hi everyone,

our friends from Eclipse Foundation are conducting a survey about IoT
technologies currently in use or aimed at in various contexts. Maybe you
can consider filling it in (and maybe the results will be of some interest).

https://www.surveymonkey.com/r/AGILEIoT

Best,

Emmanuel
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] RIOT: Production ready?

[Emmanuel Baccelli]

Hi Baptiste,

I think you need to specify for what type of use/product.
Else it's difficult to judge...
I mean: if RIOT is supposed to "make coffee and donuts out of the box",
it's maybe not production ready.
For some other types of use, it may be production-ready.

Cheers,

Emmanuel


On Wed, Mar 9, 2016 at 4:19 PM, Baptiste Clenet  wrote:

> Let's say that the production-ready RIOT could be announced for the
> next release (when network bugs will be solved) for 6LoWPAN-CoAP +
> SAUL stack.
>
> Thanks for your answer Martine.
>
> 2016-03-09 15:12 GMT+01:00 Martine Lenders :
> > Hi,
> >
> > apart from a few known bugs (and required API changes in the lower to
> > mid-high levels) in the network stack we still have, I would give the
> > (optimistic) answer that RIOT is production-ready. However, this
> > evaluation only refers to a 6LoWPAN-CoAP + SAUL stack, as the full
> > stack demos we run a few weeks ago were quite successful to my
> > knowledge. Other popular features like e.g. MQTT(-SN) are still in
> > development or not even touched upon currently. This is however my
> > personal opinion and maybe does not reflect the opinion of the
> > majority of the community. Also, some user-level APIs for CoAP (in the
> > spirit of "I want to run a CoAP server on this port which publishes
> > these actuators/sensors" in less then 10 lines) might be something
> > that a client wants to see.
> >
> > Cheers,
> > Martine
> >
> > 2016-03-09 15:02 GMT+01:00 Baptiste Clenet :
> >> Hi,
> >>
> >> Do you think that RIOT is production-ready? What is still missing
> >> according to you to run RIOT on an IOT device in production?
> >>
> >> Cheers,
> >>
> >> --
> >> Baptiste
> >> ___
> >> 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
>
>
>
> --
> Baptiste
> ___
> 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] GSOC inquiry.

[Emmanuel Baccelli]

Hi Om
RIOT is not participating in GSOC this year.
Best,
Emmanuel

On Tue, Mar 8, 2016 at 4:20 PM, Om Shivom Nagpal 
wrote:

> Hi, I am Om Shivom pursuing CSE from PEC University of Technology,
> Chandigarh and I have previously worked on C++ and Python. I am interested
> in contributing to RIOT through GSOC 2016. I need a little guidance on how
> to get started here.
>
> Regards.
>
> ___
> 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] Port to STM32F7

[Emmanuel Baccelli]

Oops, did not remember that one. Thanks Hauke!
Emmanuel
On Mar 4, 2016 08:49, "Hauke Petersen" <hauke.peter...@fu-berlin.de> wrote:

> Hi,
>
> this is not quite true, I have started to work on this some time ago [1],
> but don't quite remember were I left of. But maybe this branch might give
> you a head start? Feel free to copy what you need!
>
> Cheers,
> Hauke
>
> [1] https://github.com/haukepetersen/RIOT/tree/add_board_stm32f7discovery
>
> On 03.03.2016 18:31, Emmanuel Baccelli wrote:
>
> Hi Antoine,
>
> As far as I know, no one has started porting to this board, or to any
> other Cortex M7-based board yet.
>
> However, it would be great to have support for this Discovery board (and
> initial M7 support).
>
> Are you interested/willing to start porting?
>
> The community usually turns out to be supportive of that type of efforts
> in various ways via exchanges on GitHub or discussions on this list or
> private exchanges spun out from such discussions.
>
> Cheers
>
> Emmanuel
> On Mar 3, 2016 17:52, "Antoine Faure" <antoine.faure.1...@gmail.com>
> wrote:
>
>> Hi everyone,
>>
>> I am interested in using RTOS with an STM32F746NG Discovery (a board with
>> an ARM Cortex M7), but it doesn't seem to be supported yet. Does anyone
>> know if someone started working on this ?
>>
>> Here is a link to the board I'm talking about :
>>
>> http://www.st.com/web/en/catalog/tools/FM116/SC959/SS1532/LN1848/PF261641?sc=stm32f7-discovery
>>
>> Thanks,
>> Antoine.
>> ___
>> devel mailing list
>> devel@riot-os.org
>> https://lists.riot-os.org/mailman/listinfo/devel
>>
>
>
> ___
> devel mailing 
> listdevel@riot-os.orghttps://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] Port to STM32F7

[Emmanuel Baccelli]

Hi Antoine,

As far as I know, no one has started porting to this board, or to any other
Cortex M7-based board yet.

However, it would be great to have support for this Discovery board (and
initial M7 support).

Are you interested/willing to start porting?

The community usually turns out to be supportive of that type of efforts in
various ways via exchanges on GitHub or discussions on this list or private
exchanges spun out from such discussions.

Cheers

Emmanuel
On Mar 3, 2016 17:52, "Antoine Faure"  wrote:

> Hi everyone,
>
> I am interested in using RTOS with an STM32F746NG Discovery (a board with
> an ARM Cortex M7), but it doesn't seem to be supported yet. Does anyone
> know if someone started working on this ?
>
> Here is a link to the board I'm talking about :
>
> http://www.st.com/web/en/catalog/tools/FM116/SC959/SS1532/LN1848/PF261641?sc=stm32f7-discovery
>
> Thanks,
> Antoine.
> ___
> 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] Sample applications

[Emmanuel Baccelli]

Hi there,
I think it would be great to have a RIOT tutorial space somewhere. Two
comments:
- Cenk also had some input on that at
https://github.com/cgundogan/RIOT-Tutorial
- maybe some stuff from Alex (e.g. his upcoming Bluetooth+802.15.4 border
router) could belong into applications or even examples?
Cheers
Emmanuel


On Tue, Mar 1, 2016 at 10:35 PM, Ludwig Knüpfer <
ludwig.knuep...@fu-berlin.de> wrote:

> Hi,
>
> Based on a quick scan this looks very good indeed and think we should
> incorporate it into the RIOT project space. Not sure where exactly though.
>
> Cheers,
> Ludwig
>
> Am 1. März 2016 11:48:19 MEZ, schrieb Alexandre Abadie <
> alexandre.aba...@inria.fr>:
> >Dear Rioters,
> >
> >I started to use riot-os a few weeks ago now and I'd like to tell you
> >that your project is totally awesome and quite well documented.
> >
> >I first began to write some sample applications with in mind the idea
> >of providing some easy to use/understand starter tutorials showing the
> >possibilities offered by riot-os (UART, GPIO, NET, etc). I tried to
> >have the examples as much documented as possible (but we all know that
> >this can always be improved).
> >The code is already available on GitHub [1]. By the way I noticed that
> >you already have a repo targeting the same idea [2].
> >
> >What do you think of merging both or maybe create another repository
> >called "riot-tutorials" where "aabadie/riot-apps" could be moved ? Are
> >you interested in such a contribution ?
> >
> >Cheers,
> >
> >Alex
> >
> >[1] https://github.com/aabadie/riot-apps
> >[2] https://github.com/RIOT-OS/applications
> >___
> >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] Happy 10k!

[Emmanuel Baccelli]

Fantastic! Let's keep rocking!

On Mon, Feb 22, 2016 at 6:33 AM, Ludwig Knüpfer <
ludwig.knuep...@fu-berlin.de> wrote:

> Hoorah!
>
> BTW:
> what's the current SLoC count?
>
> Cheers,
> Ludwig
>
> Am 22. Februar 2016 00:56:13 MEZ, schrieb Kaspar Schleiser <
> kas...@schleiser.de>:
> >Hey fellow RIOTers,
> >
> >we've passed 1 commits...
> >
> >Congratulations to everyone!
> >
> >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
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Newcomer to the community

[Emmanuel Baccelli]

Hi Satyaki,
thanks for your interest. Please have a look at
https://github.com/RIOT-OS/RIOT/wiki/GSOC16
Thanks,
Emmanuel

On Tue, Feb 16, 2016 at 9:41 AM, Satyaki Upadhyay 
wrote:

> Hi
>
>
> My name is Satyaki and I'm a newcomer to the RIOT community. I want to
> contribute to this project. I have been an active participator in
> programming contests like ACM-ICPC and on online judges over the last two
> years (am comfortable in C++).
> Codeforces -http://codeforces.com/profile/satyaki3794
> Topcoder -   https://www.topcoder.com/members/satyaki3794/
> SPOJ - http://www.spoj.com/users/satyaki3794/
>
>
> I am new to open source development and want to get involved using Google
> Summer of Code. Can someone please give me some pointers as to how I can
> get started?
>
>
> Regards
> Satyaki
> ᐧ
> ᐧ
>
> ___
> 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] Contribution to RIOT OS as GSOC 2016 student

[Emmanuel Baccelli]

Hi there,
thanks for your interest! Please have a look at
https://github.com/RIOT-OS/RIOT/wiki/GSOC16
Thanks,
Emmanuel

On Tue, Feb 16, 2016 at 8:01 AM, Aditya Manglik 
wrote:

> Hello developers
> I would like to contribute to RIOT OS as a Google Summer of Code
> participant for the current year(2016). I am currently an undergraduate in
> an engineering college(BITS Pilani) in India, majoring in Electronics and
> Computer Science. I have some experience working with micro controllers and
> embedded systems, with a fairly good knowledge of C/C++ programming. I am
> highly motivated and excited to learn any new skills or programming
> languages required as part of this contribution. Please tell me the
> required milestones that should be completed before the student application
> period opens. Any helpful pointers in the right direction would be a good
> start.
> Thanks!
> 
> 
>
> ___
> 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] Contiki as a RIOT thread

[Emmanuel Baccelli]

Hey there,
+1 for the idea on my side too.
cheers
Emmanuel

On Tue, Jan 19, 2016 at 12:45 PM, Kaspar Schleiser 
wrote:

> Hey,
>
> On 01/19/2016 11:58 AM, Joakim Nohlgård wrote:
>
>> I would like to hear any ideas and opinions on this list on how to
>> effectively implement this.
>>
>
> I really like the possiblity and always bragged that this way it is
> possble, but running RIOT as thread within Contiki is not (in any way that
> makes sense).
>
> 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

Re: [riot-devel] RIOT Release 2015.12

[Emmanuel Baccelli]

Yay!

On Sun, Jan 10, 2016 at 4:28 PM, Cenk Gündogan 
wrote:

> Dear RIOT developers and users,
>
> I am glad to announce the sixth official release of the RIOT operating
> system:
>
> --- * RIOT 2015.12 *
> ---
>
> This release is packed with nearly 150 enhancements to the codebase and
> bugfixes
> for several known issues. It also contains a lot of new documentation as
> well as
> improvements to existing ones, which can be found in
> http://doc.riot-os.org/.
>
> In addition to the above, this new release re-enables the support for ICN
> by integrating CCN-lite as a package and provides example applications
> to showcase its functionality.
>
> Developers can now make use of a Vagrant file that ships with
> this release in order to manage a RIOT supported guest machine.
> This reduces the set-up time by delivering a system with all
> necessary toolchains installed without the need to touch the host system.
>
> With a partial support of the Arduino API, RIOT becomes more accessible
> to a wide range of Arduino specialized developers. Although this new
> feature is
> still rudimentary, it already enables simple Arduino sketches to be
> compiled
> into RIOT.
>
> A further highlight of this release is the introduction of SAUL,
> the [S]ensor [A]ctuator [U]ber [L]ayer. SAUL enables a portable approach
> to interact with different types of sensors and actuators on RIOT supported
> hardware by offering a unified API to the developer.
>
> Several new platforms and device drivers found their way into this release.
> RIOT 2015.12 supports the WeIO board, the Silicon Labs Wireless Eval Kit
> (SLWSTK6220A) and the STM32 Nucleo-F401. With the new device driver for the
> enc28j60 ethernet chip it is now possible to use wired connections with
> RIOT.
>
> Since the last release about 222 new pull requests with about 631 commits
> were merged and 48 additional issues have been solved. 37 people generated
> a total of ~59779 insertions and ~12115 deletions in 980 files.
>
> You can download the RIOT release from Github by cloning the repositoryor
> by
> downloading the tarball:
> https://github.com/RIOT-OS/RIOT/archive/2015.12.tar.gz
>
> Keep RIOTing!
>
> - Cenk
> ___
> 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] Wind in our sails?

[Emmanuel Baccelli]

Hi everyone,

here's what some people say looking back at 2015 [1].

If what is stated there is true, it may be one more hint we're on good
tracks at all levels, even license-wise?

Cheers,

Emmanuel

[1] http://www.zdnet.com/article/linux-and-open-source-have-won-get-over-it/
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] Low-power WAN

[Emmanuel Baccelli]

Hi everyone,

while so far most of us here are interested in shorter range radios (as far
as I know), there is this recent push towards low-power long-range
technologies of various types. I stumbled over this blunt, high-level
survey [1] of the current state of affairs in that domain, I thought it
might be relevant to share here.

One question: is anyone working with some such wireless technology with
RIOT, or planning to in the near future?

cheers,

Emmanuel

[1] http://www.eejournal.com/archives/articles/20150907-lpwa/
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Task Forces

[Emmanuel Baccelli]

Hi again,

OK, I modified the page, here's how it would look like:
https://github.com/RIOT-OS/RIOT/wiki/Task-Forces
Comments/input welcome.

Talking about task forces, was there not a LPM task force on the way too?

Best,

Emmanuel


On Thu, Nov 19, 2015 at 4:59 PM, Kaspar Schleiser <kas...@schleiser.de>
wrote:

> Hey,
>
> On 11/19/15 16:50, Emmanuel Baccelli wrote:
> > - would Kaspar agree he was the shepherd of the timers task force?
>
> yes.
>
> 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

Re: [riot-devel] Task Forces

[Emmanuel Baccelli]

OK, I could go ahead and modify the wiki with some tentative text for that,
which we could refine later on.
In practice:

- would Kaspar agree he was the shepherd of the timers task force?

- would Martine & Hauke agree they were the shepherds of the nasty task
force?

- would Martine & Hauke agree they are the shepherds of the documentation
task force?

- who would take on the shepherding for the OTA task force? If no-one
speaks up, we could classify this TF as dormant the time being.



On Thu, Nov 19, 2015 at 4:04 PM, Oleg Hahm <oliver.h...@inria.fr> wrote:

> Hi!
>
> Sounds like a sensible proposal to me.
>
> Cheers,
> Oleg
>
> Am Thu, Nov 19, 2015 at 03:51:36PM +0100 schrieb Emmanuel Baccelli:
> > +1 here too.
> > I think it is also important to describe to malloc and free :)
> > I mean how to:
> >
> > 1 - create a new task force (hopefully we have a lot more to come!)
> > 2 - join/ping/revive an existing task force (e.g. OTA is somewhat
> dormant)
> > 3 - dissolve an existing task force
> >
> > For creating: how about, simply stating something like:
> > "If you wish to launch a new task force, go ahead, create your wikipage,
> > and report your progress or summarize the latest stand of your
> discussions
> > on devel@riot-os.org"
> > There's the slight possibility that duplicate work may happen down the
> > line, if a lot of task forces are active at the same time.
> > But this is not dangerous right now. If we want to cover this case, maybe
> > we can add: "RIOT maintainers will contact you if duplicate or very
> > closely-related work has been detected elsewhere, and if joining forces
> > might make sense."
> >
> > For ping/join/revive how about naming one or two shepherds per task
> force,
> > that could be pinged?
> >
> > For dissolving: how about "either (i) the shepherd(s) declares the TF is
> > done, or gives up, or (ii) the shepherds are unreachable, the TF has been
> > dormant for a long time and RIOT maintainers declare the TF dissolved"
> >
> >
> >
> >
> > On Thu, Nov 19, 2015 at 3:34 PM, Kaspar Schleiser <kas...@schleiser.de>
> > wrote:
> >
> > > Hey,
> > > On 11/19/15 14:48, Oleg Hahm wrote:
> > > > As an effort to "formalize" this idea of task forces a little bit
> more,
> > > I just
> > > > created a small page in the Wiki:
> > > >
> > > > What do you think?
> > >
> > > +1
> > >
> > > I've updated the xtimer page.
> > >
> > > 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
>
>
> --
> /* Thanks to Rob `CmdrTaco' Malda for not influencing this code in any
>  * way.
>  */
> linux-2.4.3/net/core/netfilter.c
>
> ___
> 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] Task Forces

[Emmanuel Baccelli]

+1 here too.
I think it is also important to describe to malloc and free :)
I mean how to:

1 - create a new task force (hopefully we have a lot more to come!)
2 - join/ping/revive an existing task force (e.g. OTA is somewhat dormant)
3 - dissolve an existing task force

For creating: how about, simply stating something like:
"If you wish to launch a new task force, go ahead, create your wikipage,
and report your progress or summarize the latest stand of your discussions
on devel@riot-os.org"
There's the slight possibility that duplicate work may happen down the
line, if a lot of task forces are active at the same time.
But this is not dangerous right now. If we want to cover this case, maybe
we can add: "RIOT maintainers will contact you if duplicate or very
closely-related work has been detected elsewhere, and if joining forces
might make sense."

For ping/join/revive how about naming one or two shepherds per task force,
that could be pinged?

For dissolving: how about "either (i) the shepherd(s) declares the TF is
done, or gives up, or (ii) the shepherds are unreachable, the TF has been
dormant for a long time and RIOT maintainers declare the TF dissolved"




On Thu, Nov 19, 2015 at 3:34 PM, Kaspar Schleiser 
wrote:

> Hey,
> On 11/19/15 14:48, Oleg Hahm wrote:
> > As an effort to "formalize" this idea of task forces a little bit more,
> I just
> > created a small page in the Wiki:
> >
> > What do you think?
>
> +1
>
> I've updated the xtimer page.
>
> 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

Re: [riot-devel] Disabled Strider (1 and 2)

[Emmanuel Baccelli]

+1 for disabling (unless Philipp yells very loud now ;)

On Tue, Nov 17, 2015 at 1:49 PM, Oleg Hahm  wrote:

> Hi,
>
> since the results of both Strider CI systems are currently of very limited
> use and confusing for many people, I decided to deactivate them for now. If
> you object, please shout now!
>
> Cheers,
> Oleg
> --
> panic("Lucy in the sky");
> linux-2.2.16/arch/sparc64/kernel/starfire.c
>
> ___
> 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] module documentation

[Emmanuel Baccelli]

Hi there,
I agree that some text would be very helpful. Actually, the plan was to
indeed provide some such text very soon, right Martine?
Best,
Emmanuel

On Tue, Nov 17, 2015 at 11:03 AM, Kaspar Schleiser 
wrote:

> Hey Martine,
>
> On 11/17/15 09:18, Martine Lenders wrote:
> > The module documentation for RIOT can be found here [1].
>
> duh. ;)
>
> When I saw Ralph's question, I was looking forward to you using the
> opportunity to put some light in how gnrc_ipv6, gnrc_ipv6_router,
> ipv6_router_default, sixlowpan, sixlowpan_nd, sixlowpan_router_nd,
> sixlowpan_border_router_sixlowpan_nd_host, ..., are related.
>
> Sure, it might be in our doxygen, but some words of you might save hours
> of clicking through multiple windows of html documentation.
>
> 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

Re: [riot-devel] Documentation How-To

[Emmanuel Baccelli]

Hi there,

I don't know about 101 or no 101 (although maybe it's too american centric
an expression, indeed, so I'd vote for another title).
But I do support some explicit policy as to how to contribute documentation
to RIOT.
The hope is that it will diminish duplicate documentation, and thus
diminish outdated/conflicting/desynchronized documentation.

best,

Emmanuel

On Tue, Oct 20, 2015 at 8:52 PM, Martine Lenders 
wrote:

> Hi Oleg,
>
> 2015-10-20 19:14 GMT+02:00 Oleg Hahm :
>
>> Hi Martine!
>>
>> > I came up with some "rules" about where to put what documentation: [1].
>> > They represent an idea of how it could be, not how it currently is. Does
>> > anyone has any input on that.
>>
>> I'm still not convinced that we need any rules for that, but if it helps
>> some
>> people, why not. However, what is the title of this page is supposed to
>> mean?
>> It looks a bit confusing to me.
>>
>
> Just a bit I took from our American friends ;-)
> https://en.wikipedia.org/wiki/101_(number)#In_education but if it
> confuses you, rename it ;-)
>
> Cheers,
> Martine
>
> ___
> 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] RIOT Release 2015.09

[Emmanuel Baccelli]

And thank you Oleg for driving "the last mile" for the release!

On Mon, Oct 5, 2015 at 11:35 PM, rakendra thapa <rakendrath...@gmail.com>
wrote:

> Congratulations team !!
>
> Cheers,
> Rakendra
>
> On Tue, Oct 6, 2015 at 3:00 AM, <kas...@schleiser.de> wrote:
>
>> wohoooah!
>>
>>
>> -Original Message-
>> From: Emmanuel Baccelli <emmanuel.bacce...@inria.fr>
>> To: RIOT OS kernel developers <devel@riot-os.org>
>> Sent: Mo., 05 Okt. 2015 23:11
>> Subject: Re: [riot-devel] RIOT Release 2015.09
>>
>> YAY!
>>
>> On Mon, Oct 5, 2015 at 10:55 PM, Martine Lenders <authmille...@gmail.com>
>> wrote:
>>
>>> \o/ finally!
>>>
>>> /goes to bed
>>> Am 05.10.2015 22:17 schrieb "Oleg Hahm" <oliver.h...@inria.fr>:
>>>
>>>> Dear RIOT developers and users,
>>>>
>>>> it has been a long and rocky road, but thanks to the marvellous
>>>> community, we
>>>> managed to finalize the fifth official release of the RIOT operating
>>>> system:
>>>> ---
>>>> * RIOT 2015.09*
>>>> ---
>>>>
>>>> The highlights of this release are three major parts:
>>>> * gnrc network stack
>>>> * xtimer
>>>> * cleanup of CPU and board specific code
>>>>
>>>> The new generic ("gnrc") network stack is a highly modular and
>>>> configurable
>>>> IPv6/6LoWPAN network stack. It implements a large number of IETF RFCs,
>>>> such as
>>>> RFC 2473, RFC 4861, RFC 4944, RFC 6550, or RFC 6775. Furthermore, it
>>>> provides
>>>> a unified API between the different layers and a generic network device
>>>> interface. The provided 6LoWPAN border router (6LBR) can be run on any
>>>> hardware, providing an IPv6 capable network interface or a UART for
>>>> using SLIP
>>>> (RFC 1055).
>>>>
>>>> A new timer subsystem is introduced by xtimer, replacing hwtimer and
>>>> vtimer
>>>> modules. xtimer offers very precise timer operations as well as support
>>>> for
>>>> long-term timers running over days and weeks. Along with well-known
>>>> timer
>>>> operations in RIOT, it also provides a function for accurate periodic
>>>> timers.
>>>> In order to ease porting of your existing RIOT code, a vtimer
>>>> compatibility
>>>> layer can be used on top.
>>>>
>>>> Refactoring and cleaning up the peripheral drivers as well as other CPU
>>>> and
>>>> board specific code, helped to reduce the number of Makefile
>>>> duplication lines
>>>> by about 50% and provide a much cleaner and easier to use interface for
>>>> porting new platforms to RIOT.
>>>>
>>>> Of course this release also comes along with a variety of newly
>>>> supported
>>>> boards, CPUs, and device drivers. RIOT 2015.09 has been ported to the
>>>> Eistec
>>>> Mulle, Phytec phyWAVE, Zolertia ReMote, Atmel SAML21, various ST Nucleo
>>>> boards, Freescale Freedom, TI Stellaris Launchpad, the LimiFrog, and
>>>> Silab's
>>>> Wonder Gecko. It supports a LC display, new light, motion, and
>>>> temperature
>>>> sensors, and more accelerometers and magnetometers.
>>>>
>>>> Just to give you a rough estimation about the tremendous amount of work
>>>> that
>>>> has been put into this release, here are some impressive numbers:
>>>> About 580 pull requests with about 2,500 commits have been merged since
>>>> the
>>>> last release and 120 additional issues have been solved. 62 people
>>>> contributed
>>>> code in 277 days. 2578 files have been touched with ~320,000 insertions
>>>> and
>>>> ~134,000 deletions.
>>>>
>>>> As a major change to our development procedures, the RIOT community
>>>> will offer
>>>> long-term bug fixes for this release in a API-stable branch.
>>>>
>>>> You can download the RIOT release from Github, either by cloning the
>>>> repository or using the tarball:
>>>> https://github.com/RIOT-OS/RIOT/archive/2015.09.tar.gz
>>>>
>>>> Happy RIOT,
>>>> Oleg
>>>> --
>>>> printk(CARDNAME": Bad Craziness - sent packet while busy.\n" );
>>>> linux-2.6.6/drivers/net/smc9194.c
>>>>
>>>> ___
>>>> 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
>
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] RIOT Release 2015.09

[Emmanuel Baccelli]

YAY!

On Mon, Oct 5, 2015 at 10:55 PM, Martine Lenders 
wrote:

> \o/ finally!
>
> /goes to bed
> Am 05.10.2015 22:17 schrieb "Oleg Hahm" :
>
>> Dear RIOT developers and users,
>>
>> it has been a long and rocky road, but thanks to the marvellous
>> community, we
>> managed to finalize the fifth official release of the RIOT operating
>> system:
>> ---
>> * RIOT 2015.09*
>> ---
>>
>> The highlights of this release are three major parts:
>> * gnrc network stack
>> * xtimer
>> * cleanup of CPU and board specific code
>>
>> The new generic ("gnrc") network stack is a highly modular and
>> configurable
>> IPv6/6LoWPAN network stack. It implements a large number of IETF RFCs,
>> such as
>> RFC 2473, RFC 4861, RFC 4944, RFC 6550, or RFC 6775. Furthermore, it
>> provides
>> a unified API between the different layers and a generic network device
>> interface. The provided 6LoWPAN border router (6LBR) can be run on any
>> hardware, providing an IPv6 capable network interface or a UART for using
>> SLIP
>> (RFC 1055).
>>
>> A new timer subsystem is introduced by xtimer, replacing hwtimer and
>> vtimer
>> modules. xtimer offers very precise timer operations as well as support
>> for
>> long-term timers running over days and weeks. Along with well-known timer
>> operations in RIOT, it also provides a function for accurate periodic
>> timers.
>> In order to ease porting of your existing RIOT code, a vtimer
>> compatibility
>> layer can be used on top.
>>
>> Refactoring and cleaning up the peripheral drivers as well as other CPU
>> and
>> board specific code, helped to reduce the number of Makefile duplication
>> lines
>> by about 50% and provide a much cleaner and easier to use interface for
>> porting new platforms to RIOT.
>>
>> Of course this release also comes along with a variety of newly supported
>> boards, CPUs, and device drivers. RIOT 2015.09 has been ported to the
>> Eistec
>> Mulle, Phytec phyWAVE, Zolertia ReMote, Atmel SAML21, various ST Nucleo
>> boards, Freescale Freedom, TI Stellaris Launchpad, the LimiFrog, and
>> Silab's
>> Wonder Gecko. It supports a LC display, new light, motion, and temperature
>> sensors, and more accelerometers and magnetometers.
>>
>> Just to give you a rough estimation about the tremendous amount of work
>> that
>> has been put into this release, here are some impressive numbers:
>> About 580 pull requests with about 2,500 commits have been merged since
>> the
>> last release and 120 additional issues have been solved. 62 people
>> contributed
>> code in 277 days. 2578 files have been touched with ~320,000 insertions
>> and
>> ~134,000 deletions.
>>
>> As a major change to our development procedures, the RIOT community will
>> offer
>> long-term bug fixes for this release in a API-stable branch.
>>
>> You can download the RIOT release from Github, either by cloning the
>> repository or using the tarball:
>> https://github.com/RIOT-OS/RIOT/archive/2015.09.tar.gz
>>
>> Happy RIOT,
>> Oleg
>> --
>> printk(CARDNAME": Bad Craziness - sent packet while busy.\n" );
>> linux-2.6.6/drivers/net/smc9194.c
>>
>> ___
>> 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