Rockbox
Find a file
Jens Arnold 8831a0a1c6 Postfix for bootbox: charging screen reacts on ON press not release as well.
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@7105 a1c6a512-1295-4272-9138-f99709370657
2005-07-11 19:16:14 +00:00
apps Fixed a long-standing bug in the charging screen. The charging screen froze when OFF was pressed. The intention was to powerdown, but this cannot work on archos, so the charging screen must not react on OFF. Made the charging screen react on the ON press instead of the release for better feedback. Bootbox uses SYS_POWEROFF for powering down. 2005-07-11 19:14:26 +00:00
bootloader iriver bootloader: enable backlight at boot, reset uda1380, warning when low battery, let the user try with USB when the ATA init fails 2005-07-11 14:01:45 +00:00
CVSROOT bootbox is not a module 2005-06-22 20:07:45 +00:00
docs Patch #1232741 by Frederic Devernay - chip8 plugin now playable, and with SCHIP emulation 2005-07-06 18:38:25 +00:00
firmware Replaced some yields with sleep(1) to save battery while paused or 2005-07-11 18:47:47 +00:00
flash Postfix for bootbox: charging screen reacts on ON press not release as well. 2005-07-11 19:16:14 +00:00
fonts New fonts + slight fix to rockbox_default by Antonius Hellman (patch #1228206) 2005-06-30 21:14:09 +00:00
gdb Port A inits for cold-start capability 2003-06-29 21:57:20 +00:00
songdbj javazoom converter, not the tritonus one.. 2005-07-11 15:43:44 +00:00
tools Adapted fwpatcher to patch both H110/H115 and H120/H140 firmwares. Unpatched firmwares are detected by md5sum, and the patched firmware's md5sum is compared to the matching entry, so it should be even more safe than before. 2005-07-09 12:01:18 +00:00
uisimulator Fixed a simulator crash while trying to play a song. Fixed crossfade 2005-07-10 16:33:03 +00:00
www Music on iRiver 2005-06-05 23:19:31 +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!