From 6d4c19707ef95942e323cbdc89fbbfdbe45e7cc5 Mon Sep 17 00:00:00 2001 From: Björn Stenberg Date: Mon, 8 Jan 2007 23:52:01 +0000 Subject: Splitting out www git-svn-id: svn://svn.rockbox.org/rockbox/trunk@11952 a1c6a512-1295-4272-9138-f99709370657 --- www/docs/Help-JBR.txt | 81 ---- www/docs/Help-Stu.txt | 62 --- www/docs/Makefile | 83 ---- www/docs/battery-faq.t | 6 - www/docs/color_t.jpg | Bin 1405 -> 0 bytes www/docs/contributing.t | 8 - www/docs/credits.t | 11 - www/docs/custom_wps_format.t | 8 - www/docs/cygwin_sdk.t | 14 - www/docs/datasheets.t | 51 --- www/docs/devicechart.t | 368 ---------------- www/docs/faq.t | 6 - www/docs/features.t | 357 ---------------- www/docs/firsttime.t | 67 --- www/docs/flash.t | 418 ------------------- www/docs/flash/rockbox-flash.jpg | Bin 16430 -> 0 bytes www/docs/flash/rockbox_flash_boot.avi | Bin 1591964 -> 0 bytes www/docs/fmrecorder.jpg | Bin 13254 -> 0 bytes www/docs/fmrecorder_t.jpg | Bin 1602 -> 0 bytes www/docs/how_to_compile.t | 8 - www/docs/index.t | 123 ------ www/docs/lcd_new.gif | Bin 43437 -> 0 bytes www/docs/lcd_new_hw.gif | Bin 41878 -> 0 bytes www/docs/lcd_new_subst.gif | Bin 43437 -> 0 bytes www/docs/lcd_old.gif | Bin 43437 -> 0 bytes www/docs/lcd_old_hw.gif | Bin 41878 -> 0 bytes www/docs/lcd_old_subst.gif | Bin 43437 -> 0 bytes www/docs/license.t | 8 - www/docs/mpeghdr.t | 761 ---------------------------------- www/docs/nano_t.jpg | Bin 1297 -> 0 bytes www/docs/newplayer.jpg | Bin 13526 -> 0 bytes www/docs/newplayer_t.jpg | Bin 1539 -> 0 bytes www/docs/nodo.t | 6 - www/docs/oldplayer.jpg | Bin 12856 -> 0 bytes www/docs/oldplayer_t.jpg | Bin 1537 -> 0 bytes www/docs/ondiofm.jpg | Bin 10190 -> 0 bytes www/docs/ondiofm_t.jpg | Bin 1463 -> 0 bytes www/docs/ondiosp.jpg | Bin 11085 -> 0 bytes www/docs/ondiosp_t.jpg | Bin 1450 -> 0 bytes www/docs/patch.t | 99 ----- www/docs/ports.t | 230 ---------- www/docs/recorder.jpg | Bin 13911 -> 0 bytes www/docs/recorder_t.jpg | Bin 1556 -> 0 bytes www/docs/repairbattery.t | 53 --- www/docs/repairlcd.t | 125 ------ www/docs/rocklatin.t | 95 ----- www/docs/rvf.t | 117 ------ www/docs/solderjoints.jpg | Bin 59916 -> 0 bytes www/docs/solderjoints2.jpg | Bin 81739 -> 0 bytes www/docs/solderjoints2_t.jpg | Bin 9141 -> 0 bytes www/docs/solderjoints_t.jpg | Bin 13878 -> 0 bytes www/docs/tools.t | 407 ------------------ 52 files changed, 3572 deletions(-) delete mode 100644 www/docs/Help-JBR.txt delete mode 100644 www/docs/Help-Stu.txt delete mode 100644 www/docs/Makefile delete mode 100644 www/docs/battery-faq.t delete mode 100644 www/docs/color_t.jpg delete mode 100644 www/docs/contributing.t delete mode 100644 www/docs/credits.t delete mode 100644 www/docs/custom_wps_format.t delete mode 100644 www/docs/cygwin_sdk.t delete mode 100644 www/docs/datasheets.t delete mode 100644 www/docs/devicechart.t delete mode 100644 www/docs/faq.t delete mode 100644 www/docs/features.t delete mode 100644 www/docs/firsttime.t delete mode 100644 www/docs/flash.t delete mode 100644 www/docs/flash/rockbox-flash.jpg delete mode 100644 www/docs/flash/rockbox_flash_boot.avi delete mode 100644 www/docs/fmrecorder.jpg delete mode 100644 www/docs/fmrecorder_t.jpg delete mode 100644 www/docs/how_to_compile.t delete mode 100644 www/docs/index.t delete mode 100644 www/docs/lcd_new.gif delete mode 100644 www/docs/lcd_new_hw.gif delete mode 100644 www/docs/lcd_new_subst.gif delete mode 100644 www/docs/lcd_old.gif delete mode 100644 www/docs/lcd_old_hw.gif delete mode 100644 www/docs/lcd_old_subst.gif delete mode 100644 www/docs/license.t delete mode 100644 www/docs/mpeghdr.t delete mode 100644 www/docs/nano_t.jpg delete mode 100644 www/docs/newplayer.jpg delete mode 100644 www/docs/newplayer_t.jpg delete mode 100644 www/docs/nodo.t delete mode 100644 www/docs/oldplayer.jpg delete mode 100644 www/docs/oldplayer_t.jpg delete mode 100644 www/docs/ondiofm.jpg delete mode 100644 www/docs/ondiofm_t.jpg delete mode 100755 www/docs/ondiosp.jpg delete mode 100755 www/docs/ondiosp_t.jpg delete mode 100644 www/docs/patch.t delete mode 100755 www/docs/ports.t delete mode 100644 www/docs/recorder.jpg delete mode 100644 www/docs/recorder_t.jpg delete mode 100644 www/docs/repairbattery.t delete mode 100644 www/docs/repairlcd.t delete mode 100644 www/docs/rocklatin.t delete mode 100644 www/docs/rvf.t delete mode 100644 www/docs/solderjoints.jpg delete mode 100644 www/docs/solderjoints2.jpg delete mode 100644 www/docs/solderjoints2_t.jpg delete mode 100644 www/docs/solderjoints_t.jpg delete mode 100644 www/docs/tools.t (limited to 'www/docs') diff --git a/www/docs/Help-JBR.txt b/www/docs/Help-JBR.txt deleted file mode 100644 index 6f674661fc..0000000000 --- a/www/docs/Help-JBR.txt +++ /dev/null @@ -1,81 +0,0 @@ -ROCKBOX "QUICK HELP" FOR JUKEBOX RECORDERS -A "How to/Where to" short section can be found at the end of this file. - -GENERAL KEY CONTROL -OFF: Quick press: End current function - Hold: Switch off the Jukebox (not advised while an MP3 is playing, i.e. without first stopping playback) - -DIRECTORY BROWSING KEY CONTROLS -UP/DOWN: Go to previous/next item in list. If you are on the first/last entry, the cursor will wrap to the last/first entry. -ON+UP/DOWN: Move one page up/down in the list. -LEFT: Go to the parent directory. -PLAY/RIGHT: Execute an action. Depending on the file type, that action may vary. -ON: If there is an MP3 playing, return to the While Playing Screen (WPS) -ON+PLAY: Enter the File Menu -F1: Switch to/leave the Main Menu -F2: Switch to/leave the Browse/play Quick Menu -F3: Switch to/leave the Display Quick Menu - -NAVIGATING THROUGH THE MENU -UP: Move up in the menu. Inside a setting, increases the value or chooses next option -DOWN: Move down in the menu. Inside a setting, decreases the value or chooses previous option -PLAY/RIGHT: Select option -OFF/LEFT: Exit menu, setting or move to parent menu - -WPS KEY CONTROLS (from the "While Playing" Sscreen) -UP/DOWN: Volume up/down -LEFT: Quick press: Go to beginning of track, or if pressed while in the first seconds of a track, go to previous track - Hold: Rewind in track -RIGHT: Quick press: Go to next track. - Hold: Fast-forward in track. -PLAY: Toggle play/pause -ON: Quick press: Go to file browser - Hold: Show pitch setting screen -OFF: Quick press: Stop playback - Hold: Switch off the Jukebox (not advised from this screen, i.e. without first stopping playback) -F1: Go to Main menu -F2: Toggle Play/browse quick menu -F3: Toggle Display quick menu -F1+DOWN: Key lock on/off (Note: The OFF key is always active) -F1+PLAY: Mute on/off -F1+ON: Enter ID3 viewer - -RECORDING KEY CONTROLS (from the "While Recording" Screen) -LEFT: Decrease Gain -RIGHT: Increase Gain -PLAY: Start recording. -OFF: Quick press: Exit Recording Screen. If Recording a file, stop recording. - Hold: Switch off the Jukebox (not advised from this screen, i.e. without first stopping recording) -F1: Open Recording Settings screen -F2: Quick menu for Recording settings. - A quick press will leave the screen up (press F2 again to exit), - holding F2 will show the screen which will close when you release the key -F3: Quick menu for source setting. - Quick/hold works as for F2. - -FILE MENU (entered by pressing ON+PLAY while pointing to a file in a directory) -This menu shows the next options: -QUEUE (only if a song is playing already): Rockbox can enqueue up to 100 files. This function needs a folder called .rockbox to save the queue file there. -RENAME: This function lets the user modify a file name. To move the cursor backward and forward in the newname field use ON+LEFT/RIGHT -DELETE: Rockbox can only delete files, not folders. Rockbox will ask for confirmation before deleting a file. -UPDATE VBR FILE: Scan the VBR file and update/create the Xing header. The Xing header contains information about the VBR stream, to calculate average bit rate and to more accurately fw/rew in the stream. - -SUPPORTED FILE FORMATS -Directory: The browser enters that directory -.mp3 Rockbox takes you to the WPS and starts playing the file -.m3u Rockbox loads the playlist and starts playing the first file -.ajz ROLO will load the new firmware -.wps The new WPS display configuration will be loaded -.lng That language will replace the current one -.txt You will read the text file using Rockbox text viewer -.cfg The settings file will be loaded -.fnt This font will replace the current one - -??? HOW TO/WHERE TO ??? -LOCK/UNLOCK KEYS: While playing an MP3 press F1+DOWN -QUEUE a file: While playing an MP3 and browsing directories press ON+PLAY to open the File Menu then select QUEUE -SEE ID3 INFO: While playing an MP3 press F1+ON or use the Main Menu (Show ID3 Info) -LEAVE THE ID3 INFO DISPLAY: "Quick press" the OFF key -BOOKMARK A TRACK: This is not standard yet, you have to use a patched version of Rockbox (but that should come soon...) -CREATE A PLAYLIST OF A DIRECTORY TREE: While inside this directory -> Main Menu (F1) -> Create playlist. The resulting file is in the upper level directory. - diff --git a/www/docs/Help-Stu.txt b/www/docs/Help-Stu.txt deleted file mode 100644 index 95e493b633..0000000000 --- a/www/docs/Help-Stu.txt +++ /dev/null @@ -1,62 +0,0 @@ -ROCKBOX "QUICK HELP" FOR JUKEBOX STUDIO/PLAYERS -A "How to/Where to" short section can be found at the end of this file. - -GENERAL KEY CONTROL -STOP: Quick press: End current function - Hold: Switch off the Jukebox (not advised while an MP3 is playing, i.e. without first stopping playback) - -DIRECTORY BROWSING KEY CONTROLS -LEFT/RIGHT: Go to previous/next item in list. If you are on the first/last entry, the cursor will wrap to the last/first entry. -STOP: Go to the parent directory. -PLAY: Execute an action. Depending on the file type, that action may vary. -ON: If there is an MP3 playing, return to the While Playing Screen (WPS) -ON+PLAY: Enter the File Menu -MENU: Switch to the Main Menu - -NAVIGATING THROUGH THE MENU -LEFT: Select previous option in the menu. Inside a setting, decrease the value or choose previous option -RIGHT: Select next option in the menu. Inside a setting increase the value or choose next option -PLAY: Select item -STOP: Exit menu, setting, or move to parent menu. - -WPS KEY CONTROLS (from the "While Playing" Sscreen) -MENU+RIGHT: Increase volume -MENU+LEFT: Decrease volume -LEFT: Quick press: Go to beginning of track, or if pressed while in the first seconds of a track, go to previous track - Hold: Rewind in track -RIGHT: Quick press: Go to next track. - Hold: Fast-forward in track. -PLAY: Toggle play/pause -ON: Quick press: Go to file browser -STOP: Quick press: Stop playback - Hold: Switch off the Jukebox (not advised from this screen, i.e. without first stopping playback) -MENU: Go to Main menu -MENU+STOP: Key lock on/off (Note: The OFF key is always active) -MENU+PLAY: Mute on/off -MENU+ON: Enter ID3 viewer - -FILE MENU (entered by pressing ON+PLAY while pointing to a file in a directory) -This menu shows the next options: -QUEUE (only if a song is playing already): Rockbox can enqueue up to 100 files. This function needs a folder called .rockbox to save the queue file there. -RENAME: This function lets the user modify a file name. To move the cursor backward and forward in the newname field use ON+LEFT/RIGHT -DELETE: Rockbox can only delete files, not folders. Rockbox will ask for confirmation before deleting a file. -UPDATE VBR FILE: Scan the VBR file and update/create the Xing header. The Xing header contains information about the VBR stream, to calculate average bit rate and to more accurately fw/rew in the stream. - -SUPPORTED FILE FORMATS -Directory: The browser enters that directory -.mp3 Rockbox takes you to the WPS and starts playing the file -.m3u Rockbox loads the playlist and starts playing the first file -.mod ROLO will load the new firmware -.wps The new WPS display configuration will be loaded -.lng That language will replace the current one -.txt You will read the text file using Rockbox text viewer -.cfg The settings file will be loaded - -??? HOW TO/WHERE TO ??? -LOCK/UNLOCK KEYS: While playing an MP3 press MENU+STOP -QUEUE a file: While playing an MP3 and browsing directories press ON+PLAY to open the File Menu then select QUEUE -SEE ID3 INFO: While playing an MP3 press MENU+ON or use the Main Menu (Show ID3 Info) -LEAVE THE ID3 INFO DISPLAY: "Quick press" the STOP key -BOOKMARK A TRACK: This is not standard yet, you have to use a separate patched version of Rockbox (but that should come soon...) -CREATE A PLAYLIST OF A DIRECTORY TREE: While inside this directory -> Main Menu (MENU) -> Create playlist. The resulting file is in the upper level directory. - diff --git a/www/docs/Makefile b/www/docs/Makefile deleted file mode 100644 index dd66652a8e..0000000000 --- a/www/docs/Makefile +++ /dev/null @@ -1,83 +0,0 @@ -ACTION=@echo preprocessing $@; rm -f $@; $(HOME)/bin/fcpp -WWW -I.. -Uunix -H -C -V -P -LL >$@ - - -SRC := $(wildcard *.t) -OBJS := $(SRC:%.t=%.html) - -FAQ2HTML = ../faq2html.pl -TXT2HTML = ../txt2html.pl - -# This is correct. It does point to ../../docs but we need a different -# name so that the directories don't collide. -DOCS = ../docs_ - -all: $(OBJS) - -faq.raw: $(DOCS)/FAQ $(FAQ2HTML) - $(FAQ2HTML) < $< > $@ - -faq.html: faq.t faq.raw $(FAQ2HTML) - $(ACTION) $< - -nodo.raw: $(DOCS)/NODO $(FAQ2HTML) - $(FAQ2HTML) < $< > $@ - -nodo.html: nodo.t nodo.raw $(FAQ2HTML) - $(ACTION) $< - -battery-faq.raw: $(DOCS)/BATTERY-FAQ $(FAQ2HTML) - $(FAQ2HTML) < $< > $@ - -battery-faq.html: battery-faq.t battery-faq.raw $(FAQ2HTML) - $(ACTION) $< - -battery-faq-liion.raw: $(DOCS)/BATTERY-FAQ-LIION $(FAQ2HTML) - $(FAQ2HTML) < $< > $@ - -battery-faq-liion.html: battery-faq-liion.t battery-faq-liion.raw $(FAQ2HTML) - $(ACTION) $< - -contributing.raw: $(DOCS)/CONTRIBUTING $(TXT2HTML) - $(TXT2HTML) < $< > $@ - -contributing.html: contributing.t contributing.raw $(TXT2HTML) - $(ACTION) $< - -custom_wps_format.raw: $(DOCS)/CUSTOM_WPS_FORMAT $(TXT2HTML) - $(TXT2HTML) < $< > $@ - -custom_wps_format.html: custom_wps_format.t custom_wps_format.raw $(TXT2HTML) - $(ACTION) $< - -custom_cfg_format.raw: $(DOCS)/CUSTOM_CFG_FORMAT $(TXT2HTML) - $(TXT2HTML) < $< > $@ - -custom_cfg_format.html: custom_cfg_format.t custom_cfg_format.raw $(TXT2HTML) - $(ACTION) $< - -how_to_compile.raw: $(DOCS)/README $(TXT2HTML) - $(TXT2HTML) < $< > $@ - -how_to_compile.html: how_to_compile.t how_to_compile.raw $(TXT2HTML) - $(ACTION) $< - -uisimulator.raw: $(DOCS)/UISIMULATOR $(TXT2HTML) - $(TXT2HTML) < $< > $@ - -uisimulator.html: uisimulator.t uisimulator.raw $(TXT2HTML) - $(ACTION) $< - -credits.raw: $(DOCS)/CREDITS $(TXT2HTML) - egrep -v '^( |People that have|$$)' $< | awk '{ print $$0 "
" }' > $@ - -credits.html: credits.t credits.raw $(TXT2HTML) - $(ACTION) $< - -license.raw: $(DOCS)/COPYING $(TXT2HTML) - $(TXT2HTML) < $< > $@ - -license.html: license.t license.raw $(TXT2HTML) - $(ACTION) $< - -%.html : %.t - $(ACTION) $< diff --git a/www/docs/battery-faq.t b/www/docs/battery-faq.t deleted file mode 100644 index 7f7446fd3e..0000000000 --- a/www/docs/battery-faq.t +++ /dev/null @@ -1,6 +0,0 @@ -#define _PAGE_ FAQ - Frequently Asked Battery Questions -#include "head.t" - -#include "battery-faq.raw" - -#include "foot.t" diff --git a/www/docs/color_t.jpg b/www/docs/color_t.jpg deleted file mode 100644 index d6689b6df3..0000000000 Binary files a/www/docs/color_t.jpg and /dev/null differ diff --git a/www/docs/contributing.t b/www/docs/contributing.t deleted file mode 100644 index f6cbc1a69a..0000000000 --- a/www/docs/contributing.t +++ /dev/null @@ -1,8 +0,0 @@ -#define _PAGE_ Contributing to Rockbox -#include "head.t" - -
-#include "contributing.raw"
-
- -#include "foot.t" diff --git a/www/docs/credits.t b/www/docs/credits.t deleted file mode 100644 index e084978f57..0000000000 --- a/www/docs/credits.t +++ /dev/null @@ -1,11 +0,0 @@ -#define _PAGE_ The Heroes of Rockbox -#include "head.t" - -

