DESCRIPTION

This is a fork of RIOT-OS used to teach EE 250 at USC.

EE 499 Spring 2017 (name before EE 250):

You may find in branches ee499_labs_stable and ee499_labs_develop the code used for some of the experiments.

Branch ee499_labs_develop is used for testing, and branch ee499_labs_stable is used for classes.

Checkout the most recent commits to see the experiments that were developed.

Most of the code changed is inside example folder.

RIOT-OS

The friendly Operating System for IoT!

RIOT is a real-time multi-threading operating system that supports a range of devices that are typically found in the Internet of Things (IoT): 8-bit, 16-bit and 32-bit microcontrollers.

RIOT is based on the following design principles: energy-efficiency, real-time capabilities, small memory footprint, modularity, and uniform API access, independent of the underlying hardware (this API offers partial POSIX compliance).

RIOT is developed by an international open source community which is independent of specific vendors (e.g. similarly to the Linux community). RIOT is licensed with LGPLv2.1, a copyleft license which fosters indirect business models around the free open-source software platform provided by RIOT, e.g. it is possible to link closed-source code with the LGPL code.

FEATURES

RIOT is based on a microkernel architecture, and provides features including, but not limited to:

• a preemptive, tickless scheduler with priorities
• flexible memory management
• high resolution, long-term timers
• support for AVR, MSP430, MIPS, ARM7, and ARM Cortex-M on over 80 boards
• the native port allows to run RIOT as-is on Linux, BSD, and MacOS. Multiple instances of RIOT running on a single machine can also be interconnected via a simple virtual Ethernet bridge
• IPv6
• 6LoWPAN (RFC4944, RFC6282, and RFC6775)
• UDP
• RPL (storing mode, P2P mode)
• CoAP
• CCN-Lite

GETTING STARTED

• You want to start the RIOT? Just follow our quickstart guide or the getting started documentation.
• The RIOT API itself can be built from the code using doxygen. The latest version is uploaded daily to http://riot-os.org/api.

USING THE NATIVE PORT WITH NETWORKING

If you compile RIOT for the native cpu and include the netdev_tap module, you can specify a network interface like this: PORT=tap0 make term

SETTING UP A TAP NETWORK

There is a shellscript in RIOT/dist/tools/tapsetup called tapsetup which you can use to create a network of tap interfaces.

USAGE To create a bridge and two (or count at your option) tap interfaces:

./dist/tools/tapsetup/tapsetup [-c [<count>]]

CONTRIBUTE

To contribute something to RIOT, please refer to the development procedures and read all notes for best practice.

MAILING LISTS

• RIOT OS kernel developers list
• [email protected] (http://lists.riot-os.org/mailman/listinfo/devel)
• RIOT OS users list
• [email protected] (http://lists.riot-os.org/mailman/listinfo/users)
• RIOT commits
• [email protected] (http://lists.riot-os.org/mailman/listinfo/commits)
• Github notifications
• [email protected] (http://lists.riot-os.org/mailman/listinfo/notifications)

LICENSE

• Most of the code developed by the RIOT community is licensed under the GNU Lesser General Public License (LGPL) version 2.1 as published by the Free Software Foundation.
• Some external sources, especially files developed by SICS are published under a separate license.

All code files contain licensing information.

For more information, see the RIOT website:

http://www.riot-os.org