Re: [riot-devel] Mailserver issues

e: >> Hello. >> >> On 08/11/2017 02:03 PM, Oleg Hahm wrote: >>> Hey Adam! >>> >>> Thanks for the pointer. That's definitely something we should consider. >>> >>> Cheers, >>> Oleg >>> >>> On Fri, Aug 11, 2017

Re: [riot-devel] Mailserver issues

but I know they've been working to stand up an OpenStack cluster they may be able to help out with CI or in other ways. I'm not affiliated with OSUOSL, I just live in their area. --adam On Fri, Aug 11, 2017 at 4:16 AM, Oleg Hahm wrote: > Hi Adam! > > On Fri, Aug 11, 2017 at 04:

Re: [riot-devel] Mailserver issues

Just out of curiosity, was this due to a lack of machine resources? How is RIOT's infrastructure (e.g. web and mail hosting) handled; is the hosting donated by one or more of the supporters listed at the bottom of the project's homepage? Would additional hosting resources be helpful? --adam On Tu

[riot-devel] Porting to the ARTIK 030 module

Has anyone taken a look at the ARTIK 030 module from Samsung? It's a Cortex-M4 based (SiLabs EFR32MG1 SoC) module with 256 kB flash and 32 kB SRAM, a cryto processor, and 802.15.4 radio. In the US they're available from Digikey and Mouser for $7.30 in single unit quantities; I'm not sure who distr

[riot-devel] Helping out with the CI situation

With all the chatter about the CI situation lately I got to wondering if there might be some way I could help out. It sound like Kaspar has things under control with the new CI system but what about builders; are there enough CPU cycles available for the current rate of RIOT development, what about

[riot-devel] 5 Open Source IoT Projects to Watch in 2016

I'm not sure if anyone saw this. Check slide #3. https://blog.benjamin-cabe.com/2016/02/08/5-open-source-iot-projects-to-watch-in-2016 ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] TI CC1310 and CC2650

ct me direclty. > > We will be in Nuremberg at the SPS IPC Drives by next week (24.11.-26.11; > Hall 6, Booth 449), so if you are nearby visit us there. > > Best > Jonas > > -"devel" schrieb: - > An: RIOT OS kernel developers > Von: Adam Hunt >

Re: [riot-devel] TI CC1310 and CC2650

of porting > > TI suggested that I wait for version 2 of the silicon of the CC1350 It > should have been release end of Q3 of this year, I'm still waiting.. > The TI rep will be here today I hope .. > > Any suggestions on the porting process? > > Kind regards >

[riot-devel] TI CC1310 and CC2650

Has anyone taken a look at TI's CC2560 or C1310 processors? They're both based on an a Cortex-M3 processor clocked up to 48 MHz and work in the 2.4 GHz and sub-1 GHz bands respectively. I haven't had a chance to read all the documentation yet but they appear similar to the CC2538, aside from one p

Re: [riot-devel] RIOT Release 2015.09

Great work! On Mon, Oct 5, 2015 at 2:50 PM Matthias Waehlisch wrote: > +1 > > and spread the word that RIOT improves, step by step by the community. > > > Cheers > matthias > > On Mon, 5 Oct 2015, Emmanuel Baccelli wrote: > > > And thank you Oleg for driving "the last mile" for the release! >

Re: [riot-devel] is the msp430 still supported?

When you say MSP430 does that include the CC430 that has the integrated CC1101? How similar is the CC430 compared to a MSP430 and CC1101? Are they 100% compatible? On Sat, Sep 5, 2015 at 1:42 AM Kaspar Schleiser wrote: > Hey, > > On 09/05/15 09:16, Eric Decker wrote: > > or did it get pulled? >

Re: [riot-devel] HotSpot JVM on RIOT-OS?

While I applaud the idea of getting something as heavyweight as a JVM to run on the type of devices that most of us on this list are targeting have you thought about non-JVM languages? I've often wondered how small of a system Erlang could be persuaded to running on. On Wed, Aug 12, 2015 at 4:47 A

