summaryrefslogtreecommitdiffstats
path: root/manual/chapter6/advanced_topics.tex
blob: 97165d68550548feb028e6c3462c6695bccaa2fa (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
\chapter{Advanced Topics}
\newpage
\section{\label{ref:CustomisingUI}Customising the userinterface}
\subsection{\label{ref:GettingExtras}Getting Extras (Fonts,Languages)}
Rockbox supports custom fonts (for the Recorder and Ondio only) and a number of different languages. Rockbox 2.4 comes with 41 fonts and 24 languages already included. If new fonts and language files have been created, then they will be found at \url{http://www.rockbox.org/fonts/} and \url{http://www.rockbox.org/lang/}.

\subsection{\label{ref:LoadingForts}Loading Fonts (Recorder, Ondio)}
Rockbox can load fonts dynamically. Simply copy the .fnt file to the
disk and ``play'' them in the directory browser or select \textbf{General Settings {\textgreater} Fonts} from the Main Menu .

If you want a font to be loaded automatically every time you start up,
it must be located in the \textbf{/.rockbox }folder and the file name
must be at most 24 characters long.

Any BDF font file up to 16 pixels high should be usable with Rockbox. To
convert from .bdf to .fnt, use the convbdf tool. This tool can be found
on the Rockbox website 
(Linux: \url{http://www.rockbox.org/fonts/convbdf}, Windows: \url{http://www.rockbox.org/fonts/convbdf.exe}).

\subsection{\label{ref:Loadinglanguages}Loading Languages}
Rockbox can load language files at runtime. Simply copy the .lng file
(do not use the .lang file) to the Jukebox and
``play'' it in the Rockbox directory browser
or select \textbf{General Settings {}-{\textgreater} Languages }from
the Main Menu. 

If you want a language to be loaded automatically every time you start
up, it must be located in the \textbf{/.rockbox }folder and the file
name must be a maximum of 24 characters long.

Rockbox supports many different languages. You can get .lng files at
\url{http://www.rockbox.org/lang/}. 
Currently all of these languages are included in the Rockbox
distribution.

If your language is not yet supported and you want to write your own
language file,  follow these instructions:

\begin{itemize}
\item Copy the\url{./ http://www.rockbox.org/lang/english.lang }file and start filling in the ``new:'' lines. 
\item Name your file {\textless}language{\textgreater}.lang, where
{\textless}language{\textgreater} is the local name for your language. i.e. svenska.lang, francais.lang etc. 
\item When you are done, submit your .lang file to Rockbox patch
tracker.
(\url{http://sourceforge.net/tracker/?group_id=44306&atid=439120})
\end{itemize}

\section{\label{ref:ConfiguringtheWPS}Configuring the WPS}

\subsection{Description / General Info}

\begin{itemize}
\item The Custom While Playing Screen (WPS) display is used on both the
Player and Recorder as a means to customise the WPS to the
user's likings.
\item After editing the .wps file, ``play'' it to make it take effect.
\item The file may be 2 lines long for the Player, and 13 lines for the
Recorder.
\item All characters not preceded by \% are displayed as typed.
\item Lines beginning with \# are comments and will be ignored.
\end{itemize}

\subsection{File Location}
Custom WPS files may be located anywhere on the drive. The only
restriction is that they must end in .wps. When PLAY is pressed on a
.wps file, it will be used for future WPS screens. If the
``played'' .wps file is located in the
/.rockbox folder, it will be remembered and used after reboot. The .wps
filename must be no more than 24 characters long for it to be
remembered.

\subsection{Tags}

\begin{itemize}
\item {\bfseries
ID3 Info Tags:}

\%ia : ID3 Artist

\%ic : ID3 Composer

\%id : ID3 Album Name

\%ig : ID3 Genre Name

\%in : ID3 Track Number

\%it : ID3 Track Title

\%iy : ID3 Year

\%iv : ID3 Version (1.0, 1.1, 2.2, 2.3, 2.4 or empty if no id3 tag)
\item {\bfseries
Battery Info:}

\%bl : Show numeric battery level in percent

\%bt : Show estimated battery time left
\item {\bfseries
File Info Tags:}

\%fb : File Bitrate (in kbps)

\%ff : File Frequency (in Hz)

\%fm : File Name

\%fn : File Name (without extension)

\%fp : File Path

\%fs : File Size (In Kilobytes)

\%fv : ``(vbr)'' if variable bit rate or ``'' if constant bit rate

\%d1 : First directory from end of file path.

\%d2 : Second directory from end of file path.

\%d3 : Third directory from end of file path.

Example for the the \%dN commands: If the path is /Rock/Kent/Isola/11
{}-747.mp3, \%d1 is ``Isola'', \%d2 is ``Kent'', \%d3 is ``Rock''.
\end{itemize}

\begin{itemize}
\item {\bfseries
Playlist/Song Info Tags:}

\%pb : Progress Bar 

\begin{itemize}
\item[] {
Player: This will display a 1 character
``cup'' that empties as the song progresses.}

Recorder: This will replace the entire line with a progress bar.
\end{itemize}
\%pf : Player: Full{}-line progress bar + time display

\%pc : Current Time In Song

\%pe : Total Number of Playlist Entries

\%pm : Peak Meter (Recorder only) {}- the entire line is used as volume
peak meter.

\%pn : Playlist Name (Without path or extension)

\%pp : Playlist Position

\%pr : Remaining Time In Song

\%ps : Shuffle. Shows 's' if shuffle
mode is enabled.

\%pt : Total Track Time

\%pv : Current volume
\item {\bfseries
Conditional Tags (If/Else block):}

 \%?xx{\textless}{\textbar}{\textgreater} : Conditional: if the tag
specified by ``xx'' has a value, the text
between the ``{\textless}'' and the ``{\textbar}'' is displayed, else the text
between the ``{\textbar}'' and the
``{\textgreater}'' is displayed. The else part is optional, so the ``{\textbar}'' does not have to be specified if no else part is desired. The conditionals
nest, so the text in the if and else part can contain all \% commands,
including conditionals.
\end{itemize}
\begin{itemize}
\item {\bfseries
Next Song info}

You can display information about the next song {}- the song that is
about to play after the one currently playing (unless you change the
plan). 

If you use the upper{}-case versions of the
three tags: F, I and D, they will instead refer to the next song
instead of the current one. Example: \%Ig is the genre name used in the
next song and \%Ff is the mp3 frequency. 

Take note that the next song information WILL NOT be available at all
times, but will most likely be available at the end of a song. We
suggest you use the conditional display tag a lot when displaying
information about the next song! 
\item {\bfseries
Alternating sublines}

It is possible to group items on each line into 2 or more groups or
``sublines''. Each subline will be displayed
in succession on the line for a specified time, alternating
continuously through each defined subline. 

Items on a line are broken into sublines with the semicolon
';' character. The display time for
each subline defaults to 2 seconds unless modified by using the
'\%t' tag to specify an alternate
time (in seconds and optional tenths of a second) for the subline to be
displayed. 

Subline related special characters and tags: 

;  : Split items on a line into separate sublines

\%t  : Set the subline display time. The
'\%t' is followed by either integer
seconds (\%t5), or seconds and tenths of a second (\%t3.5).

Each alternating subline can still be optionally scrolled while it is
being displayed, and scrollable formats can be displayed on the same
line with non{}-scrollable formats (such as track elapsed time) as long
as they are separated into different sublines. 
\item {\bfseries
Other Tags:}

\%\% : Display a '\%'

\%{\textless} : Display a
'{\textless}'

\%{\textbar} : Display a '{\textbar}'

\%{\textgreater} : Display a
'{\textgreater}'

\%s : Indicate that the line should scroll. Can occur anywhere in a line
(given that the text is displayed; see conditionals above). You can
specify up to 10 scrolling lines. Scrolling lines can not contain
dynamic content such as timers, peak meters or progress bars.
\end{itemize}
{\bfseries
Example File}

\%s\%pp/\%pe: \%?it{\textless}\%it{\textbar}\%fn{\textgreater} {}-
\%?ia{\textless}\%ia{\textbar}\%d2{\textgreater} {}-
\%?id{\textless}\%id{\textbar}\%d1{\textgreater}

\%pb\%pc/\%pt

That is, ``tracknum {}- title [artist,
album]'', where most fields are only displayed if
available. Could also be rendered as
``filename'' or ``tracknum {}-title [artist]''.

{\bfseries
Default}

If you haven't selected a .wps file in the /.rockbox
directory, you get the hard coded layout. The default WPS screen for
Players is:

\%s\%pp/\%pe: \%?it{\textless}\%it{\textbar}\%fn{\textgreater} {}-
\%?ia{\textless}\%ia{\textbar}\%d2{\textgreater} {}-
\%?id{\textless}\%id{\textbar}\%d1{\textgreater}

\%pc\%?ps{\textless}*{\textbar}/{\textgreater}\%pt

And for the Recorder and Ondio:

\%s\%?it{\textless}\%?in{\textless}\%in.
{\textbar}{\textgreater}\%it{\textbar}\%fn{\textgreater}

\%s\%?ia{\textless}\%ia{\textbar}\%?d2{\textless}\%d2{\textbar}(root){\textgreater}{\textgreater}

\%s\%?id{\textless}\%id{\textbar}\%?d1{\textless}\%d1{\textbar}(root){\textgreater}{\textgreater}
\%?iy{\textless}(\%iy){\textbar}{\textgreater}

\%pc/\%pt [\%pp:\%pe]

\%fbkBit \%?fv{\textless}avg{\textbar}{\textgreater}
\%?iv{\textless}(id3v\%iv){\textbar}(no id3){\textgreater}

\%pb

\%pm

\section{\label{ref:SettingsFile}Making your own settings file}
A .cfg file is used to load settings from a plain text file. A .cfg file
may reside anywhere on the hard disk. The only restriction is that the
filename must end in .cfg

Hint: Use the ``Write .cfg file'' feature
(Main Menu{}-{\textgreater} General Settings) to save the current
settings, then use a text editor to customize the settings file.

{\bfseries
Format Rules}

\begin{itemize}
\item Format: setting: value
\item Each setting must be on a separate line.
\item Lines starting with \# are ignored.
\end{itemize}
{\bfseries
Settings    (allowed values) [unit]}

volume   (0 {}- 100)

bass    ({}-15 {}- 15)

treble    ({}-15 {}- 15)

balance   ({}-100 {}- 100)

channels   (stereo, stereo narrow, stereo wide, mono, mono left,

     mono right, karaoke)

shuffle   (on, off)

repeat   (off, all, one)

play selected  (on, off)

resume   (off, ask, ask once, on)

scan min step  (1, 2, 3, 4, 5, 6, 8, 10, 15, 20, 25, 30, 45, 60) [secs]

scan accel   (0 {}- 15) [double scan speed every X seconds]

antiskip   (0 {}- 7) [seconds]

volume fade  (on, off)

sort case   (on, off)

show files   (all, supported, music, playlists)

follow playlist  (on, off)

playlist viewer icons

    (on, off)

playlist viewer track display

    (on, off)

recursive directory insert

    (on, off)

scroll speed  (0 {}- 15) 

scroll delay   (0 {}- 250) [1/10s]

scroll step   (1 {}- 112) [pixels]

bidir limit   (0 {}- 200) [\% of screen width]

contrast   (0 {}- 63)

backlight timeout  (off, on, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 15, 20, 25,
30, 

     45, 60, 90) [seconds]

backlight when plugged 

    (on, off)

disk spindown  (3 {}- 254) [seconds]

battery capacity  (1500 {}- 2400) [mAh]

idle poweroff  (off, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 15, 30, 45, 60)     
 [minutes]

lang    (/path/filename.lng)

wps    (/path/filename.wps)

autocreate bookmarks (on, off)

autoload bookmarks (on, off)

use most{}-recent{}-bookmarks

    (on, off)

talk dir   (off, number, spell, hover)

talk file   (off, number, spell, hover)

talk menu   (off, on)

{\bfseries
Recorder{}-specific settings}

loudness   (0 {}- 17)

super bass    (on, off)

auto volume  (off, 0.02, 2, 4, 8) [seconds]

MDB enable  (on, off)

MDB strength  (0 {--} 127) [dB]

MDB harmonics  (0 {--} 100) [\%]

MDB center frequency (20{}-300) [Hz]

MDB shape   (50{}-300) [Hz]

peak meter release (1 {}- 126)

peak meter hold  (off, 200ms, 300ms, 500ms, 1, 2, 3, 4, 5, 6, 7, 8,

      9, 10, 15, 20, 30, 1min)

peak meter clip hold (on, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 15, 20, 25, 30,


     45, 60, 90, 2min, 3min, 5min, 10min, 20min,

     45min, 90min)

peak meter busy  (on, off)

peak meter dbfs  (on, off) (on = dbfs, off = linear)

peak meter min  (0 {}- 89) [dB] or (0 {}- 100) [\%]

peak meter max  (0 {}- 89) [dB] or (0 {}- 100) [\%]

statusbar   (on, off)

scrollbar   (on, off)

volume display  (graphic, numeric)

battery display  (graphic, numeric)

time format   (12hour, 24hour)

font    (/path/filename.fnt)

invert    (on, off)

deep discharge  (on, off)

trickle charge  (on, off)

disk poweroff  (on, off)

rec quality   (0 {}- 7) (0=smallest size, 7=highest quality)

rec frequency  (48, 44, 32, 24, 22, 16) [kHz]

rec source    (mic, line, spdif)

rec channels  (mono, stereo)

rec mic gain  (0 to 15)

rec left gain  (0 to 15)

rec right gain  (0 to 15)

editable recordings (on,off)

rec timesplit  (off, 00:05, 00:10, 00:20, 00:30, 01:00, 01:12, \newline
     01:20, 02:00, 04:00, 06:00, 08:00, 16:00,\newline
     24:00) [hh:mm]

pre{}-recording time (off, 1{}-30) [secs]

rec directory  (/recordings, current) 

{\bfseries
FM recorder specific settings}

\textmd{force fm mono  (on,off)}

\textbf{Example File}

volume: 70

bass: 11

treble: 12

balance: 0

time format: 12hour

volume display: numeric

show files: supported

wps: /.rockbox/car.wps

lang: /.rockbox/afrikaans.lng

\section{\label{ref:PartISection1}Differences between binaries}
There are 3 different types of firmware binaries from Rockbox website. Current Version, Daily Builds and Bleeding Edge.

\begin{itemize}
\item \begin{itemize}
\item The current version is the latest stable version developed by the
Rockbox Team. It's free of known critical bugs and works with Archos
Jukebox Player/Studio, Recorders and Ondio devices.  It is available
from 
\url{http://www.rockbox.org/download/}.
\item The Daily Build is a development version of Rockbox. It supports all new features and patches developed since last stable version. It may also contain bugs! This version is generated automatically every day and can be found at
\url{http://www.rockbox.org/daily.shtml}.
\item Bleeding edge builds are the same as the Daily build, but built
from the latest development code every 20 minutes. These builds are for
people who want to test the code that developers just checked in.
\end{itemize}
\end{itemize}
There are binaries for different Jukebox models: 

\begin{itemize}
\item \begin{itemize}
\item The Player version is suitable for Archos Jukebox 5000, 6000 and
all Studio models.
\end{itemize}
\end{itemize}
\begin{itemize}
\item \begin{itemize}
\item If you have a recorder with cylindrically rounded bumpers, you
need the ``regular'' recorder version. 
\item FM Recorders are models with a FM radio.
\item The V2 recorder is a recorder in an FM Recorder form factor, but
without radio. 
\item The 8mb version requires a hardware hack, where the RAM chips are
replaced. 
\item  The Ondio builds come with and without radio support, for the
Ondio FM and SP respectively.
\end{itemize}
\end{itemize}
If in doubt as to which version to use, the table on page
\pageref{ref:Jukeboxtypetable} may be of assistance.

Note: All references in this manual to
``Recorder'' apply equally to the FM Recorder
unless otherwise specified.

\section{\label{ref:FirmwareLoading}Firmware Loading}
When your Jukebox powers on, it loads the Archos firmware in ROM, which
automatically checks your Jukebox hard disk's root folder for a file
named \textbf{archos.mod} (on the player version) or
\textbf{ajbrec.ajz} (on the recorder version). Note that Archos
firmware can only read the first ten characters of each file name in
this process, so don't rename your old firmware files with names like
archos.mod.old and so on, because it's possible that the Jukebox will
load a file other than the one you intended.

\section{\label{ref:PartISection4}Using ROLO (Rockbox loader)}
Rockbox is able to load and start another firmware file without
rebooting. You just press PLAY on an .ajz (Recorder, Ondio) or .mod
(Player) file. This can be used to test new firmware versions without
deleting your current version, or to load the original Archos firmware
(you have to download the appropriate file from
Archos' website). 

\section{\label{ref:Rockboxinflash}Rockbox in flash (Recorder, Ondio)}
\textbf{FLASHING ROCKBOX IS OPTIONAL!} It is not required for using
Rockbox on your Jukebox Recorder. Please read the whole section
thoroughly before flashing.

\subsection{\label{ref:PartISection61}Introduction}
Flashing in the sense used here and elsewhere in regard to Rockbox means
reprogramming the flash memory of the Jukebox unit. Flash memory
(sometimes called ``Flash ROM'') is a type of
non{}-volatile memory that can be erased and reprogrammed in circuit. It is a variation of electrically erasable
programmable read{}-only memory (EEPROM). 

A from the factory Jukebox comes with the Archos firmware flashed. It is
possible to replace the built{}-in software with Rockbox. 

Terminology used in the following:\newline
\textbf{Firmware} means the flash ROM content as a whole.\newline
\textbf{Image} means one operating software started from there. 

By reprogramming the firmware,  the Jukebox will boot much faster. The
Archos boot loader seems to take forever compared to the Rockbox
version. In fact, the Rockbox boot loader is so fast that it has to
wait for the disk to spin up.  The flashing procedure is a bit involved
for the first time, updates are very simple later on. 

\subsection{\label{ref:Method}Method}
The replaced firmware will host a bootloader and 2 images. This is made
possible by compression. The first is the
``permanent'' backup. The second is the
default image to be started.  The former is only used when you hold the
F1 key during start, and is the original Archos firmware, the second is
a current build of Rockbox. This second image is meant to be
reprogrammed whenever a Rockbox upgrade is performed.

There are two programming tools supplied: 

\begin{itemize}
\item The first one is called \textbf{firmware\_flash.rock} and is used
to program the whole flash with new content.  It can also be used to
revert back to the original firmware that is backed up as part of this
procedure.  This tool will only be needed once, and can be viewed as
``formatting'' the flash with the desired image structure. 
\item The second one is called \textbf{rockbox\_flash.rock }and is used
to reprogram only the second image. If the resulting programmed
firmware image is not operational, it is
possible to hold down the F1 key while booting to start the Jukebox
with the Archos firmware and Rockbox booted from disk to reinstall a
working firmware image. 
\end{itemize}

\subsubsection{\label{ref:PartISection63}Risks}
Well, is it dangerous? Yes, certainly, like programming a
mainboard BIOS, CD/DVD drive firmware,
mobile phone, etc. If the power fails, the chip malfunctions while
programming or particularly if the programming software malfunctions,
your Jukebox may stop functioning. The Rockbox team take no
responsibility of any kind {}- do this at your own risk. 

However, the code has been extensively tested and is known to work well.
 The new firmware file is completely read before it starts programming,
there are a lot of sanity checks. If any fail, it will not program.
There is no reason why such low level code should behave differently on
your Jukebox. 

There's one ultimate safety net to bring back Jukeboxes
with even completely garbled flash content: the UART boot mod, which in
turn requires the serial mod. This 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 during development,
else Rockbox in flash wouldn't have been possible.
Extensive development effort went into the development 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
(\textbf{firmware\_flash.rock}) for reflashing the firmware.

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.  

The flashing software is very paranoid about making sure that the
correct flash version is being installed.  If the wrong file is used,
it will simply refuse to flash the Jukebox.

About the safety of operation: Since the Rockbox boot code gives ``dual
boot'' capability, the Archos firmware is still there when you hold F1
during startup. So even if you have problems with Rockbox from flash, you can still use
the Jukebox, reflash the second image with an updated Rockbox copy,
etc. 

The flash chip being used by Archos is specified for 100,000 cycles, so
it's very unlikely that flashing it will wear it out. 

\subsection{\label{ref:Requirements}Requirements}
You need two things: 

\begin{itemize}
\item The first is a Recorder or FM model, or an Ondio SP or FM. Be sure
you're using the correct package, they differ
depending on your precise hardware! The technology works for the Player
models, too. Players can also be flashed, but Rockbox does not run
cold{}-started on those, yet. 
\item 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 option for
flashing if this is the case is to solder in the right chip
(SST39VF020), preferably with the firmware already in. If the chip is
blank, you'll need the UART boot mod as well. 
\end{itemize}
\subsubsection{\label{ref:FlashingProcedure}Flashing Procedure}
Here are step{}-by{}-step instructions on how to flash and update to a
current build.  It is assumed that you can install and operate Rockbox
the usual way. The flashing procedure has a lot of failsafes, and will
check for correct model, file, etc. {}- if something is incompatible it
just won't flash, that's all. 

Now here are the steps: 

\textbf{Preparation}

Install (with all the files, not just the .ajz) and use the current
daily build you'd like to have. Enable any voice
features that are helpful throughout the process, such as menus and
filename spelling. Set the file view to show all files, with  the menu
option \textbf{General Settings {}-{\textgreater} File View
{}-{\textgreater} Show Files} set to ``all''.
Have the Jukebox nicely charged to avoid
running out of power during the flash write.  Keep the Jukebox plugged
into the charger until flashing is complete.

{\bfseries
Backup }

Backup the existing flash content.  This is not an essential part of the
procedure, but is strongly recommended since you will need these files
if you wish to reverse the flashing procedure, or if you need to update
the bootloader (as opposed to the firmware) in the future.  Keep them
safe!

Access the main menu by pressing F1 then select \textbf{Info
{}-{\textgreater} Debug}.  Select the first entry, \textbf{Dump ROM
contents}, by pressing Play one more time. The disk should start to
spin. Wait for it to settle down, then plug in the USB cable  to copy
the dump file this has just been created to your PC. The main folder of
your Jukebox now should contain two strange .bin files. Copy the larger
one named
\textbf{internal\_rom\_2000000{}-203FFFF.bin}
to a safe place, then delete them both from the box. 

{\bfseries
Copy the new flash content file to your box }

Depending on your model (recorder, FM, V2 recorder), download one of the
3 packages: 

\url{http://joerg.hohensohn.bei.t-online.de/archos/flash/flash_rec.zip}

\url{http://joerg.hohensohn.bei.t-online.de/archos/flash/flash_fm.zip}

\url{http://joerg.hohensohn.bei.t-online.de/archos/flash/flash_v2.zip}
\url{http://joerg.hohensohn.bei.t-online.de/archos/flash/flash_v2.zip}

\url{http://joerg.hohensohn.bei.t-online.de/archos/flash/flash_v2.zip}

\url{http://joerg.hohensohn.bei.t-online.de/archos/flash/flash_ondiosp.zip}

\url{http://joerg.hohensohn.bei.t-online.de/archos/flash/flash_ondiofm.zip}

The zip archives contain two .bin files each. Those firmware*.bin files
are all we want, copy them to the root directory of your box. The names
differ depending on the model, the flash
plugin will pick the right one, no way of
doing this wrong. 

{\bfseries
Install the Rockbox
Bootloader (``formatting'' the flash)}

This procedure is only necessary the first time you flash Rockbox. 
Unplug the USB cable again, then select \textbf{Browse
}\textbf{Plugins}\textbf{ } from the main menu (F1).  Locate \textbf{firmware\_flash.rock}, and start it with PLAY.  Rockbox now displays an info screen, press F1 to acknowledge it and start a file check. Again wait for the disk to
settle, then press F2 to proceed to a warning message (if the plugin
has exited, you don't have the proper file) and F3 to actually program
the file. This takes maybe 15 seconds, wait for the disk to settle
again. Then press a key to exit the plugin.

{\centering\itshape
  [Warning: Image ignored] % Unhandled or unsupported graphics:
%\includegraphics[width=3.609cm,height=2.062cm]{images/rockbox-manual-img75.png}
     [Warning: Image ignored] % Unhandled or unsupported graphics:
%\includegraphics[width=3.669cm,height=2.097cm]{images/rockbox-manual-img76.png}
 \textmd{  }  [Warning: Image ignored]
% Unhandled or unsupported graphics:
%\includegraphics[width=3.739cm,height=2.136cm]{images/rockbox-manual-img77.png}
 \newline
Flashing boot loader in 3 easy steps
\par}

{\bfseries
\label{ref:FlashingRockbox}Install the Rockbox binary in flash}

All the above was necessary only once, although there will not be any
obvious difference (other than the Archos firmware loading a bit more quickly)
after the step above is complete.  Next install the actual Rockbox firmware thatwill be used from ROM.  This is how Rockbox will be updated when
installing a new release from now on. 

\begin{itemize}
\item Unpack the whole build that you are installing onto the Jukebox,
including plugins and support files.  This can be done using the Windows setup program to install the new version onto the Jukebox.
\item Test the build you are going to flash by playing the .ajz file so
that ROLO loads it up.  This puts the firmware in memory without
changing your flash, so you can check that everything is working.  If
you have just installed the bootloader (see above) then this will happen automatically as the existing Archos firmware loads the .ajz that you have just installed.  If upgrading ROMbox, this step \textbf{must }be carried out since Rockbox cannot overwrite the ROM while it is running from it.  
\item Play the .ucl file, which is usually found in the
\textbf{/.rockbox} directory, this will kick off the
\textbf{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 begins programming, there is no need for warning this time. If it
goes wrong, you'll still have the permanent image. 

{\centering\itshape
  [Warning: Image ignored] % Unhandled or unsupported graphics:
%\includegraphics[width=3.53cm,height=2.016cm]{images/rockbox-manual-img78.png}
 \textmd{  }  [Warning: Image ignored]
% Unhandled or unsupported graphics:
%\includegraphics[width=3.528cm,height=2.016cm]{images/rockbox-manual-img79.png}
 \newline
Using rockbox\_flash to update your boot firmware
\par}
\item It is possible that you could get an ``Incompatible
Version'' error if the plugin interface has changed since
you last flashed Rockbox. This means you are 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\textbf{ ajbrec.ajz }file. Then you are consistent and can play
\textbf{rockbox.ucl}. 
\item When done, you can restart the box and hopefully your new Rockbox
image. 
\end{itemize}
UCLs for the latest Recorder and FM firmware are included in Rockbox 2.4
and also the daily builds.

\subsection{\label{ref:KnownIssuesAndLimits}Known Issues and Limitations}
There are two variants as to how the Jukebox starts, which is why there
are normal and \_norom firmware files. The vast majority of Jukeboxes
all have the same boot ROM content, but some have different 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 \_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, and can be started by pressing  F3+ON. Using this the box can
be reprogrammed via serial if the UART mod has been applied and the
first \~{}2000 bytes of the flash are OK. 

\subsubsection{ROMbox}
ROMbox is a flashable version of Rockbox that is
uncompressed and runs directly from the flash chip rather than being
copied into memory first.  The advantage of this is that memory that
would normally be used for storing the Rockbox code can be used for
buffering MP3s instead, resulting in less disk
spin{}-ups and therefore longer battery life
 Unfortunately being uncompressed, ROMbox requires more space in flash
than Rockbox and will therefore not fit in the space that is left on an
FM recorder.  ROMbox therefore runs on the V1 and V2 recorder models
only.

The procedure for flashing ROMbox is identical to the procedure for
flashing Rockbox as laid out on page \pageref{ref:FlashingRockbox}. 
The only difference is that the file to install is called
\textbf{rombox.ucl}.  ROMbox is included automatically with rockbox 2.4
and all the current daily builds, so the procedure is identical
otherwise.