Contiki is an operating system for networked, memory-constrained systems with a focus on low-power wireless Internet of Things devices. Extant uses for Contiki include systems for street lighting, sound monitoring for smart cities, radiation monitoring, and alarms. It is open-source software released under a BSD license.
Screenshot of an Ubuntu system showing Contiki 2.6 running on 41 nodes forming an IPv6-RPL-6LoWPAN network in the Cooja Contiki network simulator.
|Source model||Open source|
|Initial release||10 March 2003|
|Latest release||3.0 / 26 August 2015|
Contiki was created by Adam Dunkels in 2002 and has been further developed by a worldwide team of developers from Texas Instruments, Atmel, Cisco, ENEA, ETH Zurich, Redwire, RWTH Aachen University, Oxford University, SAP, Sensinode, Swedish Institute of Computer Science, ST Microelectronics, Zolertia, and many others. Contiki gained popularity because of its built in TCP/IP stack and lightweight preemptive scheduling over event-driven kernel which is a very motivating feature for IoT. The name Contiki comes from Thor Heyerdahl's famous Kon-Tiki raft.
Contiki provides multitasking and a built-in Internet Protocol Suite (TCP/IP stack), yet needs only about 10 kilobytes of random-access memory (RAM) and 30 kilobytes of read-only memory (ROM). A full system, including a graphical user interface, needs about 30 kilobytes of RAM.
A new branch has recently been created, known as Contiki-NG: The OS for Next Generation IoT Devices
Contiki is designed to run on types of hardware devices that are severely constrained in memory, power, processing power, and communication bandwidth. A typical Contiki system has memory on the order of kilobytes, a power budget on the order of milliwatts, processing speed measured in megaHertz, and communication bandwidth on the order of hundreds of kilobits/second. Such systems include many types of embedded systems, and old 8-bit computers.
Contiki provides three network mechanisms: the uIP TCP/IP stack, which provides IPv4 networking, the uIPv6 stack, which provides IPv6 networking, and the Rime stack, which is a set of custom lightweight networking protocols designed for low-power wireless networks. The IPv6 stack was contributed by Cisco and was, when released, the smallest IPv6 stack to receive the IPv6 Ready certification. The IPv6 stack also contains the Routing Protocol for Low power and Lossy Networks (RPL) routing protocol for low-power lossy IPv6 networks and the 6LoWPAN header compression and adaptation layer for IEEE 802.15.4 links.
Rime is an alternative network stack, for use when the overhead of the IPv4 or IPv6 stacks is prohibitive. The Rime stack provides a set of communication primitives for low-power wireless systems. The default primitives are single-hop unicast, single-hop broadcast, multi-hop unicast, network flooding, and address-free data collection. The primitives can be used on their own or combined to form more complex protocols and mechanisms.
Many Contiki systems are severely power-constrained. Battery operated wireless sensors may need to provide years of unattended operation and with little means to recharge or replace batteries. Contiki provides a set of mechanisms to reduce the power consumption of systems on which it runs. The default mechanism for attaining low-power operation of the radio is called ContikiMAC. With ContikiMAC, nodes can be running in low-power mode and still be able to receive and relay radio messages.
The Contiki system includes a network simulator called Cooja, which simulates networks of Contiki nodes. The nodes may belong to either of three classes: emulated nodes, where the entire hardware of each node is emulated, Cooja nodes, where the Contiki code for the node is compiled for and executed on the simulation host, or Java nodes, where the behavior of the node must be reimplemented as a Java class. One Cooja simulation may contain a mix of nodes from any of the three classes. Emulated nodes can also be used to include non-Contiki nodes in a simulated network.
To run efficiently on small-memory systems, the Contiki programming model is based on protothreads. A protothread is a memory-efficient programming abstraction that shares features of both multithreading and event-driven programming to attain a low memory overhead of each protothread. The kernel invokes the protothread of a process in response to an internal or external event. Examples of internal events are timers that fire or messages being posted from other processes. Examples of external events are sensors that trigger or incoming packets from a radio neighbor.
Protothreads are cooperatively scheduled. Thus, a Contiki process must always explicitly yield control back to the kernel at regular intervals. Contiki processes may use a special protothread construct to block waiting for events while yielding control to the kernel between each event invocation.
Contiki supports per-process optional preemptive multithreading, inter-process communication using message passing through events, as well as an optional graphical user interface (GUI) subsystem with either direct graphic support for locally connected terminals or networked virtual display with Virtual Network Computing (VNC) or over Telnet.
A full installation of Contiki includes the following features:
- Multitasking kernel
- Optional per-application preemptive multithreading
- Internet Protocol Suite (TCP/IP) networking, including IPv6
- Windowing system and GUI
- Networked remote display using Virtual Network Computing
- A web browser (claimed to be the world's smallest)
- Personal web server
- Simple telnet client
The Contiki operating system is ported to the following systems:
- cc65 based development
- Contiki OS.
- Contiki: Bringing IP to Sensor Networks
- "Community", Contiki OS.
- Dunkels, Adam (2004), "Contiki – a lightweight and flexible operating system for tiny networked sensors", Proceedings of the 29th Annual IEEE International Conference on Local Computer Networks., pp. 455–462.
- Out in the Open: The Little-Known Open Source OS That Rules the Internet of Things
- Dunkels, Adam (May 2003), "Full TCP/IP for 8 Bit Architectures", Proceedings of the First ACM/Usenix International Conference on Mobile Systems, Applications and Services (MobiSys), San Francisco
- Durvy, Mathilde; Abeillé, Julien; Wetterwald, Patrick; O'Flynn, Colin; Leverett, Blake; Gnoske, Eric; Vidales, Michael; Mulligan, Geoff; Tsiftes, Nicolas; Finne, Niclas; Dunkels, Adam (November 2008), "Making sensor networks IPv6 ready", Proceedings of the Sixth ACM Conference on Networked Embedded Sensor Systems (SenSys) (poster session), Raleigh, NC, US: ACM
- Newsroom, Cisco, 2008.
- Dunkels, Adam; Österlind, Fredrik; He, Zhitao (November 2007), "An adaptive communication architecture for wireless sensor networks", Proceedings of the Fifth ACM Conference on Networked Embedded Sensor Systems (SenSys), Sydney, AU.
- Dunkels, Adam, The ContikiMAC Radio Duty Cycling Protocol (PDF).
- "Start", Contiki OS.
- Dunkels, Adam; Schmidt, Oliver; Voigt, Thiemo; Ali, Muneeb (November 2006), "Protothreads: Simplifying event-driven programming of memory-constrained embedded systems", Proceedings of the Fourth ACM Conference on Embedded Networked Sensor Systems (SenSys), Boulder, CO, USA Dunkels, A.; Schmidt, O.; Voigt, T.; Ali, M. (2006). "Protothreads". Proceedings of the 4th international conference on Embedded networked sensor systems - Sen Sys '06. p. 29. doi:10.1145/1182807.1182811. ISBN 1595933433. (PDF, Presentation slides).
- "Protothread", Code, Google.
- "wolfSSL CONTIKI OS port - wolfSSL". 2018-12-18. Retrieved 2019-01-09.
- Stein, H, Running Contiki under Windows, Trix, archived from the original on 2003-12-09.
- C64Web: a web site run from an unmodified 1982 built Commodore 64
- "Tools Contiki", Hitmen, AT: C02: unofficial website for historic ports of the 1.x version.
- "Minimal Contiki OS for LPC2103", Manishshakya, NP, archived from the original on 2014-06-04.
- Contiki 2.5 config file and disk image generator, A2 retro systems.
- Contiki porting on PIC32 (Seed-Eye Board), IT: SSSUP.