Rockbox
Find a file
Thom Johansen 3c7278f405 Reworked backlight fading by GPIO based PWM to work for other targets
than H1x0. iPod Nano and 5G backlight fading is enabled. To try for your
device, just define HAVE_BACKLIGHT_PWM_FADING in the relevant
config-xxxx.h file. NOTE: Will break your settings, so save a config
file first.


git-svn-id: svn://svn.rockbox.org/rockbox/trunk@9121 a1c6a512-1295-4272-9138-f99709370657
2006-03-19 17:42:58 +00:00
apps Reworked backlight fading by GPIO based PWM to work for other targets 2006-03-19 17:42:58 +00:00
bootloader Add the target directory tree to the include path, and set the TARGET_TREE macro for the targets that use it 2006-03-07 12:45:45 +00:00
CVSROOT Added manual 2006-02-12 12:58:51 +00:00
docs Add Fredrik Öhrn 2006-03-15 01:34:01 +00:00
firmware Reworked backlight fading by GPIO based PWM to work for other targets 2006-03-19 17:42:58 +00:00
flash Use cvs uclpack for bootbox. 2006-03-11 22:53:03 +00:00
fonts add the Adobe Helvetica font. 2006-02-13 10:56:21 +00:00
gdb Mapped iFP DRAM to 0xc00000 and enabled caching in this area. 2006-02-12 23:16:05 +00:00
manual Improved screenshot courtesy of Mikael Magnusson 2006-03-16 22:42:32 +00:00
songdbj javazoom converter, not the tritonus one.. 2005-07-11 15:43:44 +00:00
tools introducing make gzip, make bzip2 and make help 2006-03-19 06:57:59 +00:00
uisimulator code policed // comments 2006-03-19 06:59:36 +00:00
wps only use the LCD size for bitmap LCDs so that we don't get the WPSes 2006-03-18 21:17:05 +00:00
www Changed from bugs/ to tracker/ 2006-03-18 19:57:16 +00:00

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

Build Your Own Rockbox

1. Check out 'rockbox' from CVS (or extract a downloaded archive). You
   want to check out 'rockbox-devel' instead if you want the simulator
   code too (for trying out things on host before making target tests).

   (For more information about the simulator, read UISIMULATOR.)

   $ cvs -d:pserver:anonymous@www.rockbox.org:/cvsroot/rockbox login 
   $ cvs -z3 -d:pserver:anonymous@www.rockbox.org:/cvsroot/rockbox co rockbox

     or

   $ tar xzf rockbox.tar.gz

2. Create a build directory, preferably in the same directory as the firmware/
   and apps/ directories. This is where all generated files will be written.

   $ cd rockbox
   $ mkdir build
   $ cd build

4. 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 (and a
   few more questions). 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.

   $ ../tools/configure

5. *ploink*. Now you have got a Makefile generated for you.

6. Make sure you have sh-elf-gcc and siblings in the PATH. Make sure that you
   have 'perl' in your PATH too.

   $ which sh-elf-gcc
   $ which perl

7. Run 'make' and soon the necessary pieces from the firmware and the apps
   directories have been compiled, linked and scrambled for you.

   $ make

8. Copy the archos.mod or ajbrec.ajz file to your archos, reboot it and
   *smile*.  Recent Rockbox versions need no reboots, just PLAY a new rockbox
   version and that'll be loaded and replace the currently running version.

   $ mount /dev/sda1 /mnt/archos
   $ cp ajbrec.ajz /mnt/archos
   $ umount /mnt/archos

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 several build
directories and create a setup for each target:

   $ mkdir build-fmrecorder
   $ cd build-fmrecorder
   $ ../tools/configure

   $ mkdir build-player
   $ cd build-player
   $ ../tools/configure

Questions anyone? Ask on the mailing list. We'll be happy to help you!