Contiki OS for 6502 based computers
Go to file
2010-02-06 10:00:25 +00:00
apps Potential alignment problem fix 2010-02-04 16:21:15 +00:00
backyard moved obsolete cooja projects to backyard 2009-05-18 14:48:10 +00:00
core Turns out that with cxmac, clearing the header after sending a packet is not enough to make fragmentation work. Instead, we allocate a queuebuf and restore the packet after from the queuebuf after sending it. 2010-02-06 09:42:49 +00:00
cpu Missing file 2010-02-05 16:41:23 +00:00
doc Update to Contiki version number 2.4 2010-01-29 18:03:55 +00:00
examples Added a #define option to send more data than needed to be able to test fragmentation 2010-02-06 09:58:59 +00:00
platform Made it possible to override the SICSLOWPAN_CONF_FRAG option. Increased the default uIP buffer size on IPv6 to provide some room for fragmented packets 2010-02-06 10:00:25 +00:00
tools Automated test for testing IPv6/6lowpan fragmentation 2010-02-06 09:57:14 +00:00
Makefile.include removed unused compilation units for IPv6 2009-11-18 15:12:06 +00:00
README
README-BUILDING
README-EXAMPLES Removed energest-demo, which is in contikiprojects now 2010-02-04 21:03:00 +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/