- People that have contributed to the project, one way or another. Friends! -

- -#include "credits.raw" - - -#include "foot.t" diff --git a/www/docs/custom_wps_format.t b/www/docs/custom_wps_format.t deleted file mode 100644 index 6abeeef7d3..0000000000 --- a/www/docs/custom_wps_format.t +++ /dev/null @@ -1,8 +0,0 @@ -#define _PAGE_ Configuring the Player WPS -#include "head.t" - -

-#include "custom_wps_format.raw"
-
- -#include "foot.t" diff --git a/www/docs/cygwin_sdk.t b/www/docs/cygwin_sdk.t deleted file mode 100644 index 2533995842..0000000000 --- a/www/docs/cygwin_sdk.t +++ /dev/null @@ -1,14 +0,0 @@ -#define _PAGE_ Setting up a cygwin Rockbox development environment -#include "head.t" - -

- This page has been replaced. Try one of these instead: - -

- -CygwinDevelopment -
-CrossCompiler - -#include "foot.t" diff --git a/www/docs/datasheets.t b/www/docs/datasheets.t deleted file mode 100644 index 5076b7cbe2..0000000000 --- a/www/docs/datasheets.t +++ /dev/null @@ -1,51 +0,0 @@ -#define _PAGE_ Useful data sheets -#include "head.t" - -

All in PDF format. - -

General docs

- - - -

Player specific

- - -

Recorder specific

- - - -

FM Recorder specific

- - -#include "foot.t" diff --git a/www/docs/devicechart.t b/www/docs/devicechart.t deleted file mode 100644 index 3e4a6e68ca..0000000000 --- a/www/docs/devicechart.t +++ /dev/null @@ -1,368 +0,0 @@ -#define _PAGE_ Devices and features -#include "head.t" - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  -
Old Player - 		-
Player/Studio - 		-
Old Recorder - (1) - 		-
Recorder - 		-
FM Recorder - 		-
V2 Recorder - (4) - 		-
Ondio FM - 		-
Ondio SP - 		-
iRiver H120 - 		-
iRiver H140
- (5) -
USB1.11.11.12.02.02.01.11.12.02.0
Bumper ColorsBlueBlueBlue or BlackBlue or BlackBlueBlueBlue-violetBlue-violetnonenone
S/PDIFNoNoIn+OutIn+OutInInNoNoOptical In+OutOptical In+Out
Separate Line OutYesYesNoNoNoNoNoNoYesYes
Remote controlYesYesYesYesNoNoNoNoYes with LCDYes with LCD
RecordingNoNoYesYesYesYesYesNoYesYes
LCD TypeCharacter 11x2 (2)Character 11x2Bitmap 112x64Bitmap 112x64Bitmap 112x64Bitmap 112x64Bitmap 112x64Bitmap 112x64Bitmap 160x128Bitmap 160x128
LCD size??30x24mm30x24mm30x24mm30x24mm30x24mm30x24mm39x31mm39x31mm
Real Time ClockNoNoYesYesYesYesNoNoNoNo
Buttons6610101010664 + "joystick"4 + "joystick"
Alarm wake-upNoNoNoNoYesYesNoNoNoNo
FM RadioNoNoNoNoYesNo (3)YesNo87.5 - 108 MHz87.5 - 108 MHz
RAM (MB)222222223232
MP3 decoderMAS3507D / DAC3550AMAS3507D / DAC3550AMAS3587FMAS3587FMAS3587FMAS3587FMAS3587FMAS3539Fsoftwaresoftware
Charging ctrlHardwareHardwareSoftwareSoftwareHardwareHardwarenonoHardwareHardware
Charge via USBNoNoNoNoYesYesPowerPowerNo (6)No (6)
Hard drive poweroffNoNoYesYesNoNon.a.n.a.YesYes
CPUSH7034 12 MHzSH7034 12 MHzSH7034 11.0592 MHzSH7034 11.0592 MHzSH7034 11.0592 MHzSH7034 11.0592 MHzSH7034 12 MHzSH7034 12 MHzColdfire 5249 11 - 140 MHzColdfire 5249 11 - 140 MHz
Battery typeNiMH (Type AA)NiMH (Type AA)NiMH (Type AA)NiMH (Type AA)LiIon (Custom)LiIon (Custom)3*AAA3*AAALiIon PolymerLiIon Polymer
Charger spec9-12V 600mA center +9-12V 600mA center +9-12V 600mA center +9-12V 600mA center +6V 700mA center +6V 700mA center +no chargerno charger350mA 5 volt center +350mA 5 volt center +
Dimensions115x83x34 mm (4.5"x3.2"x1.3")115x83x34 mm (4.5"x3.2"x1.3")115x83x34 mm (4.5"x3.2"x1.3")115x83x34 mm (4.5"x3.2"x1.3")113x79x30 mm (4.45"x3.11"x1.18")113x79x30 mm (4.45"x3.11"x1.18")81x47x25 mm (3.1"x1.8"x0.9")81x47x25 mm (3.1"x1.8"x0.9")105x60x18 mm (4.1"x2.4"x0.7")105x60x22 mm (4.1"x2.4"x0.9")
Weight340 g (12 oz)340 g (12 oz)350 g (12.3 oz)350 g (12.3 oz)290 g (10.23 oz)290 g (10.23 oz)60 g (2.1 oz)60 g (2.1 oz)160g (5.6 oz)172g (6.0 oz)
USB ConnectorA maleA maleA maleA malemini B femalemini B femalemini B femalemini B femalemini B femalemini B female
"Ear" Positiontoptoptoptopleft sideleft sidetop lefttop lefttop lefttop left
Storage6 GB 2.5"6-20 GB 2.5"6-15 GB 2.5"20 GB 2.5"20 GB 2.5"20 GB 2.5"128 MB + MMC128 MB + MMC20 GB 1.8"40 GB 1.8"
-