Re: [riot-devel] OTA update

A BSDish license with the addition of a poison pill. Too bad. Though, while I'm certainly not a lawyer of any type I wonder about the possibility/legality of basing future works off the code without violating the license. Another option would be to simply ask the powers that be at Atmel to relice

Re: [riot-devel] OTA update

What license have they released their code under? I'd look myself but I'm away from my desk. Adam On Tue, Jun 16, 2015, 7:41 AM Baptiste Clenet wrote: > Those example are provided with the last version of Atmel Studio (which is > free). See here [1], the two examples: > > - 6LoWPAN OTA Client A

Re: [riot-devel] RIOT <-> mac80211

I forgot to mention, these days most wifi devices are softmac based. Examples of fullmac drivers are Atheros' AR600x (ath6kl), and Marvel's libertas USB and SDIO devices. On Wed, May 27, 2015, 1:21 PM Adam Hunt wrote: > Unfortunately, I haven't been able to keep up on all

[riot-devel] RIOT <-> mac80211

Unfortunately, I haven't been able to keep up on all the recent network stack work but while working on a WSN project that's currently Linux based project I got to wondering about the feasibility of 802.11 support in RIOT. I know it's been talked about in the past. Driver and MAC SUPPORT are obviou

Re: [riot-devel] Association time in mobile RPL/6lowpan networks

> Forcing a DIS from userspace sounds like a good feature. It may help in > testing/debuging the dodag tree interactively. > > I also thought about reseting the trickle timer from userspace to > enforce DIOs. > > +1 for this. It would be nice to have some shell commands to call

Re: [riot-devel] Association time in mobile RPL/6lowpan networks

That's great. Is there any way to force a node to send a DIS message from userspace? On Wed, May 20, 2015, 5:34 PM Oleg Hahm wrote: > Hi Adam! > > > Has anyone tested the amount of time it takes for a node (full or reduced > > function) to join an RPL routed 6lowpan network? I realize that it's

[riot-devel] Association time in mobile RPL/6lowpan networks

Has anyone tested the amount of time it takes for a node (full or reduced function) to join an RPL routed 6lowpan network? I realize that it's very likely to vary quite a bit depending on the network, I'm just curious if anyone has an approximate range. Thanks,

Re: [riot-devel] Switch to BSD?

I'd be willing to bet that GNU Classpath is one of the oldest projects licensed under the GPL with a linking exception. Classpath is distributed under the terms of the GNU General Public License > with the following clarification and special exception. > Linking this library statically or dynami

Re: [riot-devel] Changing the workflow.

I really like the idea of task force branches (OTA, net, filesystem, platform, etc..). They seem somewhat reminiscent of Linux's *net, net-next* and similar trees. Would they be implemented as git branches within the main repository (e.g https://github.com/RIOT-OS/RIOT/OTA) or fully independent rep

[riot-devel] How low can you go?

The other day I ran across a few Atmel Raven[0] development boards that I'd forgotten I had ​ (it never ceases to amaze the amount of random electronics I own and have completely forgotten about) . It got me thinking, now that ​ heavy lifting of porting​ RIOT ​ to its first 8 bit micro and running

Re: [riot-devel] Bypassing hardware vendors' unlicensed header files

It might be worth reaching out to maintainers of Linux's ARM port[0] or Russell King[1], the lead maintainer for Linux's port to the ARM microarchitecture. I'd imagine he'd be amenable to helping other open source projects get access to access to suitably licensed ARM documentation, headers, as wel

[riot-devel] Simulation

What simulation environment are people using for RIOT development. I seem to remember there being work done with ns-3 and maybe even Cooja but I don't remember the specifics or the state of that work. Are most people simply using the native port as their development platform? Developing on real ha

[riot-devel] New IPC API status

