Rockbox
Find a file
Rafaël Carré 5ea1fe614a cpucache_invalidate: use bx reg instead of mov pc, reg to return
Using BX has the effect to set the T bit, so it can return to a thumb
function

With this change, rockbox runs fine on Clipv2 built with -mthumb (for
most files which don't use inline 32 bits ARM assembly)

Some other places use code which change the T bit on armv5 but not on
armv4 so armv4 won't run

See FS#6734

git-svn-id: svn://svn.rockbox.org/rockbox/trunk@26386 a1c6a512-1295-4272-9138-f99709370657
2010-05-29 17:12:42 +00:00
apps Correction to clobber lists of several codec's inline assembly. 2010-05-29 15:00:10 +00:00
backdrops Remove svn:executable 2009-12-11 14:50:57 +00:00
bootloader Generate C file / header for svn version string 2010-05-27 09:41:46 +00:00
docs Generate C file / header for svn version string 2010-05-27 09:41:46 +00:00
firmware cpucache_invalidate: use bx reg instead of mov pc, reg to return 2010-05-29 17:12:42 +00:00
flash Generate C file / header for svn version string 2010-05-27 09:41:46 +00:00
fonts Revert r26008. Fonts in the font pack should at least be able to display English menus. This font can maybe included in a theme bundle. 2010-05-14 12:48:47 +00:00
gdb Generate C file / header for svn version string 2010-05-27 09:41:46 +00:00
icons Revert hotkey bitmaps 2010-05-07 14:46:42 +00:00
manual Correct manual keymaps for plugins recently converted to PLA, and use manual PLA defines for them. 2010-05-29 15:23:22 +00:00
rbutil Fix a warning. 2010-05-27 22:06:16 +00:00
tools Upgrade the ARM eabi toolchain to gcc 4.4.4 2010-05-28 23:41:16 +00:00
uisimulator Generate C file / header for svn version string 2010-05-27 09:41:46 +00:00
utils make the script zip the output 2010-05-29 14:00:55 +00:00
wps Cabbiev2: make the playlist position and playing time info actually show up as planned in the 128x128 colour port. 2010-04-27 23:02:00 +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!