|
| 1 | +RIOT-2013.08 - Release Notes |
| 2 | +============================ |
| 3 | +RIOT is a real-time multi-threading operating system that supports a range of |
| 4 | +devices that are typically found in the Internet of Things: from 16-bit |
| 5 | +microcontrollers to light-weight 32-bit processors. |
| 6 | + |
| 7 | +RIOT is based on the following design principles: energy-efficiency, real-time |
| 8 | +capabilities, small memory footprint, modularity, and uniform API access, |
| 9 | +independent of the underlying hardware (this API offers partial POSIX |
| 10 | +compliance). |
| 11 | + |
| 12 | +RIOT leverages a robust micro-kernel architecture based on the FeuerWare kernel |
| 13 | +originally developed in 2008 targeting Wireless Sensor Networks, and further |
| 14 | +developed in µkleos. As such, RIOT is the direct heir of FeuerWare and µkleos. |
| 15 | + |
| 16 | +To lower the hurdles for new developers, all coding in RIOT can be done in |
| 17 | +standard C (or C++) with standard tools like gcc and gdb, which also |
| 18 | +facilitates application development and adaptation of existing Linux libraries. |
| 19 | +Last but not least: the native port allows to run RIOT as-is on Linux and |
| 20 | +MacOS. Multiple instances of RIOT running on a single machine can also be |
| 21 | +interconnected via a simple virtual Ethernet bridge, which facilitates |
| 22 | +networked application development. |
| 23 | + |
| 24 | +Features |
| 25 | +======== |
| 26 | +Kernel |
| 27 | +------ |
| 28 | +- Microkernel with a powerful messaging system |
| 29 | +- Multi-Threading with low overhead |
| 30 | +- an energy-efficient, real-time capable scheduler |
| 31 | +- small memory footprint |
| 32 | + |
| 33 | +Userspace |
| 34 | +--------- |
| 35 | +- 6LoWPAN according to RFC 4944, RFC 6282, and RFC 6775 |
| 36 | +- TCP and UDP |
| 37 | +- RPL according to RFC 6550 and RFC 6719 |
| 38 | +- High resolution and long-term timers |
| 39 | +- POSIX IO and BSD socket API |
| 40 | +- Bloom filter |
| 41 | +- SHA256 |
| 42 | + |
| 43 | +Hardware Support |
| 44 | +---------------- |
| 45 | +- various ARM and MSP430 MCUs |
| 46 | + * ARM7 NXP LPC2387 |
| 47 | + * TI MSP430F1612 |
| 48 | + * TI CC430F6137 |
| 49 | + * ARM7 Freescale MC13224v (preliminary) |
| 50 | + * ARM Cortex-M4 STM32f407vgt6 (preliminary) |
| 51 | + * ARM Cortex-M3 STM32f103rey6 (preliminary) |
| 52 | +- radio drivers |
| 53 | + * TI CC1100 and CC1101 |
| 54 | + * TI CC2420 |
| 55 | + * Atmel AT86RF231 |
| 56 | +- sensor drivers |
| 57 | + * Sensirion SHT11 |
| 58 | + * Linear Technology LT4150 |
| 59 | + |
| 60 | +Known Issues |
| 61 | +============ |
| 62 | +#21: Deal with stdin in bordermultiplex.c |
| 63 | + Not all supported platforms provide a stdin in the current release. |
| 64 | + However, the implementation of the 6LoWPAN border router won't work |
| 65 | + without stdin. |
| 66 | +#45: bit field order in the fcf may be wrong |
| 67 | + The CC2420 FIFO expects the IEEE802.15.4 FCF field in reversed bit order. |
| 68 | + This might break the implementation for other, upcoming radio |
| 69 | + transceivers. |
| 70 | +#83: Wrong byte order in sixlowpan |
| 71 | + The 6LoWPAN stack might still contain some variables using the wrong byte |
| 72 | + order. |
| 73 | +#132: segfault in vtimer update shortterm |
| 74 | + The vtimer is known to be buggy on all platforms and causes segmentation |
| 75 | + faults on the native port. |
| 76 | + |
| 77 | +For more issues please check the RIOT issue tracker: |
| 78 | +https://github.com/RIOT-OS/RIOT/issues |
| 79 | + |
| 80 | +More information |
| 81 | +================ |
| 82 | +http://www.riot-os.org |
| 83 | + |
| 84 | +Mailing lists |
| 85 | +------------- |
| 86 | +* RIOT OS kernel developers list |
| 87 | + * devel@riot-os.org (http://lists.riot-os.org/mailman/listinfo/devel) |
| 88 | +* RIOT OS users list |
| 89 | + * users@riot-os.org (http://lists.riot-os.org/mailman/listinfo/users) |
| 90 | +* RIOT commits |
| 91 | + * commits@riot-os.org (http://lists.riot-os.org/mailman/listinfo/commits) |
| 92 | +* Github notifications |
| 93 | + * notifications@riot-os.org (http://lists.riot-os.org/mailman/listinfo/notifications) |
| 94 | + |
| 95 | +License |
| 96 | +======= |
| 97 | +* All sources and binaries that have been developed at Freie Universität Berlin are |
| 98 | + licensed under the GNU Lesser General Public License version 2 as published by the |
| 99 | + Free Software Foundation. |
| 100 | +* Some external sources, especially files developed by SICS are published under |
| 101 | + a separate license. |
| 102 | + |
| 103 | +All code files contain licensing information. |
0 commit comments