rockbox/firmware
Björn Stenberg f224f0b8e8 Don't free static data :)
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@1181 a1c6a512-1295-4272-9138-f99709370657
2002-06-25 11:29:38 +00:00
..
common 1 byte reads past a sector boundary failed 2002-06-24 07:46:19 +00:00
drivers dac_config() return the wrong error code 2002-06-25 11:22:53 +00:00
include added debug function header file. 2002-06-24 16:00:06 +00:00
malloc
test
API Added some kernel docs 2002-06-04 12:48:08 +00:00
app.lds remove padding to make it link, we're now bigger than least required! 2002-06-17 06:24:22 +00:00
backlight.c non-RTC code wrote to PAIOR instead of PADR 2002-06-25 11:15:33 +00:00
backlight.h First version 2002-06-24 13:48:42 +00:00
chartables.c several charset fixes for the proportional font 2002-06-24 07:37:58 +00:00
CONFIG
config-player.h
config-playerold.h
config-recorder.h Added first RTC functions 2002-06-24 13:23:01 +00:00
config.h moved sounds settings to settings.h, config.h is only for including the 2002-06-19 14:58:35 +00:00
CONTRIBUTING
COPYING First version 2002-06-17 13:54:03 +00:00
CREDITS synced with credits.c 2002-06-20 14:09:39 +00:00
crt0.S New section for reset vectors 2002-05-29 09:12:34 +00:00
debug.c output debugf() nicely for simulator builds too 2002-06-04 22:03:21 +00:00
debug.h output debugf() nicely for simulator builds too 2002-06-04 22:03:21 +00:00
FILES Added include files to tarball 2002-06-17 13:18:30 +00:00
gdb.lds New section for reset vectors 2002-05-29 09:12:34 +00:00
id3.c Don't free static data :) 2002-06-25 11:29:38 +00:00
id3.h Added #define ID3_H 2002-06-24 13:01:27 +00:00
kernel.c Added init_threads function 2002-06-07 14:56:10 +00:00
kernel.h Clarified the mutex code, renamed the NUM_TICK_TASKS macro 2002-06-04 12:47:39 +00:00
Makefile add our "libc header directory" to the include path 2002-06-17 13:20:03 +00:00
mpeg.c Now yields after MPEG_NEED_DATA 2002-06-20 09:18:47 +00:00
mpeg.h
panic.c
panic.h
player.lds use this linker file for player builds 2002-06-17 06:48:56 +00:00
README
rockbox-mode.el
settings.c Added the wps_display to global settings. 2002-06-25 08:40:53 +00:00
settings.h Added the wps_display to global settings. 2002-06-25 08:40:53 +00:00
system.c Exception handler clears and updates the screen now (so one can read the error message) 2002-06-24 11:35:13 +00:00
system.h Changed frequency for Recorder 2002-06-07 10:29:14 +00:00
thread.c Always clear the status register (irq mask) 2002-06-19 06:01:06 +00:00
thread.h Added init_threads function 2002-06-07 14:56:10 +00:00

               __________               __   ___.
     Open      \______   \ ____   ____ |  | _\_ |__   _______  ___
     Source     |       _//  _ \_/ ___\|  |/ /| __ \ /  _ \  \/  /
     Jukebox    |    |   (  <_> )  \___|    < | \_\ (  <_> > <  <
     Firmware   |____|_  /\____/ \___  >__|_ \|___  /\____/__/\_ \
                       \/            \/     \/    \/            \/

Build your own archos.mod.

1. Check out 'firmware' and 'apps' from CVS (or possibly form a downloaded
   archive). You probably want to check out 'tools' too (to get the configure
   script if nothing else) and possibly the 'uisimulator' too (for trying out
   things on host before making target tests).

2. Create your own build directory. This is where all generated files will be
   put.

3. In your build directory, run the 'tools/configure' script and enter what
   target you want to build for and if you want a debug version or not. It'll
   prompt you. The debug version is for making a gdb version out of it. It is
   only useful if you run gdb towards your target Archos.

4. *ploink*. Now you have got a Makefile generated for you. Run 'make' and
   soon the necessary pieces from the firmware and the apps directories have
   been compiled and linked.

5. Copy the archos.mod file to your archos, reboot it and *smile*.

Whenever the tools/configure script gets updated, you can make your makefile
updated too by running 'tools/configure update'

If you want to build for more than one target, just create a new build
directory and create a setup for another target combination in there.

Questions anyone? Take them to the mailing list. We'll be happy to help you
out!