ZZZZZZ ZZZZZZZZZZZZ ZZZZZZZZZZZZZZZZ ZZZZZZZ ZZZZZZ ZZZZZZ ZZZZZ ZZZZZ ZZZZ ZZZZ ZZZZZ ZZZZ ZZZZ ZZZZ ZZZZZ ZZZZ ZZZZZZ ZZZZ ZZZZZZZZ 777 7777 7777777777 ZZ ZZZZ ZZZZZZZZ 777 77777777 77777777777 ZZZZZZZ ZZZZ ZZZZZZZ 777 7777 7777 777 ZZZZZZZZZ ZZZZ Z 777 777 777 777 ZZZZZZ ZZZZ 777 777 777 777 ZZZZZ ZZZZ 777 777 777 777 ZZZZZ ZZZZZ ZZZZ 777 777 777 777 ZZZZ ZZZZZ ZZZZZ 777 777 777 777 ZZZZ ZZZZZ ZZZZZ 777 777 777 777 ZZZZ ZZZZ ZZZZZ 777 777 777 777 ZZZZZ ZZZZZ ZZZZZ 777 777 777 777 ZZZZZZ ZZZZZZ ZZZZZ 777 7777777777 777 ZZZZZZZZZZZZZZZ ZZZZ 777 77777777 777 ZZZZZZZZZZZ Z ZZZZZ
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.
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, ARM7, and ARM Cortex-M on over 50 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
- 6LoWPAN (RFC4944, RFC6282, and RFC6775)
- RPL (storing mode, P2P mode)
- 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.
- With latest GCC version (>= 6) platforms based on some ARM platforms will
raise some warnings, leading to a failing build
As a workaround, you can compile with warnings not being treated as errors:
USING THE NATIVE PORT WITH NETWORKING
If you compile RIOT for the native cpu and include the
you can specify a network interface like this:
PORT=tap0 make term
SETTING UP A TAP NETWORK
There is a shellscript in
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>]]
To contribute something to RIOT, please refer to the development procedures and read all notes for best practice.
- RIOT OS kernel developers list
- email@example.com (http://lists.riot-os.org/mailman/listinfo/devel)
- RIOT OS users list
- firstname.lastname@example.org (http://lists.riot-os.org/mailman/listinfo/users)
- RIOT commits
- email@example.com (http://lists.riot-os.org/mailman/listinfo/commits)
- Github notifications
- firstname.lastname@example.org (http://lists.riot-os.org/mailman/listinfo/notifications)
- 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: