You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Go to file
authmillenon 9117bb2b76 Implement simple echo request/reply 10 years ago
core fix priority comparison in sched_switch 10 years ago
cpu Merge pull request #112 from OlegHahm/msb430_uart0 10 years ago
dist fix minor typo in status output 10 years ago
doc Tell Doxygen to ignore __attribute__ 10 years ago
drivers fixes for #62: eliminate unused parameter warnings 10 years ago
sys Implement simple echo request/reply 10 years ago
.astylerc added astyle options file for coding conventions 10 years ago
.gitignore Update .gitignore 10 years ago
LICENSE * updated LICENSE file from GPL to LPGL 10 years ago
Makefile Define phony make targets 10 years ago
Makefile.base Define phony make targets 10 years ago
Makefile.dep fix for #87, replacing - with _ in module protocol_multiplex 10 years ago
Makefile.include minor changes according to 7a2cc4ae09 10 years ago
Makefile.modules restructured and fixed arm architecutre files 10 years ago
README.md added mailing lists and getting started information, fixed some links 10 years ago
keyword_space.sed minor error in sed expression 10 years ago

README.md

                      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 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 managment
  • high resolution timers
  • virtual, long-term timers
  • Wiselib support (C++ algorithm library, including routing, clustering, timesync, localization, security and more algorithms)
  • IPv6
  • TCP and UDP
  • 6LoWPAN
  • RPL

Development Procedures

  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.

Getting Started

Mailing Lists

License

  • 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:

http://www.riot-os.org