You should see this page as a starting point for a discussion! I'm sure I have missed some major points, so if you want to add/remove some requirements or if you know the best platform for the future of RIOT, tell us on this list (and I will add your points to the wiki)!
You should see this page as a starting point for a discussion! I'm
sure I have missed some major points, so if you want to add/remove
some requirements or if you know the best platform for the future of
RIOT, tell us on this list (and I will add your points to the wiki)!
I would think that "some sort of sensors to play with" is no must-have as long
as the platform offers accessible I/O-ports.
Moreover, "at least as much ram/rom as the msba2" seems like a quite strong
requirement. I guess that this would limit the choice mostly to ARM-A8/9
powered devices.
I would say that a "energy measurement feature" is more a nice to have, while
a debugging interface (e.g., JTAG) would be a "must have" in my opinion.
Well its obviously my fault for trying to compose meaningful messages in the supermarket, but what i meant was:
The wiki is the right place to collect information on possible hardware, besides it is already being used for exactly that.
Of course the discussion shouldn't take place there..
I see that all platforms currently discussed are "arm cortex
m3"-based, and their primary wireless interface is ieee802.11 based.
the Atmel SAM3S features an at86rf231 which is designed for 802.15.4 - and
already (partly) supported by RIOT. [1]
Does the IOT community moves to good old wifi? That would completely
change the networking problems...
I think IoT comprises both technologies: 802.15.4 and 802.11 (and probably
many more link layers, such as 802.3 or PLC). In my opinion, this is one main
difference to classical WSNs: standardized network protocols ranging from
lossy, low-power links to rather powerful ones.
ps: I think the raspberry pi isn't really what we want: too powerful
cpu, no wireless, a lot of interfaces we don't need...hdmi (video
support)
Well, I think the Raspberry wouldn't fit as a reference platform, but could be
considered as the upper end for the range of IoT devices. Hence, we're
targeting to support this platform with RIOT - maybe w/o features like HDMI...
I've just come across the Virtenio website (a Berlin company we met at the
ETSI plugtest) and the information about their hardware:
http://www.virtenio.com/de/preon32.html
They don't provide information about the exact hardware or if and how their
platform can be programmed, but the platform itself looks good and the
description of their MCU sounds very similar to the NXP LPC2387 we're using on
the MSB-A2.
fyi, spline is currently ordering a bunch of MC HCK boards [1] with a
MK20DX128VLF5 (50MHz ARM Cortex M4, 128KB Flash and 16KB RAM) for
~6-7€/pcs.
However, that's less powerfull than the MSB-A2, especially memory wise.
Radio module is optional, [2] suggests
http://www.ebay.com/itm/140729185691