osd-contiki/regression-tests/01-compile-base/Makefile

EXAMPLESDIR=../../examples
TOOLSDIR=../../tools

EXAMPLES = \
hello-world/avr-raven \
hello-world/exp5438 \
hello-world/micaz \
hello-world/minimal-net \
hello-world/native \
hello-world/sky \
hello-world/wismote \
hello-world/z1 \
eeprom-test/native \
collect/sky \
er-rest-example/sky \
example-shell/native \
netperf/sky \
powertrace/sky \
rime/sky \
rime/z1 \
ravenusbstick/avr-ravenusb \
rest-example/sky \
servreg-hack/sky \
sky/sky \
sky-ip/sky \
sky-shell/sky \
sky-shell-exec/sky \
sky-shell-webserver/sky \
telnet-server/minimal-net \
webserver/minimal-net \
webserver-ipv6/exp5438 \
wget/minimal-net \
z1/z1 \
settings-example/avr-raven \

TOOLS=

include ../Makefile.compile-test
Contiki regression tests, grouped into categories 2012-12-08 22:10:30 +01:00			`EXAMPLESDIR=../../examples`
			`TOOLSDIR=../../tools`

			`EXAMPLES = \`
			`hello-world/avr-raven \`
			`hello-world/exp5438 \`
			`hello-world/micaz \`
			`hello-world/minimal-net \`
			`hello-world/native \`
			`hello-world/sky \`
			`hello-world/wismote \`
			`hello-world/z1 \`
cpu/native: Add file-backed simulated EEPROM to native cpu. This patch removes a defunct EEPROM implementation from the native platform and provides a new EEPROM implementation for the native cpu. The previous implementation appears to be vestigal. This is useful for testing code which uses the EEPROM without running the code on the actual hardware. By default the code will create a new temporary file as the EEPROM backing, reinitializing each time. If you would like to preserve the EEPROM contents or specify a specific EEPROM file to use, you can set the `CONTIKI_EEPROM` environment variable to the name of the EEPROM file you wish to use instead. If it already exists, its contents will be used. If it does not already exist, it will be created and initialized by filling it with `0xFF`---just like a real EEPROM. A new example is also included, which was used to verify the correctness of the implementation. It can easily be used to verify the EEPROM implementations of other targets. 2013-01-10 18:34:48 +01:00			`eeprom-test/native \`
Contiki regression tests, grouped into categories 2012-12-08 22:10:30 +01:00			`collect/sky \`
			`er-rest-example/sky \`
			`example-shell/native \`
			`netperf/sky \`
			`powertrace/sky \`
			`rime/sky \`
			`rime/z1 \`
avr-ravenusb/cdc_task: Fix compile issues. A lot more changes are in the pipeline, but compiling is a good start. 2013-03-11 17:59:20 +01:00			`ravenusbstick/avr-ravenusb \`
Contiki regression tests, grouped into categories 2012-12-08 22:10:30 +01:00			`rest-example/sky \`
			`servreg-hack/sky \`
			`sky/sky \`
			`sky-ip/sky \`
			`sky-shell/sky \`
			`sky-shell-exec/sky \`
			`sky-shell-webserver/sky \`
			`telnet-server/minimal-net \`
			`webserver/minimal-net \`
Don't compile webserver-ipv6 for the sky platform, as it is a little too small. Use the larger exp5438 instead 2013-11-24 17:45:34 +01:00			`webserver-ipv6/exp5438 \`
Contiki regression tests, grouped into categories 2012-12-08 22:10:30 +01:00			`wget/minimal-net \`
Added rtests for 8051 ports 2012-12-16 20:26:29 +01:00			`z1/z1 \`
core/lib/settings: Generalized Settings Manager to work on any platform This commit moves the Settings Manager from the AVR codebase into the Contiki core library. Any platform that implements the Contiki EEPROM API can now use the Settings Manager's key-value store for storing their persistent configuration info. The Settings Manager is a EEPROM-based key-value store. Keys are 16-bit integers and values may be up to 16,383 bytes long. It is intended to be used to store configuration-related information, like network settings, radio channels, etc. * Robust data format which requires no initialization. * Supports multiple values with the same key. * Data can be appended without erasing EEPROM. * Max size of settings data can be easily increased in the future, as long as it doesn't overlap with application data. The format was inspired by the [OLPC manufacturing data format][]. Since the beginning of EEPROM often contains application-specific information, the best place to store settings is at the end of EEPROM (the "top"). Because we are starting at the end of EEPROM, it makes sense to grow the list of key-value pairs downward, toward the start of EEPROM. Each key-value pair is stored in memory in the following format: Order \| Size \| Name \| Description --------:\|---------:\|--------------\|------------------------------- 0 \| 2 \| `key` \| 16-bit key -2 \| 1 \| `size_check` \| One's-complement of next byte -3 \| 1 or 2 \| `size` \| The size of `value`, in bytes -4 or -5 \| variable \| `value` \| Value associated with `key` The end of the key-value pairs is denoted by the first invalid entry. An invalid entry has any of the following attributes: * The `size_check` byte doesn't match the one's compliment of the `size` byte (or `size_low` byte). * The key has a value of 0x0000. [OLPC manufacturing data format]: http://wiki.laptop.org/go/Manufacturing_data 2012-05-17 18:03:52 +02:00			`settings-example/avr-raven \`
Contiki regression tests, grouped into categories 2012-12-08 22:10:30 +01:00
			`TOOLS=`

			`include ../Makefile.compile-test`