If memory serves there were a number of potential features that were on the back burner until RIOT's new IPC API was finalized (e.g. filesystem/VFS, and maybe ELF loading). Back in November Kaspar concluded that the approach he had been working on wasn't the correct way forward and closed the PR.[1

Re: [riot-devel] Nordic's 6LoWPAN over Bluetooth Low Energy

While I can think of a few good uses for this chip I'm still not sold on BLE being a good thing for the "Internet of Things". Historically, the Bluetooth SIG has been less than open. Does anyone remember the SIG having BlueZ's site (maybe it was just a mailing list) taken down back in about 2004-20

Re: [riot-devel] MIPS platform (PIC32)

Though, if you ask me, RIOT's code is far cleaner and more approachable than that of some other projects. On Tue Jan 13 2015 at 3:15:56 PM Martine Lenders wrote: > Hi, > > 2015-01-14 0:10 GMT+01:00 Adam Hunt : > >> […] >> > Aside from those you should take a loo

Re: [riot-devel] MIPS platform (PIC32)

nk so since MSP430 and > PIC do not have any) is it using any hardware specific things ?. I am > new to RIOT that is why I ask. Is there a good ducument about the > inner workings of RIOY OS so I can see if there are possible issues > with MIPS. > > Paul. > > Adam Hunt schreef

Re: [riot-devel] MIPS platform (PIC32)

Is there anything special about the MIPS march that would make porting RIOT an issue? Seeing as RIOT runs on 32-bit ARMs, 16-bit MSP430s, x86, and now even 8-bit Atmels I don't imagine there is much standing in the way of another incredibly well documented architecture. Though, I've been wrong befo

Re: [riot-devel] new iot hardware from intel: curie

Interesting, I'd love a little more information on the open source RTOS. I'd also like to a see hardware with a 15.4 capable radio. BLE *may* have its place but as it stands now, without CSR mesh solutions being embraced it's not as an appropriate a solution as 6lowpan over 15.4 for many applicatio

[riot-devel] Searchable devel@riot-os.org archive

s fully searchable and also available via the NNTP for those that prefer it (or even remember it). I've also requested that the user list be archived there and for the older messages be added to the archive but the request hasn't yet been completed (likely because no messages have been post

Re: [riot-devel] Switch to BSD?

At risk of further confusing things maybe there's a happy medium between a strong copyleft/(L)GPL and a the BSD license. While I'm most certainly not a lawyer, copyright or otherwise, a quick look at the Eclipse Public License (EPL) and the related E

Re: [riot-devel] Switch to BSD?

moment.There are other things in my life that I must attend to and Monday is near a close. Adam Hunt On Mon Dec 08 2014 at 1:49:32 PM Johann Fischer wrote: > Hello RIOTers, > > Emmanuel Baccelli wrote: > > we have been receiving an increasing amount of negative feedback from &

Re: [riot-devel] Switch to BSD?

While I've been a fervent supporter of the GPL for many years I'm on board with a change to a simple BSD or MIT style license. Initially I was skeptical about the need to move away from the LGPL but in the world of embedded systems it's very common to make changes to the core codebase in order to w

Re: [riot-devel] Features for the next release

n distracted by sometime shinny, this appears to be exactly what I was looking for. Thanks. Adam On Sun, Nov 23, 2014, 1:29 AM Ludwig Ortmann wrote: > Hi Adam, > > On Sun, Nov 23, 2014 at 08:58:34AM +, Adam Hunt wrote: > > Is there an issue in the tracker which all the planned

Re: [riot-devel] Features for the next release

Is there an issue in the tracker which all the planned features and fixes slated for this release depend on or block? Wiki entries are great but they can easily end up being tombs of quasi-outdated information. Issues in a tracker on the other hand tend to be far more well curated. I'm sorry if so

Re: [riot-devel] Border routers and other multi-radio devices (was: Development status for SAM XR21)

dam On Tue Nov 11 2014 at 1:58:35 PM Martine Lenders wrote: > Hi Adam, > > 2014-11-11 22:43 GMT+01:00 Adam Hunt : > >> This reminds me... I was wondering, would it be possible to host more >> than one wireless interface on a theoretical RIOT border router? I was >&g

Re: [riot-devel] Development status for SAM XR21

This reminds me... I was wondering, would it be possible to host more than one wireless interface on a theoretical RIOT border router? I was thinking about the possibility of a single boarder router with both 2.4 GHz and sub-GHz radios on it. Another thing I was thinking was a wireless coordinator

Re: [riot-devel] Generic address structure for RIOT

I'm with David, having a config file for each app would make life so much easier down the road. I'd especially like to a see a quasi-standards based format used. I'd suggest TOML which is essentially a formalized INI type config. While I haven't personally used i

Re: [riot-devel] Refectoring the network stack

that's being done. On Thu Nov 06 2014 at 10:24:24 AM Martine Lenders wrote: > > Am 06.11.2014 18:56 schrieb "Adam Hunt" : > > > > > > I'm sorry, somehow I missed the point where you mentioned 802.15.4e. > Feel free to ignore me. After last night I

Re: [riot-devel] RIOT/OpenWSN and TSCH support

What are the chances that there will be video of this talk available for those of us who aren't so fortunate to live in the vicinity of IoT-Lab? On Thu Nov 06 2014 at 11:36:53 AM Oleg Hahm wrote: > Hey Thomas! > > > Happy to mention RIOT, I didn't know you were there :-) > > Yes, tomorrow I'll g

