Go to file
Oleg Hahm 9fff3f5b90 Merge pull request #657 from LudwigOrtmann/wsn430-v1_4_Makefiles
fix wsn430-v1_4 Makefiles
2014-02-11 17:55:11 +01:00
boards Merge pull request #657 from LudwigOrtmann/wsn430-v1_4_Makefiles 2014-02-11 17:55:11 +01:00
core add name to sysconfig 2014-02-06 18:13:48 +01:00
cpu changed assignment to const char* 2014-02-10 08:29:22 +01:00
dist updated INCLUDES part for the dist Makefile 2014-01-21 15:28:00 +01:00
doc substitute folder with directory 2014-01-22 20:17:07 +01:00
drivers Merge pull request #646 from BytesGalore/fix_tranceiver_pid_for_cc110x_ng 2014-02-11 17:09:24 +01:00
examples Merge pull request #657 from LudwigOrtmann/wsn430-v1_4_Makefiles 2014-02-11 17:55:11 +01:00
pkg Merge pull request #578 from LudwigOrtmann/libcoap_makefile 2014-01-31 07:21:50 -08:00
sys Merge pull request #655 from OlegHahm/cc110x_header 2014-02-11 15:47:24 +01:00
tests remove stale cc110x_ng includes 2014-02-07 19:22:27 +01:00
.astylerc Change to 1tbs in .astylerc 2014-01-06 11:41:00 +01:00
.gitignore Update .gitignore 2013-08-08 14:51:33 +02:00
LICENSE * updated LICENSE file from GPL to LPGL 2013-06-18 17:19:53 +02:00
Makefile added docclean target and replaced make calls by variables 2014-01-21 14:52:55 +01:00
Makefile.base muting compiler and binutils optionally 2014-01-05 16:11:08 +01:00
Makefile.dep model uart dependency on posix 2014-02-06 12:29:02 +01:00
Makefile.include Merge pull request #661 from LudwigOrtmann/Makefile_dep 2014-02-11 17:44:59 +01:00
Makefile.modules move Makefile.dep include 2014-02-07 21:24:42 +01:00
Makefile.unsupported imported test projects (from projects repository) 2014-01-10 16:21:35 +01:00
README.md fix paths in README.md 2014-02-01 12:22:00 +01:00
keyword_space.sed minor error in sed expression 2013-08-12 20:26:48 +02:00
release-2013.08.txt added the release notes for 2013.08 2013-08-16 08:44:41 +02:00
release-2014.01.txt substitute folder with directory 2014-01-22 20:17:07 +01:00


                 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                                             

The friendly Operating System for IoT!


RIOT OS is an operating system for Internet of Things (IoT) devices. It is based on a microkernel and designed for

  • energy efficiency
  • hardware independent development
  • a high degree of modularity

Its features comprise

  • a preemptive, tickless scheduler with priorities
  • flexible memory management
  • high resolution timers
  • virtual, long-term timers
  • 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
  • Wiselib support (C++ algorithm library, including routing, clustering, timesync, localization, security and more algorithms)
  • IPv6
  • TCP and UDP
  • 6LoWPAN
  • RPL



If you compile RIOT for the native cpu and include the nativenet module, you need to specify a network interface like this: ./bin/native/default.elf tap0


There is a shellscript in RIOT/cpu/native called tapsetup.sh 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: ./tapsetup.sh create [count]


In the examples directory you can find some example applications. The default application demonstrates all available features for the current platform.

For example, you can use it to the test the native networking by running the ./bin/native/default.elf twice with two different tap interfaces as parameters, e.g. tap0 and tap1. Now configure two different addresses for both RIOT instances by typing addr 1 and addr 2accordingly and send a text message from one "node" to another by typing txtsnd 2 hello on the first "node".


  1. Check if your code follows the https://github.com/RIOT-OS/RIOT/wiki/Coding-conventions. If the code does not comply these style rules, your code will not be merged.

  2. Create a new branch in your own fork for every new feature or fix. Then create the pull request from this branch, once you completed your task (feature or fix). Every commit in this branch will be added to the pull request.

  3. The master branch should always be in a working state. The RIOT maintainers will create release tags based on this branch, whenever a milestone is completed.

  4. New features and fixes will always be submitted as pull requests. A pull request will be merged if the RIOT maintainers acknowledge the request. Before it will get merged, the pull request has to stay open long enough to discuss possible issues, but no longer than 30 days. The more extensive the changes in the pull request, the more time should be given for discussion.

  5. Comments on a pull request should be added to the request itself, and not to the commit.

  6. Only RIOT maintainers have commit rights to the main RIOT repository. However, even they have to create pull requests to submit their changes. A RIOT contributor cannot acknowledge his own pull request. All current RIOT maintainers are listed in the wiki.

  7. Keep commits to the point, e.g., don't add whitespace/typo fixes to other code changes. If changes are layered, layer the patches.

  8. Describe the technical detail of the change(s) as specific as possible.



  • All sources and binaries that have been developed at Freie Universität Berlin are licensed under the GNU Lesser General Public License version 2 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: