Rockbox
Find a file
2005-06-04 10:19:45 +00:00
apps Recording screen rework: (1) Fixed irregular LED blinking on pause/ armed trigger. All redraw & LED intervals are now generated by the peakmeter_draw_get_button() delay alone, avoiding interference of different frequencies. (2) This also fixes irregular update intervals of the whole recording screen. (3) Code cleanup, smaller binary size. (4) Fixed gain limits (symmetric analog gain increase used mic gain limit, and so did the right analog gain decrease). 2005-06-04 10:19:45 +00:00
bootloader iRiver: The hard drive power is now OFF by default 2005-06-02 21:40:52 +00:00
CVSROOT Added fonts 2005-03-18 12:50:56 +00:00
docs Bagder in version 1.81 of plugin.h: "fprintf() is now fdprintf()" so time to put it in here too :) 2005-06-01 20:35:08 +00:00
firmware (1) Bugfix: create_xing_header() now returns 0 in case of an invalid header template, i.e. when mp3headerinfo() returns false. It used to return a random number, causing all sorts of problems. This was the cause for the end of a recording (still in the buffer) occasionally overwriting the beginning. (2) Some code cleanup. 2005-06-04 09:01:40 +00:00
flash now can compose images with ROMbox, too 2004-12-23 20:15:13 +00:00
fonts I'll commit a working version now, then... 2005-04-15 01:03:00 +00:00
gdb Port A inits for cold-start capability 2003-06-29 21:57:20 +00:00
tools Checksums for bootloader v2 2005-06-02 22:35:50 +00:00
uisimulator Added dummy function and simulator stub. 2005-05-30 06:42:14 +00:00
www Forgot ENDDATE 2005-05-13 08:24:52 +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!