Re: [riot-devel] RIOT/OpenWSN and TSCH support

I'd love to attend IETF93 if for no other reason than I have yet to get myself to Prague. Unfortunately, I don't think I'll be about to swing the US$1200 in airfare plus accommodations. I really need to find myself some wealthy benefactor interested in WSN research. On Thu, Nov 6, 2014 at 11:27 AM

Re: [riot-devel] Periodical (virtual) meetings

Sorry to sound like a skipping record but what are the chances that there's a copy of the meeting archived somewhere. I've been ill the past few days and slept through the meeting. On Thu, Nov 6, 2014 at 4:48 AM, Teemu Hakala wrote: > > On 5.11.2014, at 17:56, Hauke Petersen > wrote: > > as Ole

Re: [riot-devel] Dedicated RIOT Testing Meeting

I expect to have some real hardware in hand (CC2538 based boards of my own design, and possibly some MSP430 boards after that) in the coming weeks (months if I don't get into gear). I'd be more than willing to contribute some whatever time is needed to running tests on real hardware if it's helpful

Re: [riot-devel] Refectoring the network stack

I'm sorry, somehow I missed the point where you mentioned 802.15.4e. Feel free to ignore me. After last night I shouldn't be allowed to post in public forums full of people smarter than I. --adam On Nov 6, 2014 9:46 AM, "Martine Lenders" wrote: > Hi Adam, > > Am 0

Re: [riot-devel] Refectoring the network stack

Is support for TSCH in there somewhere? While I'm not entirely read up on the spec it would seem to be fairly important these days. What is the current state of TSCH support in RIOT these days? I'm stuck on my phone at the moment or I'd take a look for myself (really, it probably has a bit more to

Re: [riot-devel] CC2538 development

this [1] PR we have > basic support for the OpenMote in RIOT! > > Cheers, > Hauke > > [1] https://github.com/RIOT-OS/RIOT/pull/1864 > > > On 21.10.2014 23:41, Adam Hunt wrote: > > ​I see that recently there's been work being done on getting RIOT up to > speed o

[riot-devel] CC2538 development

pping me from still doing that. I'm quite ecstatic that work on this chip has begun in what looks like a serious way. I'm going to do my best to put aside as much of my other work as possible, sleep only when my head hits the keyboard, and get my boards finalized and a prototype set run so