forked from len0rd/rockbox
Fork of rockbox tailored for ipod classic
cef17e3d59
This loader is needed to use Rockbox on iBasso DX50/DX90 devices. It replaces /system/bin/MangoPlayer. It expects - the original firmware MangoPlayer as /system/bin/MangoPlayer_original - the chooser.bmp file as /system/chooser.bmp - the rbmissing.bmp file as /system/rbmissing.bmp - the usb.bmp file as /system/usb.bmp - Rockbox in /mnt/sdcard/.rockbox/ (internal device storage accessable via USB) On first boot or if the device is booted with the hold switch engaged (upper, locked position) this loader will let the user choose between Rockbox and the orginal firmware MangoPlayer. It remembers the last choice and will start the choosen player an following boots. In the chooser screen - the device can be powered off with a power button long press. - Rockbox can be startet with the "Next/Fast Forward" button or by touching the right part of the touchscreen. - the orginal firmware MangoPlayer can be startet with the "Previous/Rewind" button or by touching the left part of the touchscreen. If Rockbox can not be found/executed than a "Rockbox is missing" screen will be shown and the orginal firmware MangoPlayer will be started after 30 seconds. This loader will (try to) restart Rockbox or the orginal firmware MangoPlayer if something unexpected happens. This loader can be installed via a customized firmware image (update.img) or manually via the Android Debug Bridge (if you get adbd started on the device). This is a rewrite and code clean up of the original submission, eliminating the need for a custom Android Vold. This loader "knows", when Rockbox has exited due to a USB mass storage connection remounting /mnt/sdcard and acts accordingly, displaying a "USB connection" screen while waiting to restart Rockbox. Change-Id: I2698e173437f9c7aa1ff40649a290220e2ee0439 |
||
|---|---|---|
| android | ||
| apps | ||
| backdrops | ||
| bootloader | ||
| debian | ||
| docs | ||
| firmware | ||
| flash | ||
| fonts | ||
| gdb | ||
| icons | ||
| lib | ||
| manual | ||
| packaging | ||
| rbutil | ||
| tools | ||
| uisimulator | ||
| utils | ||
| wps | ||
| .gitattributes | ||
| .gitignore | ||
__________ __ ___.
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!