osd-contiki/cpu/mc1322x
Mariano Alvira 2e331b51e8 Merge remote branch 'libmc1322x/master' into update-libmc1322x
Conflicts:
	cpu/mc1322x/COPYING
2011-02-17 14:41:47 -05:00
..
board remove cvs keywords from cpu/mc1322x 2011-02-17 14:36:55 -05:00
dev remove cvs keywords from cpu/mc1322x 2011-02-17 14:36:55 -05:00
doc Merge remote branch 'libmc1322x/master' into update-libmc1322x 2011-02-17 14:41:47 -05:00
lib Merge remote branch 'libmc1322x/master' into update-libmc1322x 2011-02-17 14:41:47 -05:00
src Merge branch 'libmc13-9f82e068' into update-libmc1322x 2011-02-17 14:39:20 -05:00
tests Merge remote branch 'libmc1322x/master' into update-libmc1322x 2011-02-17 14:41:47 -05:00
tools remove cvs keywords from cpu/mc1322x 2011-02-17 14:36:55 -05:00
.gitignore Merge branch 'libmc13-9f82e068' into update-libmc1322x 2011-02-17 14:39:20 -05:00
clock.c remove cvs keywords from cpu/mc1322x 2011-02-17 14:36:55 -05:00
contiki-crm.c remove cvs keywords from cpu/mc1322x 2011-02-17 14:36:55 -05:00
contiki-maca.c remove cvs keywords from cpu/mc1322x 2011-02-17 14:36:55 -05:00
contiki-maca.h remove cvs keywords from cpu/mc1322x 2011-02-17 14:36:55 -05:00
contiki-mc1322x-conf.h remove cvs keywords from cpu/mc1322x 2011-02-17 14:36:55 -05:00
contiki-misc.c remove cvs keywords from cpu/mc1322x 2011-02-17 14:36:55 -05:00
contiki-uart.c remove cvs keywords from cpu/mc1322x 2011-02-17 14:36:55 -05:00
contiki-uart.h remove cvs keywords from cpu/mc1322x 2011-02-17 14:36:55 -05:00
COPYING Merge remote branch 'libmc1322x/master' into update-libmc1322x 2011-02-17 14:41:47 -05:00
CREDITS initial mc1322x commit 2010-06-09 14:43:22 +00:00
dbg-io.c remove cvs keywords from cpu/mc1322x 2011-02-17 14:36:55 -05:00
debug-uart.c initial mc1322x commit 2010-06-09 14:43:22 +00:00
debug-uart.h initial mc1322x commit 2010-06-09 14:43:22 +00:00
io.h add a dummy io.h for mc13224v 2011-02-08 09:07:54 -05:00
leds-arch.c remove cvs keywords from cpu/mc1322x 2011-02-17 14:36:55 -05:00
Makefile.include Merge branch 'libmc13-9f82e068' into update-libmc1322x 2011-02-17 14:39:20 -05:00
Makefile.mc1322x add proper arm flags and remove Makefile.src as it's not used. 2011-02-08 09:55:50 -05:00
mc1322x.lds add heap and _sbrk to mc13224v 2011-02-08 09:07:23 -05:00
mtarch.h remove cvs keywords from cpu/mc1322x 2011-02-17 14:36:55 -05:00
README Merge branch 'libmc13-9f82e068' into update-libmc1322x 2011-02-17 14:39:20 -05:00
README.subtree initial mc1322x commit 2010-06-09 14:43:22 +00:00
rtimer-arch.c remove cvs keywords from cpu/mc1322x 2011-02-17 14:36:55 -05:00
rtimer-arch.h remove cvs keywords from cpu/mc1322x 2011-02-17 14:36:55 -05:00
slip-uart1.c remove cvs keywords from cpu/mc1322x 2011-02-17 14:36:55 -05:00
TODO initial mc1322x commit 2010-06-09 14:43:22 +00:00
watchdog.c remove cvs keywords from cpu/mc1322x 2011-02-17 14:36:55 -05:00

libmc1322x is a library, build system, test code, and utilities for
using the mc13224v from Freescale.

Getting Started
---------------
$ cd tests
$ make

this will build all the test files in libmc1322x/tests for each board
defined in libmc1322x/board. You will have programs like:

  rftest-tx_redbee-dev.bin
  rftest-tx_redbee-r1.bin

  rftest-rx_redbee-dev.bin
  rftest-rx_redbee-r1.bin

if you only wanted to build binaries for one board you can do:

$ make BOARD=redbee-dev

You can use mc1322x-load.pl in libmc1322x/tools to run your code:

$ ../tools/mc1322x-load.pl -f rftest-tx_redbee-dev.bin


Incorporating libmc1322x into your own code
-------------------------------------------

The best way to incorporate libmc1322x into your code is as a git
submodule:

$ mkdir newproject
$ cd newproject
$ git init

   Initialized empty Git repository in /home/malvira/newproject/.git/

$ git submodule add git://git.devl.org/git/malvira/libmc1322x.git

This will add libmc1322x to your repository. Now to setup the
Makefile:

$ cp libmc1322x/tests/Makefile .

You need to edit the Makefile to point MC1322X to your libmc1322x
submodule:

Change line 1

   MC1322X := ..

to 

   MC1322X := libmc1322x

and edit COBJS and TARGETS accordings. COBJS are all of your common
code for any of your programs. TARGETS are the names of your programs.

For instance, you can have a common routine that prints a welcome
message that is used by two programs a and b. You would add common.o
to COBJS:

   COBJS:= common.o

and your target line would read:

   TARGETS := a b 

COBJS are made for each board --- so it is ok to have board specific
code in there. As an example, tests uses this in tests.c to print the
name of the board in the welcome message. You could also use this to
change your GPIO mappings between boards.