[riot-devel] Riot on iot-lab

Oleg Hahm oliver.hahm at inria.fr
Wed May 25 18:17:36 CEST 2016


On Wed, May 25, 2016 at 06:10:47PM +0200, Gaëtan Harter wrote:
> > > - adding support of samr21-xpro boards as new custom nodes. Of course, I
> > > wrote a firmware code based on RIOT for the continuous integration system
> > > ;). But to make it fully compatible with what the CI is expecting, I had to
> > > patch slightly the RIOT shell code by removing the echo of the input command
> > > and the display of the prompt character ('>'). This patch is based on
> > > compiler options (SHELL_NO_PROMPT and SHELL_NO_ECHO) which are not set by
> > > default. Would you accept such a contribution ? (I know it doesn't really
> > > help RIOT).
> > Out of curiosity: what is different for the samr21-xpro nodes compared to the
> > "regular" iotlab-m3 nodes where we don't need this patch?
> For M3 and A8-M3 nodes, the test firmwares are written using openlab.

thanks for the explanation. So, we're talking here actually not about the code
that the user is supposed to run, but about the software used for internal

> For samr21-xpro, as it is not supported by openlab, we thought it would be a
> good idea to write this firmware using RIOT.

Sounds like a splendid idea to me, too. ;-)

> In the same time it would give us a firmware compilable with platforms
> supported by RIOT.
> Then, adding support for any RIOT compatible board on IoT-LAB would only be
> adding administration code.


My computer is so slow that sometimes it gets a timeout from http://localhost.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.riot-os.org/pipermail/devel/attachments/20160525/545e2b11/attachment.sig>

More information about the devel mailing list