- - (1) It is hard to tell if the recorder is old, but - the Rec6 and Rec10 are old. The Rec15 seems to be available in both new and - old versions. - -
(2) The old player has a limited LCD with no - support for double line height and only four user definable characters - instead of eight. - -
(3) The early V2 models were in fact FM - Recorders in disguise, so they had the FM radio still mounted. - -
(4) The picture shows an FM Recorder, but - they look exactly the same, apart from the printed text. - -
(5) The picture shows an iRiver H120, but - they look exactly the same, apart from the printed text. - -
(6) There is an adapter available for - charging from your host's USB cable, but that is a cable that splits the USB - and power and uses the iRiver's standard charging plug. It is not charging - via the music player's USB. - - -#include "foot.t" diff --git a/www/docs/faq.t b/www/docs/faq.t deleted file mode 100644 index 387961a4af..0000000000 --- a/www/docs/faq.t +++ /dev/null @@ -1,6 +0,0 @@ -#define _PAGE_ FAQ - Frequently Asked Questions -#include "head.t" - -#include "faq.raw" - -#include "foot.t" diff --git a/www/docs/features.t b/www/docs/features.t deleted file mode 100644 index 77c8e92d6b..0000000000 --- a/www/docs/features.t +++ /dev/null @@ -1,357 +0,0 @@ -#define _PAGE_ Firmware Feature Comparison Chart -#include "head.t" - -#define NAME -#define ENAME -#define TD -#define ETD -#define EFEAT - -#define YES Yes ETD -#define PARTLY Partly ETD -#define NO No ETD -#define BADYES Yes ETD -#define GOODNO No ETD -#define UNKNOWN TD ? ETD -#define NA TD N/A ETD - -

- Moved here: - www.rockbox.org/twiki/bin/view/Main/FeatureComparison - -#if 0 - -

This chart compares Rockbox with the original firmwares as shipped by the - manufacturers of the players. The Rockbox column may specify features only - available in CVS and daily builds. - -

- - - - - - - - - -NAME ID3v1 and ID3v2 support ENAME -YES -TD ID3v1 ETD -YES -EFEAT - -NAME Background noise during playback ENAME -GOODNO -BADYES -GOODNO -EFEAT - -NAME Mid-track resume ENAME -YES -NO -YES -EFEAT - -NAME Mid-playlist resume ENAME -YES -NO -UNKNOWN -EFEAT - -NAME Resumed playlist order ENAME -YES -NO -UNKNOWN -EFEAT - -NAME Battery lifetime ENAME -TD Longer ETD -TD Long ETD -TD Long ETD -EFEAT - -NAME Battery time indicator ENAME -YES -NO -NO -EFEAT - -NAME Customizable font (Recorder) ENAME -YES -NO -NO -EFEAT - -NAME Customizable screen info when playing songs ENAME -YES -NO -NO -EFEAT - -NAME USB attach/detach without reboot ENAME -YES -NO -YES -EFEAT - -NAME Can load another firmware without rebooting ENAME -YES -NO -NO -EFEAT - -NAME Playlist load speed, songs/sec ENAME -TD 3000 - 4000 ETD -TD 15 - 20 ETD -TD 30 - 40 ETD -EFEAT - -NAME Max number of songs in a playlist ENAME -TD 20 000 ETD -TD 999 ETD -UNKNOWN -EFEAT - -NAME Supports bad path prefixes in playlists ENAME -YES -YES -UNKNOWN -EFEAT - -NAME Open source/development process ENAME -YES -NO -NO -EFEAT - -NAME Corrects reported bugs ENAME -YES -NO -NO -EFEAT - -NAME Automatic Volume Control (Recorder) ENAME -YES -NO -NO -EFEAT - -NAME Pitch control (Recorder) ENAME -YES -NO -NO -EFEAT - -NAME Text File Reader ENAME -YES -YES -YES -EFEAT - -NAME Games (Recorder) ENAME -TD 8 ETD -NO -NO -EFEAT - -NAME Games (Player) ENAME -TD 2 ETD -NO -NA -EFEAT - -NAME File Delete & Rename ENAME -YES -YES -
FeatureRockboxArchosiRiver h1x0
Partly (delete)ETD -EFEAT - -NAME Playlist Building ENAME -YES -YES -NO -EFEAT - -NAME Recording (Recorder) ENAME -YES -YES -YES -EFEAT - -NAME Generates XING VBR header when recording ENAME -YES -YES -UNKNOWN -EFEAT - -NAME High Resolution Volume Control ENAME -YES -NO -YES -EFEAT - -NAME Deep discharge option (Recorder) ENAME -YES -NO -NO -EFEAT - -NAME Customizable backlight timeout ENAME -YES -YES -YES -EFEAT - -NAME Backlight-on when charging option ENAME -YES -NO -YES -EFEAT - -NAME Queue function ENAME -YES -YES - -EFEAT - -NAME Supports the XING header ENAME -YES -YES -UNKNOWN -EFEAT - -NAME Supports the VBRI header ENAME -PARTLY -YES -UNKNOWN -EFEAT - -NAME Max number of files in a dir ENAME -TD 10 000 ETD -TD 999 ETD -UNKNOWN -EFEAT - -NAME Adjustable scroll speed ENAME -YES -NO -YES -EFEAT - -NAME Screensaver style demos (Recorder) ENAME -YES -NO -NO -EFEAT - -NAME Variable step / accelerating ffwd and rwd ENAME -YES -NO -NO -EFEAT - -NAME Visual Progress Bar ENAME -YES -NO -YES -EFEAT - -NAME Select/Load configs ENAME -YES -NO -NO -EFEAT - -NAME Sleep timer ENAME -YES -NO -YES -EFEAT - -NAME Easy User Interface ENAME -YES -NO -NO -EFEAT - -NAME Remote Control Controllable ENAME -YES -YES -YES -EFEAT - -NAME ISO8859-1 font support (Player) ENAME -YES -NO -NA -EFEAT - -NAME Queue songs to play next ENAME -YES -YES -YES -EFEAT - -NAME Bookmark positions in songs ENAME -YES -NO -NO -EFEAT - -NAME Number of available languages ENAME -TD 24 ETD -TD 3 ETD -UNKNOWN -EFEAT - -NAME Accurate VBR bitrate display ENAME -YES -NO -NO -EFEAT - -NAME FM Tuner support (FM Recorder) ENAME -YES -YES -YES -EFEAT - -NAME FF/FR with sound ENAME -NO -YES -UNKNOWN -EFEAT - -NAME Pre-Recording (Recorders) ENAME -YES -YES -UNKNOWN -EFEAT - -NAME Video Playback with sound (Recorders) ENAME -YES -NO -NO -EFEAT - -NAME Boot Time from Flash (in seconds) ENAME -TD 4 ETD -TD 12 ETD -TD 13 ETD -EFEAT - -NAME Speaking Menus Support ENAME -YES -NO -NO -EFEAT - -
- -

- Wrong facts? Mail rockbox@cool.haxx.se now! - -#endif - -#include "foot.t" diff --git a/www/docs/firsttime.t b/www/docs/firsttime.t deleted file mode 100644 index 677d4e043b..0000000000 --- a/www/docs/firsttime.t +++ /dev/null @@ -1,67 +0,0 @@ -#define _PAGE_ First Look at Rockbox -#include "head.t" - -

First Time Guide to Rockbox Development

-

- Welcome to our humble project. -

- In order to get your hands dirty as quickly and smoothly as possible, here -follows our suggest approach! - -

Join the Rockbox Community

-

- Mail: We have a very active developers mailing list no -serious Rockbox freak can live without. -

- IRC: There's always a bunch of friendly and helpful people around in the - IRC channel. - -

Setup Your Environment

- You need a cross-compiler and linker to build the code. Pick one of these: -

- -

Get The Source

-

- Get a fresh source to build Rockbox from. We usually recommend you get the -sources fresh from the CVS repo (How to use CVS), but -you can also get a daily tarball or even the latest released source package. - -

Build Rockbox

-

- Build rockbox using your aquired sources! If you're using Linux or the -suggested cygwin approach, read How to compile -Rockbox. -

- Also note that we have put a whole lot of effort in writing simulators so -that you can build, run and try code on your host PC before you build and -download your target version. This of course requires a working compiler for -your native system. - -

Change Rockbox

-

- Before you change any code, make sure to read the contributing information if you want to have any hope of having your changes accepted. -

