Hi *,
I had some discussions about: "What should our (next) primary platform for RIOT look like".
I have done a short list of points to talk about: https://github.com/RIOT-OS/RIOT/wiki/FutureHardwarePlatforms
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)!
Best Christian
Hi!
I have done a short list of points to talk about: Create new page · RIOT-OS/RIOT Wiki · GitHub
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.
Postscapes provides a nice list of typical IoT platforms:
The Wi-Go Module looks interesting, but is probably too expensive.
Spark Core [1] provides an ARM Cortex-M3 and a 802.11 transceiver, but no sensors. Price: 39$ + 20$
DigiX [2] provides similar hardware for 59$.
Cheers, Oleg
[1] http://www.kickstarter.com/projects/sparkdevices/spark-core-wi-fi-for-everything-arduino-compatible [2] http://www.kickstarter.com/projects/digistump/digix-the-ultimate-arduino-compatible-board-with-w
Hi all, Cedric mentioned this platform last week https://shop.dresden-elektronik.de/radio-modules/minimodul-sam3-23t02-2.html At first sight it seems to match the criterias of price, CPU and memory, and availability. Should we also add this to the potential reference hardware list? Best, Emmanuel
Thema Wiki is for brainstorming 
Emmanuel Baccelli Emmanuel.Baccelli@inria.fr schrieb:
the wiki…
Ludwig Ortmann ludwig.ortmann@fu-berlin.de schrieb:
Hey Ludwig,
Thema Wiki is for brainstorming
I'm with Kaspar: new-fashioned shit! 
Seriously, I think it's good to have this discussion here and put the results in the Wiki.
Cheers, Oleg
Hi!
Cedric mentioned this platform last week https://shop.dresden-elektronik.de/radio-modules/minimodul-sam3-23t02-2.html At first sight it seems to match the criterias of price, CPU and memory, and availability. Should we also add this to the potential reference hardware list?
Looks a good at first glance. I'll update the Wiki.
The only Cortex-based platforms supported by Contiki are mb851 and mbxxx [1]. They look interesting, too, but are unfortunately quite expensive.
Cheers, Oleg
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..
Oleg Hahm <oleg@riot-os.org> schrieb:
I see that all platforms currently discussed are "arm cortex m3"-based, and their primary wireless interface is ieee802.11 based.
So where is the ieee802.15.4 interface? Can we buy this as shield? Or do we switch to 11g?
Does the IOT community moves to good old wifi? That would completely change the networking problems...
Best Christian
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)
Hi Christian,
>https://shop.dresden-elektronik.de/radio-modules/minimodul-sam3-23t02-2.html
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...
Cheers, Oleg
[1] RIOT/drivers/at86rf231 at agilefox · awe00/RIOT · GitHub
Hey,
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.
Cheers, Oleg
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
[1] https://mchck.org/ [2] https://github.com/mchck/mchck/wiki/Details
Hi all,
Stefan just pointed me to the STM32W-RFCKIT (http://www.st.com/web/en/catalog/tools/FM116/SC959/SS1532/PF251361) which provides a Cortex-M3 SoC with 2,4GHz 802.15.4-capable radio.
Unfortunately the board seems to be discontinued but maybe there's gonna be a successor.
Cheers, Oleg
