rockbox

History

Thomas Orgis 8aa72f07f4 Enhancement of the metronome plugin: - square sine tick and tock sounds (more annoying, more useful;-) - optical indication of tics on display - unification of mode of operation for SWCODEC and HWCODEC (tested on simulator) Both playback and display drawing happen in main loop, always. - operating in two modes now: -- 1. classic dumb metronome --- active when openened as application without file to open --- the usual functionality with tapping and bpm change --- controls indicated on display -- 2. track mode with programmable series of parts --- active when started as viewer for a .tempo file --- differing meters (4/4, 3/4, 6/8, etc.) --- patterns (tick/tock/silence on each beat) --- smooth tempo changes in those tracks This version had lots of testing regarding metronome accuracy, resulting in the realization that PLL A and PLL B differ on the Clip+, causing drift. There is still drift when the timer intervall is too small, so I settled on 2 ms as compromise. This is the final version, after adding documentation and extensive help from Sebastian Leonhardt testing it on slower hardware (YH820), where it works up to 650 actual bpm with display indication. Latest change: Documentation nitpicks. Change-Id: I764c8252526db188352385c5462f9453d882beb9		2015-02-03 22:41:40 +01:00
..
logo	lcd_color/cabbiev2: New iconset in multiple sizes	2011-11-26 16:01:11 +00:00
API
BATTERY-FAQ
BATTERY-FAQ-LIION
CHARGING_ALGORITHM
COMMITTERS	Add myself to committers list	2014-11-18 02:31:24 +01:00
CONTRIBUTING	Update CONTRIBUTING to reflect our switch to git on gerrit.	2012-01-24 13:05:25 +01:00
COPYING
COPYING-MANUAL
CREDITS	Enhancement of the metronome plugin:	2015-02-03 22:41:40 +01:00
gpl-2.0.html	Remove duplicated license file.	2010-09-04 18:50:12 +00:00
HISTORY
KNOWN_ISSUES	Use crc32 of filename to resume tracks	2013-01-02 08:29:38 +01:00
LICENSES
MAINTAINERS
NODO
PLUGIN_API	lcd-common/scroll_engine: Remove unused functions lcd_puts_scroll_style().	2014-01-07 14:13:48 +01:00
profontdoc.txt
README	Update instructions in docs/README to change 'Check out from SVN' to 'Clone from git'	2013-04-24 11:11:38 +01:00
sample.colours
sample.icons
TECH
UISIMULATOR

README

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

Build Your Own Rockbox

1. Clone 'rockbox' from git (or extract a downloaded archive).

   $ git clone git://git.rockbox.org/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!