- Now, you fixed any bugs? You added any features? Then make a -patch and head over to the patch-tracker -and submit it. Of course, you can also check the open -bugreports and jump in and fix one of them (or possibly submit -a new bug report. - -

- Regularly checking the open feature-requests -gives a picture of what people want to see happen and what is left to add... - -

- You'll be better off with a sourceforge account for most bugreport and -feature-request work. - -#include "foot.t" diff --git a/www/docs/flash.t b/www/docs/flash.t deleted file mode 100644 index 118940fe1c..0000000000 --- a/www/docs/flash.t +++ /dev/null @@ -1,418 +0,0 @@ -#define _PAGE_ Rockbox in Flash - FAQ and User Manual -#include "head.t" -

-by Jörg Hohensohn aka [IDC]Dragon -

-1. Introduction
-2. Method
-3. Risks
-4. Requirements
-5. Flashing procedure
-6. Bringing in a current or personal build of Rockbox
-7. Known issues and limitations
-8. Movies and images
- - -

1. Introduction

-

-Flashing -in the sense used here and elsewhere in regard to Rockbox means -reprogramming the flash memory of the Archos unit. Flash memory -(sometimes called "Flash ROM") is a type of nonvolatile -memory that can be erased and reprogrammed in-circuit. It is a -variation of electrically erasable programmable read-only memory -(EEPROM). -

-

-When -you bought your Archos, it came with the Archos firmware flashed. -Now, you can replace the built-in software with Rockbox. -

-

-Terminology used in the following:
-Firmware means the flash ROM content as a whole.
-Image means one operating software started from there. -

-

-By -reprogramming the firmware, we can boot much faster. Archos has a -pathetic boot loader, versus the boot time for Rockbox is much faster -than the disk spinup, in fact it has to wait for the disk. Your boot -time will be as quick as a disk spinup (e.g. 4 seconds from powerup -until resuming playback). -

- -

2. Method

-

-The -replaced firmware will host a bootloader and 2 images. This possible -by compression. The first is the "permanent" backup, not to -be changed any more. The second is the default one to be started, the -first is only used when you hold the F1 key (will be Menu for recorders) -during start. Like -supplied here, the first image is the original Archos firmware, the -second is a current build of Rockbox. This second image is meant to -be reprogrammed, it can contain anything you like, if you prefer, you -can program the Archos firmware to there, too. -

-

-There are two programming tools supplied: -

-
    -
  • - The - first one is called "firmware_flash.rock" and is used to - program the whole flash with a new content. You can also use it to - revert back to the original firmware you've hopefully backup-ed. In - the ideal case, you'll need this tool only once. You can view this - as "formatting" the flash with the desired image - structure. -
    • -
  • - The - second one is called "rockbox_flash.rock" and is used to - reprogram only the second image. It won't touch any other byte, - should be safe to fool around with. If the programmed firmware is - inoperational, you can still use the F1 start with the Archos - firmware and Rockbox booted from disk to try better. -
    • -
-

-More technical details will be provided in the future, as well as non-user -tools. There's an authoring tool which composed the firmware file with the -bootloader and the 2 images, the bootloader project, the plugin sources, and -the tools for the UART boot feature: a monitor program for the box and a PC -tool to drive it. Feel free to review the -sources - for all of it, but be careful when fooling around with powerful toys! -

- -

3. Risks

-

-Well, -is it dangerous? Yes, certainly, like programming a mainboard BIOS, -CD/DVD drive firmware, mobile phone, etc. If the power fails, your -chip breaks while programming or most of all the programming software -malfunctions, you'll have a dead box. We take no responsibility of -any kind, you do that at your own risk. However, we tried as -carefully as possible to bulletproof this code. The new firmware file -is completely read before it starts programming, there are a lot of -sanity checks. If any fails, it will not program. Before releasing -this, we have checked the flow with exactly these files supplied -here, starting from the original firmware in flash. It worked -reliably, there's no reason why such low level code should behave -different on your box. -

-

-There's -one ultimate safety net to bring back boxes with even completely -garbled flash content: the UART boot mod, which in turn requires the -serial mod. It can bring the dead back to life, with that it's -possible to reflash independently from the outside, even if the flash -is completely erased. It has been used that during development, else -Rockbox in flash wouldn't have been possible. -Extensive development effort went into the exploitation of the UART boot -mod. Mechanically adept users with good soldering skills can easily perform -these mods. Others may feel uncomfortable using the first tool -(firmware_flash.rock) for reflashing the firmware. -

-

-To comfort you a bit again: -If you are starting with a known-good image, you are unlikely to experience -problems. The flash tools have been stable for quite a while. Several users -have used them extensively, even flashing while playing! Although it worked, -it's not the recommended method. ;-)" -

-

-About -the safety of operation: Since we have dual boot, you're not giving -up the Archos firmware. It's still there when you hold F1 during -startup. So even if Rockbox from flash is not 100% stable for -everyone, you can still use the box, reflash the second image with an -updated Rockbox copy, etc. -

-

-The -flash chip being used by Archos is specified for 100,000 cycles (in -words: one hundred thousand), so you don't need to worry about that -wearing out. -

- -

4. Requirements

-

-You need two things: -

-
    -
  • - The first is a Recorder, FM Recorder or Recorder V2 model. Be sure - you're using the correct package, they are different! The technology - works for the Player models, too. Players can also be flashed, but Rockbox - does not run cold-started on those, yet. -
    • -
  • - Second, - you need an in-circuit programmable flash. Chances are about 85% - that you have, but Archos also used an older flash chip which can't - do the trick. You can find out via Rockbox debug menu, entry - Hardware Info. If the flash info gives you question marks, you're - out of luck. The only chance then is to solder in the right chip - (SST39VF020), at best with the firmware already in. If the chip is - blank, you'll need the UART boot mod as well. -
    • -
- -

5. Flashing procedure

-

-Short -explanation: copy the firmware_*.bin files for your model from the -distribution to the root directory of your box, then run the -"firmware_flash.rock" plugin. Long version, step by step -procedure: -

-
    -
  • - download the correct package for you model, - Recorder - or - FM, - or - V2, - copy some files of it to your box: -
      -
    1. - "ajbrec.ajz" - into the root directory (the version of Rockbox we're going to use - and have in the firmware file) -
      2. -
    2. - firmware_rec.bin or firmware_fm.bin or firmware_v2.bin (name depends on - your model) into the root directory (the complete firmware - for your model, with the bootloader and the two images). There now - is also a _norom variant, copy both, the plugin will decide which - one is required for your box. -
      3. -
    3. - the .rockbox subdirectory with all the plugins for Rockbox -
      4. -
    -
  • - Restart the box so that the new ajbrec.ajz gets started. -
    • - -
  • - Enter - the debug menu and select the hardware info screen. Check you flash - IDs (bottom line), and please make a note about your hardware mask - value (second line). The latter is just for our curiosity, not - needed for the flow. If the flash info shows question marks, you can - stop here, sorry. -
    • -
  • - Backup - the current firmware, using the first option of the debug menu (Dump - ROM contents). This creates 2 files in the root directory, which you - may not immediately see in the Rockbox browser. The 256kB-sized - "internal_rom_2000000-203FFFF.bin" one is your present - firmware. Back both up to your PC. -
    • -
  • - (optional) - While you're in this Rockbox version, it is recommended to give it a - test and play around with it, this version is identical to the one - about to be programmed. Make sure that especially USB access and - Rolo works. When done, restart again to have a fresh start and to be - back in this Rockbox version. -
    • -
  • - Use - the F2 settings to configure seeing all files within the browser. -
    • -
  • - Connect - the charger and make sure your batteries are also in good shape. - That's just for security reasons, it's not that flashing needs more - power. -
    • -
  • - Run - the "firmware_flash.rock" plugin. It again tells you about - your flash and the file it's gonna program. After F1 it checks the - file. Your hardware mask value will be kept, it won't overwrite it. - Hitting F2 gives you a big warning. If we still didn't manage to - scare you off, you can hit F3 to actually program and verify. The - programming takes just a few seconds. If the sanity check fails, you - have the wrong kind of boot ROM and are out of luck by now, sorry. -
    • -
  • - In - the unlikely event that the programming should give you any error, - don't switch off the box! Otherwise you'll have seen it working for - the last time. While Rockbox is still in DRAM and operational, we - could upgrade the plugin via USB and try again. If you switch it - off, it's gone. -
    • -
  • - Unplug - the charger, restart the box and hopefully be in Rockbox straight - away! You may delete "firmware_flash.rock" then, to avoid - your little brother playing with that. Pressing On+Play can do it, - or your PC. You can also delete the ".bin" files. -
    • -
  • - Try - starting again, this time holding F1 while pressing On. It should - boot the Archos firmware, which then loads rockbox from disk. In - fact, even the Archos firmware comes up quicker, because their - loader is replaced by mine. -
    • -
-

6. Bringing in a current or personal build of Rockbox

-

-Short -explanation: very easy, just play a .ucl file like "rockbox.ucl" -from the download or build. Long version: -

-

-The -second image is the working copy, the "rockbox_flash.rock" -plugin from this package reprograms it. The plugins needs to be -consistant with the Rockbox plugin API version, otherwise it will -detect mismatch and won't run. -

-

-It -requires an exotic input, a UCL-compressed image, because that's the -internal format. UCL is a nice open-source compression library. The -decompression is very fast and less than a page of C-code. The -efficiency is even better than Zip with maximum compression, cooks it -down to about 58% of the original size. For details on UCL, see: -www.oberhumer.com/opensource/ucl/ - -

-

-Linux -users will have to download it from there and compile it, for Win32 -and Cygwin the executables are in -the packages. -The sample program from that download is called "uclpack". -We'll use that to compress "rockbox.bin" which is the -result of the compilation. This is a part of the build process -meanwhile. If you compile Rockbox yourself, you should copy uclpack -to a directory which is in the path, we recommend placing it in the -same dir as SH compiler. -

-

-Don't -flash any "old" builds which don't have the latest -coldstart ability. They won't boot. These instructions refer to -builds from cvs state 2003-07-10 on. -

-

-Here are the steps: -

-
    -
  • - If - you start from a .ajz file, you'll need to descramble it first into - "rockbox.bin", by using "descramble ajbrec.ajz - rockbox.bin". IMPORTANT: For an FM, the command is different, - use "descramble -fm ajbrec.ajz rockbox.bin"! Otherwise the - image won't be functional. Compress the image using uclpack, - algorithm 2e (the most efficient, and the only one supported by the - bootloader), with maximum compression, by typing "uclpack --2e - --best rockbox.bin rockbox.ucl". You can make a batch file for - this and the above step, if you like. -
    • -
  • - Normally, - you'll simply download or compile rockbox.ucl. Copy it together with - ajbrec.ajz and all the rocks to the appropriate places, replacing - the old. -
    • -
  • - Just - "play" the .ucl file, this will kick off the - "rockbox_flash.rock" plugin. It's a bit similar to the - other one, but it's made different to make the user aware. It will - check the file, available size, etc. With F2 it's being programmed, - no need for warning this time. If it goes wrong, you'll still have - the permanent image. -
    • -
  • - It - may happen that you get an "Incompatible Version" error, - if the plugin interface has changed meanwhile. You're running an - "old" copy of Rockbox, but are trying to execute a newer - plugin, the one you just downloaded. The easiest solution is to rolo - into this new version, by playing the ajbrec.ajz file. Then you are - consistant and can play rockbox.ucl. -
    • -
  • - When - done, you can restart the box and hopefully your new Rockbox image. -
    • -
-

-If -you like or have to, you can also flash the Archos image as the -second one, e.g. in case Rockbox from flash doesn't work for you. -This way you keep the dual bootloader and you can easily try -different later. You can download -UCLs -for the latest firmware -here. - -

- -

7. Restoring the original firmware

-

-If you'd like to revert to the original firmware, you can -do like you did when you flashed Rockbox for the first time (section 5), but -copy and rename your backup to be -"firmware_rec.bin" on the box this time. Keep the Rockbox -copy and the plugins of this package for that job, because that's the -one it was tested with. -

- -

8. Known issues and limitations

-

-Latest -Rockbox now has a charging screen, but it is in an early stage. -You'll get it when the unit is off and you plug in the charger. The -Rockbox charging algorithm is first measuring the battery voltage for -about 40 seconds, after that it only starts charging when the -capacity is below 85%. You can use the Archos charging (which always -tops off) by holding F1 while plugging in. Some FM users reported -charging problems even with F1, they had to revert to the original -flash content. -

-

-If the plugin API is changed, new builds may render the plugins -incompatible. When updating, make sure you grab those too, and rolo -into the new version before flashing it. -

-

-There -are two variants of how the boxes starts, therefore the normal and -the _norom firmware files. The vast majority of the -Player/Recorder/FM all have the same boot ROM content, -differentiation comes later by flash content. Rockbox identifies this -boot ROM with a CRC value of 0x222F in the hardware info screen. Some -recorders have the boot ROM disabled (it might be unprogrammed) and -start directly from a flash mirror at address zero. They need the new -_norom firmware, it has a slightly different bootloader. Without a -boot ROM there is no UART boot safety net. To compensate for that as -much as possible the MiniMon monitor is included, it starts with -F3+On. Using that the box can be reprogrammed via serial if the first -~2000 bytes of the flash are OK. -

- -

8. Movies and images

-

- Jörg's AVI movie (1.5MB) rockbox_flash_boot.avi -showing his unit booting Rockbox from flash. -

- Roland's screendump from the movie:
- - -#include "foot.t" diff --git a/www/docs/flash/rockbox-flash.jpg b/www/docs/flash/rockbox-flash.jpg deleted file mode 100644 index 1ca3f36d8a..0000000000 Binary files a/www/docs/flash/rockbox-flash.jpg and /dev/null differ diff --git a/www/docs/flash/rockbox_flash_boot.avi b/www/docs/flash/rockbox_flash_boot.avi deleted file mode 100644 index ddbe9a9d4a..0000000000 Binary files a/www/docs/flash/rockbox_flash_boot.avi and /dev/null differ diff --git a/www/docs/fmrecorder.jpg b/www/docs/fmrecorder.jpg deleted file mode 100644 index 69af670a52..0000000000 Binary files a/www/docs/fmrecorder.jpg and /dev/null differ diff --git a/www/docs/fmrecorder_t.jpg b/www/docs/fmrecorder_t.jpg deleted file mode 100644 index f3cb37de68..0000000000 Binary files a/www/docs/fmrecorder_t.jpg and /dev/null differ diff --git a/www/docs/how_to_compile.t b/www/docs/how_to_compile.t deleted file mode 100644 index f58b80615e..0000000000 --- a/www/docs/how_to_compile.t +++ /dev/null @@ -1,8 +0,0 @@ -#define _PAGE_ How to compile Rockbox -#include "head.t" - -

-#include "how_to_compile.raw"
-
- -#include "foot.t" diff --git a/www/docs/index.t b/www/docs/index.t deleted file mode 100644 index eccd2d390f..0000000000 --- a/www/docs/index.t +++ /dev/null @@ -1,123 +0,0 @@ -#define _PAGE_ Documentation -#include "head.t" - -

For Users

- -

Customizing Rockbox

- -

For Advanced Users

- - -

For Hackers

- -

Howtos

- - -

Specs and Papers

- - -

Rockbox Design Docs

- - - -

Hardware

- - -

External Pages

- - -#include "foot.t" diff --git a/www/docs/lcd_new.gif b/www/docs/lcd_new.gif deleted file mode 100644 index 823843b5a4..0000000000 Binary files a/www/docs/lcd_new.gif and /dev/null differ diff --git a/www/docs/lcd_new_hw.gif b/www/docs/lcd_new_hw.gif deleted file mode 100644 index 11690897b1..0000000000 Binary files a/www/docs/lcd_new_hw.gif and /dev/null differ diff --git a/www/docs/lcd_new_subst.gif b/www/docs/lcd_new_subst.gif deleted file mode 100644 index 3b85f03f7b..0000000000 Binary files a/www/docs/lcd_new_subst.gif and /dev/null differ diff --git a/www/docs/lcd_old.gif b/www/docs/lcd_old.gif deleted file mode 100644 index a01467b87b..0000000000 Binary files a/www/docs/lcd_old.gif and /dev/null differ diff --git a/www/docs/lcd_old_hw.gif b/www/docs/lcd_old_hw.gif deleted file mode 100644 index 651450187f..0000000000 Binary files a/www/docs/lcd_old_hw.gif and /dev/null differ diff --git a/www/docs/lcd_old_subst.gif b/www/docs/lcd_old_subst.gif deleted file mode 100644 index 21af2bbb8a..0000000000 Binary files a/www/docs/lcd_old_subst.gif and /dev/null differ diff --git a/www/docs/license.t b/www/docs/license.t deleted file mode 100644 index 8d4f722763..0000000000 --- a/www/docs/license.t +++ /dev/null @@ -1,8 +0,0 @@ -#define _PAGE_ GNU General Public License -#include "head.t" - -
-#include "license.raw"
-
- -#include "foot.t" diff --git a/www/docs/mpeghdr.t b/www/docs/mpeghdr.t deleted file mode 100644 index bf3373e98c..0000000000 --- a/www/docs/mpeghdr.t +++ /dev/null @@ -1,761 +0,0 @@ -#define _PAGE_ MPEG Audio Frame Header -#include "head.t" - -

This is a brief and informal document targeted to those who want to deal -with the MPEG format. If you are one of them, you probably already know what -is MPEG audio. If not, jump to http://www.mp3.com/ or http://www.layer3.org/ where you will find -more details and also more links. This document does not cover compression and -decompression algorithm. - -

NOTE: You cannot just search the Internet and find the MPEG audio specs. It -is copyrighted and you will have to pay quite a bit to get the Paper. That's why -I made this. Information I got is gathered from the Internet, and mostly originate -from program sources I found available for free. Despite my intention to always -specify the information sources, I am not able to do it this time. Sorry, I did -not maintain the list. :-( -

These are not a decoding specs, it just informs you how to read the MPEG headers and the MPEG TAG. MPEG Version 1, 2 and 2.5 and Layer I, II -and III are supported, the MP3 TAG (ID3v1 and ID3v1.1) also.. Those of you -who use Delphi may find MPGTools Delphi unit (freeware source) -useful, it is where I implemented this stuff. - -

I do not claim information presented in this document is accurate. At first -I just gathered it from different sources. It was not an easy task but I needed -it. Later, I received lots of comments as feedback when I published this document. -I think this last release is highly accurate due to comments and corrections I -received. -

This document is last updated on December 22, 1999. -

MPEG Audio Compression Basics - -

This is one of many methods to compress audio in digital form trying to consume -as little space as possible but keep audio quality as good as possible. MPEG compression -showed up as one of the best achievements in this area. -

This is a lossy compression, which means, you will certainly loose some audio -information when you use this compression methods. But, this lost can hardly be -noticed because the compression method tries to control it. By using several quite -complicate and demanding mathematical algorithms it will only loose those parts -of sound that are hard to be heard even in the original form. This leaves more -space for information that is important. This way you can compress audio up to -12 times (you may choose compression ratio) which is really significant. Due to -its quality MPEG audio became very popular. -

MPEG standards MPEG-1, MPEG-2 and MPEG-4 are known but this document covers -first two of them. There is an unofficial MPEG-2.5 which is rarely used. It is -also covered. -

MPEG-1 audio (described in ISO/IEC 11172-3) describes three Layers of audio coding with the following properties: -

  • one or two audio channels -
  • sample rate 32kHz, 44.1kHz or 48kHz. -
  • bit rates from 32kbps up to 448kbps
    -Each layer has its merits. - -

    MPEG-2 audio (described in ISO/IEC 13818-3) has two extensions to MPEG-1, usually referred as MPEG-2/LSF and MPEG-2/Multichannel. -

    MPEG-2/LSF has the following properties: -

  • one or two audio channels -
  • sample rates half those of MPEG-1 -
  • bit rates from 8 kbps up to 256kbps. - -

    MPEG-2/Multichannel has the following properties: -

  • up to 5 full range audio channels and an LFE-channel (Low Frequency -Enhancement <> subwoofer!) -
  • sample rates the same as those of MPEG-1 -
  • highest possible bitrate goes up to about 1Mbps for 5.1 - - -

    MPEG Audio Frame -Header - -

    An MPEG audio file is built up from smaller parts called frames. Generally, -frames are independent items. Each frame has its own header and audio informations. -There is no file header. Therefore, you can cut any part of MPEG file and play -it correctly (this should be done on frame boundaries but most applications will -handle incorrect headers). For Layer III, this is not 100% correct. Due to internal -data organization in MPEG version 1 Layer III files, frames are often dependent -of each other and they cannot be cut off just like that. -

    When you want to read info about an MPEG file, it is usually enough to find -the first frame, read its header and assume that the other frames are the same -This may not be always the case. Variable bitrate MPEG files may use so called -bitrate switching, which means that bitrate changes according to the content of -each frame. This way lower bitrates may be used in frames where it will not reduce -sound quality. This allows making better compression while keeping high quality -of sound. -

    The frame header is constituted by the very first four bytes (32bits) in a -frame. The first eleven bits (or first twelve bits, see below about frame sync) -of a frame header are always set and they are called "frame sync". Therefore, -you can search through the file for the first occurence of frame sync (meaning -that you have to find a byte with a value of 255, and followed by a byte with -its three (or four) most significant bits set). Then you read the whole header -and check if the values are correct. You will see in the following table the exact -meaning of each bit in the header, and which values may be checked for validity. -Each value that is specified as reserved, invalid, bad, or not allowed should -indicate an invalid header. Remember, this is not enough, frame sync can be easily -(and very frequently) found in any binary file. Also it is likely that MPEG file -contains garbage on it's beginning which also may contain false sync. Thus, you -have to check two or more frames in a row to assure you are really dealing with -MPEG audio file. -

    Frames may have a CRC check. The CRC is 16 bits long -and, if it exists, it follows the frame header. After the CRC comes the audio -data. You may calculate the length of the frame and use it if you need to read -other headers too or just want to calculate the CRC of the frame, to compare -it with the one you read from the file. This is actually a very good method to -check the MPEG header validity. - -

    Here is "graphical" presentation of the header content. Characters -from A to M are used to indicate different fields. In the table, you can see -details about the content of each field. -

    - -AAAAAAAA AAABBCCD EEEEFFGH IIJJKLMM - - - -

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    SignLength
    (bits)    		Position
    (bits)    		Description
    A11(31-21)Frame sync (all bits set)
    B2(20,19)MPEG Audio version ID
    -00 - MPEG Version 2.5
    01 - reserved
    10 - MPEG Version 2 (ISO/IEC 13818-3)
    11 - MPEG Version 1 (ISO/IEC 11172-3) -

    Note: MPEG Version 2.5 is not official standard. Bit No 20 in frame header -is used to indicate version 2.5. Applications that do not support this MPEG version -expect this bit always to be set, meaning that frame sync (A) is twelve bits long, -not eleve as stated here. Accordingly, B is one bit long (represents only bit -No 19). I recommend using methodology presented here, since this allows you to -distinguish all three versions and keep full compatibility. -

    C2(18,17)Layer description
    -00 - reserved
    -01 - Layer III
    -10 - Layer II
    -11 - Layer I
    D1(16)Protection bit
    -0 - Protected by CRC (16bit crc follows header)
    -1 - Not protected
    E4(15,12)Bitrate index
    - - - - - - - - - - - - - - - - - - -
    bitsV1,L1V1,L2V1,L3V2,L1V2, L2 & L3
    0000freefreefreefreefree
    0001323232328
    00106448404816
    00119656485624
    010012864566432
    010116080648040
    011019296809648
    01112241129611256
    100025612811212864
    100128816012814480
    101032019216016096
    1011352224192176112
    1100384256224192128
    1101416320256224144
    1110448384320256160
    1111badbadbadbadbad
    -

    -NOTES: All values are in kbps
    -V1 - MPEG Version 1
    -V2 - MPEG Version 2 and Version 2.5
    -L1 - Layer I
    -L2 - Layer II
    -L3 - Layer III
    -"free" means free format. If the correct fixed bitrate (such files cannot -use variable bitrate) is different than those presented in upper table it must -be determined by the application. This may be implemented only for internal purposes -since third party applications have no means to find out correct bitrate. Howewer, -this is not impossible to do but demands lot's of efforts.
    -"bad" means that this is not an allowed value - -

    MPEG files may have variable bitrate (VBR). This means that bitrate in the file may change. I have learned about two used methods: -

  • bitrate switching. Each frame may be created with different bitrate. It may be used in all layers. Layer III decoders must support this method. Layer I & II decoders may support it. -
  • bit reservoir. Bitrate may be borrowed (within limits) from previous frames -in order to provide more bits to demanding parts of the input signal. This causes, -however, that the frames are no longer independent, which means you should not -cut this files. This is supported only in Layer III. -

    More about VBR you may find on Xing Tech -site -

    For Layer II there are some combinations of bitrate and mode which are not -allowed. Here is a list of allowed combinations. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    bitrateallowed modes
    freeall
    32single channel
    48single channel
    56single channel
    64all
    80single channel
    96all
    112all
    128all
    160all
    192all
    224stereo, intensity stereo, dual channel
    256stereo, intensity stereo, dual channel
    320stereo, intensity stereo, dual channel
    384stereo, intensity stereo, dual channel
    -

    • F2(11,10)Sampling rate frequency index (values are in Hz) - - - - - - -
    bitsMPEG1MPEG2MPEG2.5
    00441002205011025
    01480002400012000
    1032000160008000
    11reserv.reserv.reserv.
    -
    G1(9)Padding bit
    -0 - frame is not padded
    -1 - frame is padded with one extra slot
    - -Padding is used to fit the bit rates exactly. For an example: 128k 44.1kHz layer II uses a lot of 418 bytes and some of 417 bytes long frames to get the exact 128k bitrate. For Layer I slot is 32 bits long, for Layer II and Layer III slot is 8 bits long. - - - -

    How to calculate frame length - -

    First, let's distinguish two terms frame size and frame length. Frame size -is the number of samples contained in a frame. It is constant and always 384 samples -for Layer I and 1152 samples for Layer II and Layer III. Frame length is length -of a frame when compressed. It is calculated in slots. One slot is 4 bytes long -for Layer I, and one byte long for Layer II and Layer III. When you are reading -MPEG file you must calculate this to be able to find each consecutive frame. Remember, -frame length may change from frame to frame due to padding or bitrate switching. -

    Read the BitRate, SampleRate and Padding of the frame header. -

    For Layer I files us this formula: -

    FrameLengthInBytes = (12 * BitRate / SampleRate + Padding) * 4 -

    For Layer II & III files use this formula: -

    FrameLengthInBytes = 144 * BitRate / SampleRate + Padding -

    Example:
    -Layer III, BitRate=128000, SampleRate=44100, Padding=0
    -      ==>  FrameSize=417 bytes -

    H1(8)Private bit. It may be freely used for specific needs of an application, i.e. if it has to trigger some application specific events.
    I2(7,6)Channel Mode
    -00 - Stereo
    -01 - Joint stereo (Stereo)
    -10 - Dual channel (Stereo)
    -11 - Single channel (Mono)
    J2(5,4)Mode extension (Only if Joint stereo) -

    Mode extension is used to join informations that are of no use for stereo effect, thus reducing needed resources. These bits are dynamically determined by an encoder in Joint stereo mode. - -

    Complete frequency range of MPEG file is divided in subbands There are 32 subbands. For Layer I & II these two bits determine frequency range (bands) where intensity stereo is applied. For Layer III these two bits determine which type of joint stereo - -is used (intensity stereo or m/s stereo). Frequency range is determined within decompression algorythm. - - - - - -
    Layer I and IILayer III
    - - - - - -
    valueLayer I & II
    00bands 4 to 31
    01bands 8 to 31
    10bands 12 to 31
    11bands 16 to 31
    -    		 - - - - - -
    Intensity stereoMS stereo
    offoff
    onoff
    offon
    onon
    -
    -

    K1(3)Copyright
    -0 - Audio is not copyrighted
    -1 - Audio is copyrighted
    L1(2)Original
    -0 - Copy of original media
    -1 - Original media
    M2(1,0)Emphasis
    -00 - none
    -01 - 50/15 ms
    -10 - reserved
    -11 - CCIT J.17
    -

     

    - -

    MPEG Audio Tag ID3v1 -

    The TAG is used to describe the MPEG Audio file. It contains information -about artist, title, album, publishing year and genre. There is some extra -space for comments. It is exactly 128 bytes long and is located at very end of -the audio data. You can get it by reading the last 128 bytes of the MPEG audio -file. - -

    -AAABBBBB BBBBBBBB BBBBBBBB BBBBBBBB
    -BCCCCCCC CCCCCCCC CCCCCCCC CCCCCCCD
    -DDDDDDDD DDDDDDDD DDDDDDDD DDDDDEEE
    -EFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFG
    -     - -

    - - - - - - - - - - - - -
    SignLength
    (bytes)    		Position
    -(bytes)    		Description
    A3(0-2)Tag identification. Must contain 'TAG' if tag exists and is -correct.
    B30(3-32)Title
    C30(33-62)Artist
    D30(63-92)Album
    E4(93-96)Year
    F30(97-126)Comment
    G1(127)Genre
    -
    - -

    The specification asks for all fields to be padded with null character -(ASCII 0). However, not all applications respect this (an example is WinAmp -which pads fields with <space>, ASCII 32). - -

    There is a small change proposed in ID3v1.1 structure. The last byte -of the Comment field may be used to specify the track number of a song in an -album. It should contain a null character (ASCII 0) if the information is -unknown. - -

    Genre is a numeric field which may have one of the following values: - -

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    0'Blues'20'Alternative'40'AlternRock'60'Top 40'
    1'Classic Rock'21'Ska'41'Bass'61'Christian Rap'
    2'Country'22'Death Metal'42'Soul'62'Pop/Funk'
    3'Dance'23'Pranks'43'Punk'63'Jungle'
    4'Disco'24'Soundtrack'44'Space'64'Native American'
    5'Funk'25'Euro-Techno'45'Meditative'65'Cabaret'
    6'Grunge'26'Ambient'46'Instrumental Pop'66'New Wave'
    7'Hip-Hop'27'Trip-Hop'47'Instrumental Rock'67'Psychadelic'
    8'Jazz'28'Vocal'48'Ethnic'68'Rave'
    9'Metal'29'Jazz+Funk'49'Gothic'69'Showtunes'
    10'New Age'30'Fusion'50'Darkwave'70'Trailer'
    11'Oldies'31'Trance'51'Techno-Industrial'71'Lo-Fi'
    12'Other'32'Classical'52'Electronic'72'Tribal'
    13'Pop'33'Instrumental'53'Pop-Folk'73'Acid Punk'
    14'R&B'34'Acid'54'Eurodance'74'Acid Jazz'
    15'Rap'35'House'55'Dream'75'Polka'
    16'Reggae'36'Game'56'Southern Rock'76'Retro'
    17'Rock'37'Sound Clip'57'Comedy'77'Musical'
    18'Techno'38'Gospel'58'Cult'78'Rock & Roll'
    19'Industrial'39'Noise'59'Gangsta'79'Hard Rock'
    -

    -WinAmp expanded this table with next codes:
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    80'Folk'92'Progressive Rock'104'Chamber Music'116'Ballad'
    81'Folk-Rock'93'Psychedelic Rock'105'Sonata'117'Poweer Ballad'
    82'National Folk'94'Symphonic Rock'106'Symphony'118'Rhytmic Soul'
    83'Swing'95'Slow Rock'107'Booty Brass'119'Freestyle'
    84'Fast Fusion'96'Big Band'108'Primus'120'Duet'
    85'Bebob'97'Chorus'109'Porn Groove'121'Punk Rock'
    86'Latin'98'Easy Listening'110'Satire'122'Drum Solo'
    87'Revival'99'Acoustic'111'Slow Jam'123'A Capela'
    88'Celtic'100'Humour'112'Club'124'Euro-House'
    89'Bluegrass'101'Speech'113'Tango'125'Dance Hall'
    90'Avantgarde'102'Chanson'114'Samba'  
    91'Gothic Rock'103'Opera'115'Folklore'  
    Any other value should be considered as 'Unknown' -
    -

     

    - -

    MPEG Audio Tag ID3v2 -

    This is new proposed TAG format which is different than ID3v1 and ID3v1.1. -Complete tech specs for it may be found at http://www.id3.org/. -

    -
    -

    Created on September 1998. by Predrag -Supurovic.
    -Thanks to Jean for debugging and polishing -of this document, Peter -Luijer, Guwani, Rob Leslie and Franc Zijderveld
    -for valuable comments and corrections.

    -

    © 1998, 1999 Copyright by DataVoyage

    -

    This document may be changed. Check http://www.dv.co.yu/mpgscript/mpeghdr.htm -for updates.
    -You may use it freely. Distribution is allowed only in unaltered form. If you -can help me make it more accurate, please do.

    -

     

    -
    - -#include "foot.t" diff --git a/www/docs/nano_t.jpg b/www/docs/nano_t.jpg deleted file mode 100644 index 2dcf3caaf0..0000000000 Binary files a/www/docs/nano_t.jpg and /dev/null differ diff --git a/www/docs/newplayer.jpg b/www/docs/newplayer.jpg deleted file mode 100644 index 4386240adc..0000000000 Binary files a/www/docs/newplayer.jpg and /dev/null differ diff --git a/www/docs/newplayer_t.jpg b/www/docs/newplayer_t.jpg deleted file mode 100644 index 89c1181907..0000000000 Binary files a/www/docs/newplayer_t.jpg and /dev/null differ diff --git a/www/docs/nodo.t b/www/docs/nodo.t deleted file mode 100644 index 841eaa5475..0000000000 --- a/www/docs/nodo.t +++ /dev/null @@ -1,6 +0,0 @@ -#define _PAGE_ FAQ - Features We Will Not Implement -#include "head.t" - -#include "nodo.raw" - -#include "foot.t" diff --git a/www/docs/oldplayer.jpg b/www/docs/oldplayer.jpg deleted file mode 100644 index 5d1a2489e1..0000000000 Binary files a/www/docs/oldplayer.jpg and /dev/null differ diff --git a/www/docs/oldplayer_t.jpg b/www/docs/oldplayer_t.jpg deleted file mode 100644 index ea13f2e851..0000000000 Binary files a/www/docs/oldplayer_t.jpg and /dev/null differ diff --git a/www/docs/ondiofm.jpg b/www/docs/ondiofm.jpg deleted file mode 100644 index acf9f00929..0000000000 Binary files a/www/docs/ondiofm.jpg and /dev/null differ diff --git a/www/docs/ondiofm_t.jpg b/www/docs/ondiofm_t.jpg deleted file mode 100644 index bee36463f7..0000000000 Binary files a/www/docs/ondiofm_t.jpg and /dev/null differ diff --git a/www/docs/ondiosp.jpg b/www/docs/ondiosp.jpg deleted file mode 100755 index eafbfa504b..0000000000 Binary files a/www/docs/ondiosp.jpg and /dev/null differ diff --git a/www/docs/ondiosp_t.jpg b/www/docs/ondiosp_t.jpg deleted file mode 100755 index 92e257485f..0000000000 Binary files a/www/docs/ondiosp_t.jpg and /dev/null differ diff --git a/www/docs/patch.t b/www/docs/patch.t deleted file mode 100644 index ab43ed1606..0000000000 --- a/www/docs/patch.t +++ /dev/null @@ -1,99 +0,0 @@ -#define _PAGE_ How To Work With Patches -#include "head.t" -

    - When we speak of 'patches' in the Rockbox project, we mean a set of changes - to one or more source files. - -

    Tools Of The Trade

    -

    -Use the tools 'diff' and 'patch'. Preferably the GNU versions. They're readily -available for all imaginable platforms. -

    -Try one of these: -

    - -

    Newlines

    -

    - These tools will assume and operate on "unix-style" newlines. That means all -files that you're diffing and patching etc must have LF newlines only, and -not the Windows/DOS standard CRLF newlines, -

    - Not complying to this simple fact will cause you grief. Mark my words. - -

    Creating A Patch

    -

    - We generate diffs (often called patches) using 'diff' in a manner similar to -this: -

    -  diff -u oldfile newfile > patch
-
    -

    - People who have checked out code with CVS can do diffs using cvs like this: -

    -  cvs diff -u file > patch
-
    -

    - 'diff' can also be used on a whole directory etc to generate one file with -changes done to multiple: -

    -  diff -u olddir newdir > patch 
-
    -

    - The -u option means the output is using the 'unified diff' format. Older - diff programs don't have that, and then -c (for 'context diff') is OK. - -

    Submitting A Patch

    - -

    All patches that are meant for inclusion in the sources should follow the -format listed on the Contributing to Rockbox -page, and be posted to the patch -tracker. Patches sent to the mailing list are quickly lost in the traffic -of the list itself. - -

    - Please keep in mind that not all submitted patches will be accepted. - -

    Applying A Patch

    -

    - Applying a 'patch' (output from diff -u) is done with the 'patch' tool: -

    -  cd to/source/root
-  patch < patchfile
-
    -

    - patch knows that the patchfile is a set of changes on one or more files, and -will do those to your local files. If your files have changed too much for the -patch to work, it will save the sections of the patch that aren't possible to -apply in a file called "filename.rej" (filename being the name of the file for -which the failing section was intended for). Then you must take care of them -manually. - -

    - If there is path information in the patchfile that you want to cut off - from the left, tell patch how many directory levels to cut off to find the - names in your file system: -

    -  patch -p0 < patchfile
-  patch -p1 < patchfile
-  patch -p2 < patchfile
-
    - ... each example line removes one extra level of dir info from the left. -

    - You can use the --dry-run option to patch to make sure that the patch applies -clean. It doesn't actually apply the patch, only prints what would happen if -you run it. -

    Removing A Patch

    -

    - You can remove a patch again from the sources by doing the reverse action of -a specific patch. You do this with the -R (or --reverse) options, such as: -

    -  patch -p1 -R < patchfile
-
    - -#include "foot.t" diff --git a/www/docs/ports.t b/www/docs/ports.t deleted file mode 100755 index 511fb0aca6..0000000000 --- a/www/docs/ports.t +++ /dev/null @@ -1,230 +0,0 @@ -#define _PAGE_ Port pin assignments -#include "head.t" - -

    Port A

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    Port pinPlayerRecorderFM/V2 Recorder
    PA0GP InDC adapter detect (0=inserted)/CS4MAS Parallel Port (for recording)/CS4MAS Parallel Port (for recording)
    PA1/RAS OutDRAM control/RAS OutDRAM control/RAS OutDRAM control
    PA2/CS6 OutATA registers/CS6 OutATA registers/CS6 OutATA registers
    PA3/WAIT InBus handshake/WAIT InBus handshake/WAIT InBus handshake
    PA4/WR OutBus write signal/WR OutBus write signal/WR OutBus write signal
    PA5GP InON key (0=pressed)GP OutATA power control (1=on)GP OutATA/LED power control (1=on)
    PA6/RD OutBus read signal/RD OutBus read signal/RD OutBus read signal
    PA7GP OutATA buffer control (0=active)GP OutATA buffer control (0=active)GP OutATA buffer control (0=active)
    PA8  GP OutMAS POR Reset (polarity varies)GP OutMAS POR Reset (polarity varies)
    PA9GP OutATA Reset (0=reset)GP OutATA Reset (0=reset)GP OutATA Reset (0=reset)
    PA10GP OutUSB Enable (0=enable)GP OutUSB Enable (polarity varies)GP OutUSB Enable (polarity varies)
    PA11GP InSTOP key (0=pressed)GP OutMAS PR DMA Request (polarity varies)GP OutMAS PR DMA Request (polarity varies)
    PA12/IRQ0ATA INTRQ (not used)/IRQ0ATA INTRQ (not used)/IRQ0ATA INTRQ (not used)
    PA13  /IRQ1RTC IRQ  
    PA14GP OutBacklight (1=on)GP InNot used  
    PA15GP InUSB cable detect (0=inserted)/IRQ3MAS Demand IRQ, start demand/IRQ3MAS Demand IRQ, start demand
    - -

    Port B

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    Port pinPlayerRecorderFM/V2 Recorder
    PB0GP OutLCD Data Select (1=data)GP OutLCD Serial DataGP OutLCD Serial Data / FM Radio Data In
    PB1GP OutLCD Chip Select (0=active)GP OutLCD Serial ClockGP OutLCD Serial Clock / FM Radio Serial Clock
    PB2GP OutLCD Serial DataGP OutLCD Data Select (1=data)GP OutLCD Data Select (1=data)
    PB3GP OutLCD Serial ClockGP OutLCD Chip Select (0=active)GP OutLCD Chip Select (0=active) / FM Radio Chip Enable (1=active)
    PB4GP OutHard disk power (1=on) NewPlayer onlyGP InOFF key (0=pressed)GP InFM Radio Data Out
    PB5GP OutMAS WSEN (1=enable)GP OutCharger control (0=enable)GP OutMain power control (0=shut off)
    PB6GP OutRed LED control (1=on)GP OutRed LED control (1=on)GP OutRed LED control (1=on)
    PB7GP I/OI²C DataGP OutI²C DataGP OutI²C Data
    PB8  GP InON key (0=pressed)  
    PB9TxD0MAS Serial link for MP3 dataTxD0MAS Serial link for MP3 dataTxD0MAS Serial link for MP3 data
    PB10RxD1Remote control serial inputRxD1Remote control serial inputUnused(meant for RDS data input, IIRC)
    PB11      
    PB12SCK0MAS Serial Clock for MP3 dataSCK0MAS Serial Clock for MP3 dataSCK0MAS Serial Clock for MP3 data
    PB13GP OutI²C ClockGP OutI²C ClockGP OutI²C Clock
    PB14/IRQ6MAS Demand IRQ, stop demand/IRQ6MAS Demand IRQ, stop demand/IRQ6MAS Demand IRQ, stop demand
    PB15GP InMAS MP3 frame syncGP InMAS PRTW input (0=ready)GP InMAS PRTW input (0=ready)
    - -

    Port C/Analog In

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    Port pinPlayerRecorderFM/V2 Recorder
    PC0/AN0LEFT keyBattery voltage 1 (unusable) 
    PC1/AN1MENU keyCharger regulator voltageUSB detect
    PC2/AN2RIGHT keyUSB voltageOFF key
    PC3/AN3PLAY key ON key
    PC4/AN4 F1, F2, F3, UP keysF1, F2, F3, UP keys
    PC5/AN5 DOWN, PLAY, LEFT, RIGHT keysDOWN, PLAY, LEFT, RIGHT keys
    PC6/AN6Battery voltageBattery voltageBattery voltage
    PC7/AN7DC input voltageDC input voltageCharge current?
    -#include "foot.t" diff --git a/www/docs/recorder.jpg b/www/docs/recorder.jpg deleted file mode 100644 index 016bac2930..0000000000 Binary files a/www/docs/recorder.jpg and /dev/null differ diff --git a/www/docs/recorder_t.jpg b/www/docs/recorder_t.jpg deleted file mode 100644 index 74806c0263..0000000000 Binary files a/www/docs/recorder_t.jpg and /dev/null differ diff --git a/www/docs/repairbattery.t b/www/docs/repairbattery.t deleted file mode 100644 index 080c2fc186..0000000000 --- a/www/docs/repairbattery.t +++ /dev/null @@ -1,53 +0,0 @@ -#define _PAGE_ Repair your JBR V1 battery connectors -#include "head.t" - -

    - This guide will show you how to repair the battery connectors on your - Jukebox Recorder V1. You will need some soldering skills, and not be afraid - of opening up your jukebox. If you have second thoughts about this, let - somebody else do it for you. - NewMP3Technology can certainly help you with that. - -

    Symptoms

    -A loose battery connector can give all kinds of weird behaviour: - -
      -
    • Drastically lowered battery runtime -
    • It shuts down or reboots when you squeeze the bumpers -
    • It refuses to start up, saying something like this: - 
      -      HD register error
-      SC1 (85) 128
-      SN1 (170) 128
-      SC2 (170) 128
-      SN2 (85) 128
-
      -
    - -

    Performing the surgery

    -First you open up your recorder, this is described -here. -

    -This picture shows you the two solder joints that most often are broken. - -

    - - -

    - Now you fire up your soldering iron and resolder the joints. Make sure that the PCB really is connected to the metal housing. - -

    - - -

    -Once you have resoldered all joints, reassemble the archos and start it up. -The reassembly is described -here. - -

    -Good luck! - -

    -Linus - -#include "foot.t" diff --git a/www/docs/repairlcd.t b/www/docs/repairlcd.t deleted file mode 100644 index 6c1438853e..0000000000 --- a/www/docs/repairlcd.t +++ /dev/null @@ -1,125 +0,0 @@ -#define _PAGE_ Repair Your LCD -#include "head.t" - -

    -Author: Peter van Hardenberg -

    -My LCD screen broke, I know I'm not alone, so at dwihno's suggestion, I'm -typing up this information so everyone else can benefit too. -

    -Okay, your LCD is broken, but the 'box still works. Now what? -

    PART 1: Getting a new screen

    -

    -You're going to need a new LCD, but odds are you don't have a clue where -to get one. -

    -Part number: G112064-30
-Manufacturer: Shing Yih Technologies, Taiwan
-
    -

    -Unless you're buying a few hundred, I don't think Shing Yih is going to -listen to you. Instead, I recommend you shop at: -

    -http://www.newmp3technology.com/ -

    -For me, a replacement LCD was $24USD with shipping. (Archos wants $60 -minimum just to look at it.) - -

    PART 2: Disassembling the Frame

    -

    -This is written up well on the rockbox site, but you will need a #10 Torx -bit (check your hardware store) and a small Phillip's head screwdriver to -take the box apart. -

    -http://rockbox.haxx.se/mods/disassemble.html - -

    PART 3: Desoldering

    -

    -There are a total of eight points you will need to desolder. They are -three on each side of the metal frame holding the electronics, and two at -the top end. The side points are structural, but the top two (which are on -either side of the microphone) supply power to the hard drive. I am not -going to tell you how to desolder a joint. That is up to you. I found it -helpful to use a small tool to lift up the joints as I worked, seperating -the side ones individually and then gradually working out the top ones. I -certainly hope you are more competant at desoldering than I. -

    -The two electronics boards inside the Archos are connected by a paralell -connector, much like the one you find on the back of your hard drives, -though without the cable. This is why even desoldered the boards will -stick together. Carefully seperate the two boards. They are connected by -several wires. Don't break them. -

    -NOTE: The two connections at the top (by the microphone) have wires -embedded in them. This won't make your life any easier. -

    -NOTE: If you remove the tape in the battery compartment while you work, -make sure you replace it with something afterwards! (A couple strips of -simple scotch tape worked for me.) -

    -BE CAREFUL not to break the end boards off while you work! -

    -Again, the rockbox site has some handy pictures, though this section is -for the non-recorder model and is a bit uninformative. -

    -http://rockbox.haxx.se/mods/disassemble2.html - -

    PART 3: The New LCD

    -

    -Remove the old LCD cable. There are two little clips (one on each side of -the connector) that can be gently pushed out to free the strip connector. -When you put the new LCD in, make sure you have the right orientation -(duh) and also make sure the connection is tight before you clip it back -down. This part is probably the easiest of the whole affair. Be careful -with the plastic frame under the LCD, as it seems a bit fragile. - -

    PART 4: Test!

    -

    -Don't solder it all back together yet. Re-seat the top electronics board -so the parallel connector is snug. (Watch out for those pins by the -microphone! Now you can plug the unit into the AC adapter to see if the -LCD works. You should get a message on the LCD saying "ATA Error" or -something to that effect. This means the LCD is sitting correctly and you -can proceed to reassemble. If not, go back to part 3. -

    -

    PART 5: Resolder

    -

    -UNPLUG the archos. (Just thought I'd better reiterate.) -

    -Resolder the two top connections (the ones by the mic). -

    -PLUG the archos back in. The hard drive should spin up. Nothing much more -will happen until you put the batteries in though. (I think, I can't quite -remember.) -

    -Okay, good. Unplug the Archos again. -

    -IMPORTANT: When you resolder the frame points, make sure you don't leave -any pointy bits of solder poking into where the batteries run. I did, and -they scraped the plastic off my batteries, shorted out against the frame, -melted the inside of one of the bumpers a bit (smoking and smelling -awfully) and just about scared me to death. This is also why you need to -put the tape back on if you removed it. - -

    PART 6: Reassemble the Archos!

    -

    -Put the archos back together, taking care not to bend anything. The rubber -bumpers are tricky, but I think there are some notes on the rockbox site -about how to put them on the right way. -

    -Victory at last! You're done! Now go to the rockbox site and update your -firmware, I bet it's out of date! - -

    CONCLUSION

    -

    -In the end, this cost me much less than sending it in to someone -qualified, but was also a hell of a lot scarier. I think I learned a few -things about my Archos though, and I look forward to trying some of the -other mods. -

    -I'm sure there are people out there (real pros) who are horrified at what -I have written. Please, correct any mistakes I have made in this document -so future 'boxers don't have to go through the hours of stress and strain -I did. - -#include "foot.t" diff --git a/www/docs/rocklatin.t b/www/docs/rocklatin.t deleted file mode 100644 index 819a845051..0000000000 --- a/www/docs/rocklatin.t +++ /dev/null @@ -1,95 +0,0 @@ -#define _PAGE_ Rocklatin1 -#include "head.t" - -

    Only for developers... - -

    Background

    -The Archos player comes in two models. One with old LCD and one with new LCD. -(Differences can be seen below). You can't find any difference more than the -LCD, therefor we run the same code on both models. The original software -contains two different mappings from ASCII-character to hardware-LCD. Because -some characters doesn't exist in both hardwares all national characters -are left out in both hardware. -

    The old LCD can have 4 software defined characters, and the new LCD can -have 8 software defined characters. - - - -
    HW layout of old LCD:
    		HW layout of new LCD:
    - -

    What is Rocklatin1

    -Rocklatin1 is based on Winlatin1 (which is identical to Latin1 but some -extra characters). All characters presented in any HW-LCD (i.e. old LCD) -is mapped in Rocklatin1 and some extra characters we find good to use. - - - - -
    Rocklatin1 of old LCD:
    		Rocklatin1 of new LCD:
    -The red characters are characters not defined in the HW-LCD. These characters -are mapped by the software to a software defined character (0-4/8) whenever -they are used. - -

    But what if...

    -...all software defined characters are taken?
    -Well, then a substitute character will be used for that character. - - - - -
    Substitute of old LCD:
    		Substitute of new LCD:
    -The red characters shows where a substitution is made. - -

    -All Rocklatin1 characters between 0x00 and 0x1f are hardcoded to be prioritized. -That means that if a national character is displayed at LCD and an icon -(0x18-0x1f) is to be shown, the character with highest Rocklatin1 value will -be switched to a substitute character. - -

    Accessing hardware

    -The Rockbox software can access a HW-LCD-character by doing a lcd_putc(0x100-0x1ff). That would of course make it 100% hardware depended (=not good). -

    -The Rockbox software can also define 22 own patterns, even though hardware only -allows 4 or 8. The software should of course not try to display more than 4 -or 8 of such characters. This code example shows how to define a pattern: -

    -{
-  unsigned char pattern[]={ 0x0a, 0x00, 0x00, 0x0c,
-                            0x04, 0x04, 0x0e};
-  unsigned char handle;
-
-  handle=lcd_get_locked_pattern();
-  lcd_define_pattern(handle, pattern);
-
-  lcd_putc(x, y, handle);
-
-  ...
-
-  lcd_unlock_pattern(handle);
-}
-
    -The handle is very likely to be between 0x01 to 0x15, which in software will -be handled as a prioritized character (even higher than the icons). - -

    Some notes

    -
      -
    • Displaying the same rocklatin-mapped-character many times at the LCD -only occupies one HW-LCD-mapped character. -
    • If a substitute character is used, the "should-be" character will never -be shown (no flickering screen) until the character is moved or scrolled. -
    • Characters already displayed are only substituted if a prioritized -character is to be displayed. -
    • The software maps the characters circular in order to minimize the -likelyhood to remap the same character very often. -
    • The gifs above is generated with the tool "generate_rocklatin". -
    • Rocklatin character 0x92 is defined as the "cursor" character. -
    • Rocklatin character 0x93-0x95 is only used for substitution (a substitute -character must be a Rocklatin character). -
    • Implementation and design by Kjell Ericson and Mats Lidell (for questions). -
    • Rocklatin1 is based on Winlatin1 because the old LCD happened to have 7 -of the Winlatin1-extra characters (no need to remap/remove those). -
    • If you find any characters identical in old and new HW-LCD that aren't -mapped (and really are useful) you can tell us. -
    - -#include "foot.t" diff --git a/www/docs/rvf.t b/www/docs/rvf.t deleted file mode 100644 index 171319fcca..0000000000 --- a/www/docs/rvf.t +++ /dev/null @@ -1,117 +0,0 @@ -#define _PAGE_ RVF Conversions and Similar -#include "head.t" - -

    Introduction

    -This is a simple tutorial (or, at least, as simply put as possible) on how -to convert your video files to RVF (Rockbox Video File), to be played on -the Archos Recorder / FM Recorder / V2 line. - -

    Other option is to get the GUI Video Conversion Tool from John Wunder, which - can be downloaded from - http://home.ripway.com/2004-2/66978/RockVideoRelease.zip. (Windows users only) - -

    See also Fabian Merki's msi-rvf-gallery, a Java program for - building RVF movies out of individual JPEGs. - -

    How To Convert AVI to RVF

    -

    - This Process Is For Windows Users Only -

      - -
    1. Convert your movie file to an AVI file, uncompressed, and with the size: - 112x64. There are quite a few programs out there that will do this for you, - so I will leave this step up to you. One such program is "BPS Video - Converter" available online. Use google if you need. - -
    2. Download the tools required here: - http://joerg.hohensohn.bei.t-online.de/archos/video/ - Unzip to a PATH, such as C:\RVF, that is easily remembered. - -
    3. Press START on your taskbar, choose RUN and type in the box (minus - quotes): "command" You should now be looking at a command prompt. If you - don't know basic DOS commands, here is what you need to know: -
      - Use 'cd' to change dir (format: cd [dir]) IE: "cd .." to go UP one, "cd - ROCKBOX" to enter a path "ROCKBOX" - -
    4. Navigate to your PATH in DOS prompt, using "cd" as illustrated above. - -
    5. Run the file, avitoyuv, which was in the packet you earlier downloaded, using the format: -
      -	avitoyuv [input.avi] [output.yuv]
-
      - For example, if your AVI movie is called "filename" then you'd put in the following: -
      -	avitoyuv filename.avi filename.yuv
-
      - - OPTIONAL: You can name the output file differently, whatever you specify it - will be called. INFO: This can take long to convert. - -
    6. Now run the file, halftone, which was in the packet you earlier downloaded, using the format: -
      -	halftone [input.yuv] [output.rvf]
-
      - For example, if your YUV output from step 5 is called "filename" then you'd put in the following: -
      -	halftone filename.yuv filename.rvf
-
      - - OPTIONAL: You can name the output differently, again. INFO: When this is - done, a long list will appear on your DOS screen and you will be back at the - command prompt again. - -
    7. Next step is adding sound to your video file. Run the tool avi2wav using the format: -
      -        avi2wav [input.avi] [output.wav]
-
      - For example, if your original file is called "filename" then you'd put in the following: -
      -        avi2wav filename.avi filename.wav
-
      - - OPTIONAL: You can name the output differently. - -
    8. The extracted audio file must be in mp3 format, so you have to convert the WAV file into MP3. - One option to make this is using the LAME codec. You can download the win32 binary from http://mitiok.cjb.net. - One format used with LAME (good quality/size) is: -
      -         lame --preset standard [input.wav] [output.mp3]
-
      - For example, if your audio file is called "filename" then you'd put in the following: -
      -         lame --preset standard filename.wav filename.mp3
-
      - - OPTIONAL: You can name the output differently. Also, you can use other wav to mp3 tool, or even use - other options in the lame command. NOTE: The --preset standard will give you a VBR file, so if you want a - CBR file, just change the preset to --preset cbr [kbps], where [kbps] is the Constant Bit Rate desired. - -
    9. Now we have to merge the sound with the video, so run the rvf_mux tool found - in the packet you've downloaded, using the format: -
      -        rvf_mux [option] [videoinput.rvf] [audioinput.mp3] [output.rvf]
-
      - For example, if your video file from step 6 is called "filename.rvf" and the audio file from step 7 - is called "filename.wav" then you'd put in the following: -
      -        rvf_mux filename.rvf filename.mp3 filename_av.rvf
-
      - - NOTE: You can use any name for the output file, but it's recomended that the name is not the same name - used in the input video file. - You can change the frames per second of Rockbox playback using the -play_fps [fps] option. The default - value is 67.0 fps. - -
    10. Copy the .rvf output to your jukebox, load up a recent daily build and - plugins, and kick back and watch the movie! -
    - -

    -Video tools, player: Jörg Hohensohn -

    -Tutorial: Zakk Roberts -#include "foot.t" diff --git a/www/docs/solderjoints.jpg b/www/docs/solderjoints.jpg deleted file mode 100644 index 916311b89d..0000000000 Binary files a/www/docs/solderjoints.jpg and /dev/null differ diff --git a/www/docs/solderjoints2.jpg b/www/docs/solderjoints2.jpg deleted file mode 100644 index 260a718e63..0000000000 Binary files a/www/docs/solderjoints2.jpg and /dev/null differ diff --git a/www/docs/solderjoints2_t.jpg b/www/docs/solderjoints2_t.jpg deleted file mode 100644 index 12a846c1fe..0000000000 Binary files a/www/docs/solderjoints2_t.jpg and /dev/null differ diff --git a/www/docs/solderjoints_t.jpg b/www/docs/solderjoints_t.jpg deleted file mode 100644 index cfe1dc4720..0000000000 Binary files a/www/docs/solderjoints_t.jpg and /dev/null differ diff --git a/www/docs/tools.t b/www/docs/tools.t deleted file mode 100644 index 4fdbb26b93..0000000000 --- a/www/docs/tools.t +++ /dev/null @@ -1,407 +0,0 @@ -#define _PAGE_ Useful mp3 and jukebox related tools -#include "head.t" - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

    Jukebox Synchronization

    NameLinuxWindowsOpen SourceFreeware
    Jukebox Synchronizer X X
    Jukebox Manager X X
    ABSync X X
    TreeComp X X
    rsyncXXX 
    UnisonXXX 

    MP3 Ripping & Encoding

    NameLinuxWindowsOpen SourceFreeware
    Exact Audio Copy (Cardware) -  X  
    CDex XX 
    cdparanoiaX X 
    cdda2wavX X 
    Audiograbber X X
    dbPowerAmp Music Converter X X
    LameXXX 

    MP3 Cutting, Splitting, Merging

    NameLinuxWindowsOpen SourceFreeware
    mp3DirectCut X X
    MP3Slixer XX 
    MusiCutter X X
    MP3Merge X X
    Split MP3 X X
    MP3 SpltXXX 
    mp3cutXXX 
    mp3Trim (free version limits file length to approx. 7 minutes) X X

    MP3 Tagging & Organization

    NameLinuxWindowsOpen SourceFreeware
    The GodFather X X
    Mp3TagStudio (Shareware) X  
    MP3BookHelper XX 
    MP3Tag X X
    MP3TagTools XX 
    Tag&Rename (Shareware) X  
    ID3-TagIT X X
    MP3 ID3Tag Renamer (Emailware) X  
    ID3Browse X X
    MediaMonkey Standard X X
    EasyTAGX X 
    mp3info - X X 
    mp3getcddb - X X 
    mp3rename - X X 
    Media Tagger -  X X

    MP3 Repairing & Analyzing

    NameLinuxWindowsOpen SourceFreeware
    VBRfixXXX 
    MP3FixerXXX 
    MP3Utility X X
    EncSpot Basic X X
    MP3 Gain XX 

    Disk Utilities

    NameLinuxWindowsOpen SourceFreeware
    File Recovery X X
    h2format (formats FAT32 > 32GB, German docs only) X X
    Jukebox Utility DiskOS independentX 

    Video Tools

    NameLinuxWindowsOpen SourceFreeware
    Jörg's Video Tools XX 
    GUI Video Conversion Tool X X
    Rockbox Video Viewer & Gallery MakerXXX 
    - -#include "foot.t" -- cgit v1.2.3