Contiki OS for 6502 based computers
Go to file
2008-06-11 19:04:14 +00:00
apps Fixed copy&paste issue. 2008-05-24 08:31:56 +00:00
backyard Moved old unused files to backyard 2008-05-27 13:16:34 +00:00
core Changed energest_type_time() to first update the total time, if the device 2008-06-02 13:12:07 +00:00
cpu Removed '!' as gnumake already adds '.'. 2008-05-22 19:43:08 +00:00
doc Contributions from Michael Baar. 2008-04-28 11:36:59 +00:00
examples Reverted mistake commit 2008-06-02 08:42:34 +00:00
platform clear bit when uart edge is set. 2008-05-29 22:06:18 +00:00
tools Tool for Base64 encoding 2008-06-11 19:04:14 +00:00
Makefile.include Now that we started adding files to the CVS which are normally generated with a 'save...' make goal we can remove the DEFAULT_TARGET mechanism altogether and just add Makefile.target files. 2008-05-26 10:09:12 +00:00
README README 2007-03-29 23:42:18 +00:00
README-BUILDING Many project Makefiles build just one Contiki binary. Up to now the name of this binary was only available to the 'all' goal as prerequisite. So it was possible to create a non-project-specific rule to i.e. load that binary into the target device. 2008-05-26 08:04:10 +00:00
README-EXAMPLES Introduced web browser as new example using ctk fullscreen mode. 2007-12-15 22:36:50 +00:00

Contiki is an open source, highly portable, multi-tasking operating
system for memory-constrained networked embedded systems written by
Adam Dunkels at the Networked Embedded Systems group at the Swedish
Institute of Computer Science.

Contiki is designed for embedded systems with small amounts of
memory. A typical Contiki configuration is 2 kilobytes of RAM and 40
kilobytes of ROM. Contiki consists of an event-driven kernel on top of
which application programs are dynamically loaded and unloaded at
runtime. Contiki processes use light-weight protothreads that provide
a linear, thread-like programming style on top of the event-driven
kernel. Contiki also supports per-process optional preemptive
multi-threading, interprocess communication using message passing
through events, as well as an optional GUI subsystem with either
direct graphic support for locally connected terminals or networked
virtual display with VNC or over Telnet.

Contiki contains two communication stacks: uIP and Rime. uIP is a
small RFC-compliant TCP/IP stack that makes it possible for Contiki to
communicate over the Internet. Rime is a lightweight communication
stack designed for low-power radios. Rime provides a wide range of
communication primitives, from best-effort local area broadcast, to
reliable multi-hop bulk data flooding.

Contiki runs on a variety of platform ranging from embedded
microcontrollers such as the MSP430 and the AVR to old
homecomputers. Code footprint is on the order of kilobytes and memory
usage can be configured to be as low as tens of bytes.

Contiki is written in the C programming language and is freely
available as open source under a BSD-style license. More information
about Contiki can be found at the Contiki home page:
http://www.sics.se/contiki/