Rockbox
Find a file
Thomas Martitz b5b2a03ee2 A tiny bit more Sansa Fuze v2 work.
- buttonlight works
 - backlight turns on (quite weak though and no brightness adjustment/backlight off functional)
 - don't share drivers with e200v2/fuzev1 for now as it's not entirely clear how dbop plays into this
 - deactivte scrollwheel as it's messing up the timer setup in kernel-as3525.c indicating the dbop input reading doesn't work well
 - still no working bootloader/no lcd or buttons

git-svn-id: svn://svn.rockbox.org/rockbox/trunk@25225 a1c6a512-1295-4272-9138-f99709370657
2010-03-16 22:38:57 +00:00
apps Updated italian translation. 2010-03-16 22:19:50 +00:00
backdrops Remove svn:executable 2009-12-11 14:50:57 +00:00
bootloader Clip+ : make the bootloader not verbose by default 2010-03-15 11:47:50 +00:00
docs Sansa Clipv2: use similar button driver to Clipv1 2010-03-15 23:01:45 +00:00
firmware A tiny bit more Sansa Fuze v2 work. 2010-03-16 22:38:57 +00:00
flash Simplify powermgmt thread loops so it calls functions turn (no more power_thread_sleep). Do other target-friendly simplifications, generic battery switch handling and split sim-specific code. Whoever can, please verify charging on the Archos Recorder (due to change in the charger duty cycle code). 2008-12-24 16:58:41 +00:00
fonts Rename some glyphs in 08-Atadore font to standard unicode names (part 2 of FS#11082) 2010-03-14 19:45:11 +00:00
gdb Updated our source code header to explicitly mention that we are GPL v2 or 2008-06-28 18:10:04 +00:00
icons kill the release script and build tarball from *everything* in SVN... 2008-03-26 13:12:07 +00:00
manual Add a note to the gigabeat F manual to be in the correct USB mode before installing. 2010-03-13 10:50:39 +00:00
rbutil mkamsboot: update README for Clip+/Fuzev2 2010-03-16 15:24:56 +00:00
tools Fix rbspeex on big endian hosts. 2010-03-14 18:20:18 +00:00
uisimulator UIsimulator: iAudio M3 remote keys add. 2010-03-15 12:51:53 +00:00
utils amsinfo: do not assume library blocks always have the same size 2010-03-14 23:35:01 +00:00
wps Fix wpsbuild to properly generate "-" for theme related settings (to get the default values/no file for filename settings). 2010-02-21 19:10:57 +00:00

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

Build Your Own Rockbox

1. Check out 'rockbox' from SVN (or extract a downloaded archive).

   $ svn co svn://svn.rockbox.org/rockbox/trunk rockbox

     or

   $ tar xjf rockbox.tar.bz2

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

3. Make sure you have sh/arm/m68k-elf-gcc and siblings in the PATH. Make sure
   that you have 'perl' in your PATH too. Your gcc cross compiler needs to be
   a particular version depending on what player you are compiling for. These
   can be acquired with the rockboxdev.sh script in the /tools/ folder of the
   source, or will have been included if you've installed one of the
   toolchains or development environments provided at http://www.rockbox.org/

   $ which sh-elf-gcc
   $ which perl

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. Run 'make' and soon the necessary pieces from the firmware and the apps
   directories have been compiled, linked and scrambled for you.

   $ make
   $ make zip

7. unzip the rockbox.zip on your music player, reboot it and
   *smile*.

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!