Smart supermarket toy implementation for Networked Embedded Systems exam on Launchpad CC2650 with contiki-ng
Go to file
oliverschmidt 080ecc5488 Changed packet drivers from services to plain processes.
Now tcpip_output() is a function pointer that is supposed to be set via the macro tcpip_set_outputfunc(). Packet drivers do so on process startup.

Thus if there are several packet drivers in a Contiki system the one started last is the one actually used. This behaviour is especially useful for the 'IP forwarding' "meta" packet driver.
2007-05-21 22:29:13 +00:00
apps Made the webserver cfs support build and run. 2007-04-23 23:08:44 +00:00
core * Rename field reserved to prefix_sz. 2007-05-21 15:26:57 +00:00
cpu * Use _end rather than nonstandard __bss_end. 2007-05-21 15:29:46 +00:00
doc Changed packet drivers from services to plain processes. 2007-05-21 22:29:13 +00:00
examples Changed Contiki File System (cfs) from a service to a plain library. 2007-05-19 21:05:48 +00:00
platform removed old cfs.c 2007-05-21 14:57:47 +00:00
tools * Line buffered stdout (also when pipe). 2007-05-21 15:22:45 +00:00
Makefile
Makefile.include Changed packet drivers from services to plain processes. 2007-05-20 21:29:39 +00:00
README README 2007-03-29 23:42:18 +00:00
README-BUILDING Language fix 2007-03-30 08:17:47 +00:00
README-EXAMPLES Readme file for the examples 2007-03-31 18:46:05 +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/