summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter D'Hoye <peter.dhoye@gmail.com>2007-12-17 22:27:19 +0000
committerPeter D'Hoye <peter.dhoye@gmail.com>2007-12-17 22:27:19 +0000
commit0506ec7e8f6f9485024697b2eb5416c1a917e144 (patch)
tree821bc9a36ba55748eb16cfe4f865c7a40235b9c5
parent760c1ba5f076440c02b15f2304a82dfc68db2e88 (diff)
downloadrockbox-0506ec7e8f6f9485024697b2eb5416c1a917e144.tar.gz
rockbox-0506ec7e8f6f9485024697b2eb5416c1a917e144.zip
Accept FS #8323 by David Bishop: always use the term bootloader
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@15951 a1c6a512-1295-4272-9138-f99709370657
-rw-r--r--manual/advanced_topics/archos-flashing.tex12
-rw-r--r--manual/getting_started/iaudio_install.tex2
-rw-r--r--manual/getting_started/installation.tex26
-rw-r--r--manual/getting_started/iriver_install.tex32
4 files changed, 36 insertions, 36 deletions
diff --git a/manual/advanced_topics/archos-flashing.tex b/manual/advanced_topics/archos-flashing.tex
index 3f72158471..747fd5c0a4 100644
--- a/manual/advanced_topics/archos-flashing.tex
+++ b/manual/advanced_topics/archos-flashing.tex
@@ -19,14 +19,14 @@ Now, you can add Rockbox to the built-in software.
19\end{description} 19\end{description}
20 20
21By reprogramming the firmware, we can boot much faster. \playerman\ has an 21By reprogramming the firmware, we can boot much faster. \playerman\ has an
22unnecessary slow boot loader, versus the boot time for Rockbox is much faster 22unnecessary slow bootloader, versus the boot time for Rockbox is much faster
23than the disk spin-up, in fact it has to wait for the disk. Your boot time will 23than the disk spin-up, in fact it has to wait for the disk. Your boot time will
24be as quick as a disk spin-up (e.g. 4 seconds from power-up until resuming 24be as quick as a disk spin-up (e.g. 4 seconds from power-up until resuming
25playback). 25playback).
26 26
27\subsection{Method} 27\subsection{Method}
28 28
29The replaced firmware will host a boot loader and 2 images. This is possible by 29The replaced firmware will host a bootloader and 2 images. This is possible by
30compression. The first is the \emph{permanent} backup, not to be changed any 30compression. The first is the \emph{permanent} backup, not to be changed any
31more.The second is the default one to be started, the first is only used when 31more.The second is the default one to be started, the first is only used when
32you hold the \opt{recorder,recorderv2fm}{\ButtonFOne}\opt{ondio}{\ButtonLeft}\opt{player}{\ButtonLeft} -key during start. Like supplied here, the first image 32you hold the \opt{recorder,recorderv2fm}{\ButtonFOne}\opt{ondio}{\ButtonLeft}\opt{player}{\ButtonLeft} -key during start. Like supplied here, the first image
@@ -57,7 +57,7 @@ There are two programming tools supplied:
57 57
58The non-user tools are in the \fname{flash} subdirectory of the CVS source 58The non-user tools are in the \fname{flash} subdirectory of the CVS source
59files. There's an authoring tool which composed the firmware file with the 59files. There's an authoring tool which composed the firmware file with the
60boot loader and the 2 images. The boot loader project, a firmware extraction 60bootloader and the 2 images. The bootloader project, a firmware extraction
61tool, the plugin sources, and the tools for the UART boot feature: a monitor 61tool, the plugin sources, and the tools for the UART boot feature: a monitor
62program for the box and a PC tool to drive it. Feel free to review the sources 62program for the box and a PC tool to drive it. Feel free to review the sources
63for all of it, but be careful when fooling around with powerful toys! 63for all of it, but be careful when fooling around with powerful toys!
@@ -138,7 +138,7 @@ Long version, step by step procedure:
138 you want to restore the flash contents. 138 you want to restore the flash contents.
139\item Download the correct package for you model. Copy one or two files of it to 139\item Download the correct package for you model. Copy one or two files of it to
140 your box: \fname{firmware\_*.bin} (name depends on your model) into the root 140 your box: \fname{firmware\_*.bin} (name depends on your model) into the root
141 directory (the initial firmware for your model, with the boot loader and the 141 directory (the initial firmware for your model, with the bootloader and the
142 Archos image). There now is also a \_norom variant, copy both, the plugin will 142 Archos image). There now is also a \_norom variant, copy both, the plugin will
143 decide which one is required for your box. 143 decide which one is required for your box.
144\item Enter the debug menu and select the hardware info screen. Check your flash 144\item Enter the debug menu and select the hardware info screen. Check your flash
@@ -230,7 +230,7 @@ and now preferred one. Use this if available.
230 230
231If you like or have to, you can also flash the Archos image as the second one. 231If you like or have to, you can also flash the Archos image as the second one.
232E.g. in case Rockbox from flash doesn't work for you. This way you keep the dual 232E.g. in case Rockbox from flash doesn't work for you. This way you keep the dual
233boot loader and you can easily try different later. The \fname{.ucl} of the Archos 233bootloader and you can easily try different later. The \fname{.ucl} of the Archos
234firmware is included in the package. 234firmware is included in the package.
235 235
236\subsection{Restoring the original firmware} 236\subsection{Restoring the original firmware}
@@ -253,7 +253,7 @@ There are two variants of how the boxes starts, therefore the normal and the
253\_norom firmware files. The vast majority of the \daps\ all have the same boot 253\_norom firmware files. The vast majority of the \daps\ all have the same boot
254ROM content, differentiation comes later by flash content. Rockbox identifies 254ROM content, differentiation comes later by flash content. Rockbox identifies
255this boot ROM with a CRC value of 0x222F in the hardware info screen. \opt{recorder,recorderv2fm}{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 255this boot ROM with a CRC value of 0x222F in the hardware info screen. \opt{recorder,recorderv2fm}{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
256 \_norom firmware that has a slightly different boot loader.} 256 \_norom firmware that has a slightly different bootloader.}
257Without a boot ROM there is no UART boot safety net. To compensate for that as 257Without a boot ROM there is no UART boot safety net. To compensate for that as
258much as possible the MiniMon monitor is included, it starts with \opt{recorder,recorderv2fm}{\ButtonFThree+\ButtonOn}\opt{ondio}{\ButtonRight+\ButtonOff}\opt{player}{\ButtonRight+\ButtonOn}. 258much as possible the MiniMon monitor is included, it starts with \opt{recorder,recorderv2fm}{\ButtonFThree+\ButtonOn}\opt{ondio}{\ButtonRight+\ButtonOff}\opt{player}{\ButtonRight+\ButtonOn}.
259Using that the box can be reprogrammed via serial if the first 2000 bytes of the 259Using that the box can be reprogrammed via serial if the first 2000 bytes of the
diff --git a/manual/getting_started/iaudio_install.tex b/manual/getting_started/iaudio_install.tex
index cdab94b925..7d66947aa2 100644
--- a/manual/getting_started/iaudio_install.tex
+++ b/manual/getting_started/iaudio_install.tex
@@ -1,7 +1,7 @@
1\fixme{This is merely a copy of the wiki page IaudioBoot, so this section needs 1\fixme{This is merely a copy of the wiki page IaudioBoot, so this section needs
2a more natural language and also error checking by Iaudio owners.} 2a more natural language and also error checking by Iaudio owners.}
3 3
4The \playername{} has a built-in boot loader which performs the 4The \playername{} has a built-in bootloader which performs the
5firmware update, and can also access the hard drive via USB. Therefore the 5firmware update, and can also access the hard drive via USB. Therefore the
6Rockbox bootloader can be very minimalistic, without USB mode. 6Rockbox bootloader can be very minimalistic, without USB mode.
7This also makes it less dangerous to install the Rockbox bootloader, as you can 7This also makes it less dangerous to install the Rockbox bootloader, as you can
diff --git a/manual/getting_started/installation.tex b/manual/getting_started/installation.tex
index 6a97fdaa94..fc40929b30 100644
--- a/manual/getting_started/installation.tex
+++ b/manual/getting_started/installation.tex
@@ -27,24 +27,24 @@ installation options.
27 27
28\begin{description} 28\begin{description}
29\opt{HAVE_RB_BL_ON_DISK}{ 29\opt{HAVE_RB_BL_ON_DISK}{
30\item[The \playerman{} boot loader.] 30\item[The \playerman{} bootloader.]
31 The \playerman{} boot loader is the program that tells your \dap{} how to boot 31 The \playerman{} bootloader is the program that tells your \dap{} how to boot
32 and load the remaining firmware from disk. It is also responsible for the 32 and load the remaining firmware from disk. It is also responsible for the
33 disk mode on your \dap{}. 33 disk mode on your \dap{}.
34 34
35 This boot loader is stored in special flash memory in your \playerman{}. 35 This bootloader is stored in special flash memory in your \playerman{}.
36 It is already installed on your \dap{}, so it is never necessary to modify 36 It is already installed on your \dap{}, so it is never necessary to modify
37 this in order to install Rockbox.} 37 this in order to install Rockbox.}
38 38
39\item[The Rockbox boot loader.] \index{Boot loader} 39\item[The Rockbox bootloader.] \index{Bootloader}
40 \opt{HAVE_RB_BL_ON_DISK}{The Rockbox boot loader is loaded from disk by 40 \opt{HAVE_RB_BL_ON_DISK}{The Rockbox bootloader is loaded from disk by
41 the \playerman{} boot loader. It is responsible for loading the Rockbox 41 the \playerman{} bootloader. It is responsible for loading the Rockbox
42 firmware and for providing the dual boot function. It directly replaces the 42 firmware and for providing the dual boot function. It directly replaces the
43 \playerman{} firmware on the \daps{} disk. 43 \playerman{} firmware on the \daps{} disk.
44 \opt{gigabeat}{\note{Dual boot does not currently work on the gigabeat.}}} 44 \opt{gigabeat}{\note{Dual boot does not currently work on the gigabeat.}}}
45 45
46 \opt{HAVE_RB_BL_IN_FLASH}{ 46 \opt{HAVE_RB_BL_IN_FLASH}{
47 The boot loader is the program that tells your 47 The bootloader is the program that tells your
48 \dap{} how to boot and load other components of Rockbox. This is the 48 \dap{} how to boot and load other components of Rockbox. This is the
49 component of Rockbox that is installed to the flash memory of your 49 component of Rockbox that is installed to the flash memory of your
50 \playerman.} 50 \playerman.}
@@ -303,7 +303,7 @@ structure that Rockbox needs.
303} 303}
304 304
305\opt{SWCODEC}{ 305\opt{SWCODEC}{
306 \subsubsection{Installing the boot loader} 306 \subsubsection{Installing the bootloader}
307 \opt{h1xx,h300}{\input{getting_started/iriver_install.tex}} 307 \opt{h1xx,h300}{\input{getting_started/iriver_install.tex}}
308 \opt{ipod}{\input{getting_started/ipod_install.tex}} 308 \opt{ipod}{\input{getting_started/ipod_install.tex}}
309 \opt{m5,x5}{\input{getting_started/iaudio_install.tex}} 309 \opt{m5,x5}{\input{getting_started/iaudio_install.tex}}
@@ -413,17 +413,17 @@ completely follow the manual uninstallation instructions below.}}
413\opt{h1xx,h300}{ 413\opt{h1xx,h300}{
414 \note{ 414 \note{
415 If you want to remove the Rockbox bootloader, simply flash an unpatched 415 If you want to remove the Rockbox bootloader, simply flash an unpatched
416 \playerman{} firmware. Be aware that doing so will also remove the boot 416 \playerman{} firmware. Be aware that doing so will also remove the bootloader
417 loader USB mode. As that mode can come in quite handy (especially when 417 USB mode. As that mode can come in quite handy (especially when
418 having disk errors) it is recommended to keep the boot loader. It also 418 having disk errors) it is recommended to keep the bootloader. It also
419 gives you the possibility of trying Rockbox anytime later by simply 419 gives you the possibility of trying Rockbox anytime later by simply
420 installing the distribution files. 420 installing the distribution files.
421 \opt{h1xx}{ 421 \opt{h1xx}{
422 The Rockbox bootlaoder will automatically start the original firmware if 422 The Rockbox bootloader will automatically start the original firmware if
423 the \fname{.rockbox} directory has been deleted. 423 the \fname{.rockbox} directory has been deleted.
424 }% 424 }%
425 \opt{h300}{% 425 \opt{h300}{%
426 Although if you retain the Rockbox boot loader, you will need to hold the 426 Although if you retain the Rockbox bootloader, you will need to hold the
427 \ButtonRec{} button each time you want to start the original firmware. 427 \ButtonRec{} button each time you want to start the original firmware.
428 } 428 }
429 } 429 }
diff --git a/manual/getting_started/iriver_install.tex b/manual/getting_started/iriver_install.tex
index bc57617e0d..de3c8c0552 100644
--- a/manual/getting_started/iriver_install.tex
+++ b/manual/getting_started/iriver_install.tex
@@ -1,11 +1,11 @@
1% $Id$ % 1% $Id$ %
2 2
3 Installing the boot loader is the trickiest part of the installation. 3 Installing the bootloader is the trickiest part of the installation.
4 The Rockbox boot loader allows users to boot into either the Rockbox 4 The Rockbox bootloader allows users to boot into either the Rockbox
5 firmware or the \playerman{} firmware. For legal reasons, we cannot distribute 5 firmware or the \playerman{} firmware. For legal reasons, we cannot distribute
6 the boot loader. Instead, we have developed a program that will patch the 6 the bootloader. Instead, we have developed a program that will patch the
7 Iriver firmware with the Rockbox boot loader. These instructions will explain 7 Iriver firmware with the Rockbox bootloader. These instructions will explain
8 how to download and patch the Iriver firmware with the Rockbox boot loader 8 how to download and patch the Iriver firmware with the Rockbox bootloader
9 and install it on your jukebox. 9 and install it on your jukebox.
10 10
11 11
@@ -22,7 +22,7 @@
22 your player.} 22 your player.}
23 \opt{IRIVER_H300_PAD}{1.28K, 1.28EU, 1.28J, 1.29K, 1.29J and 1.30EU. 23 \opt{IRIVER_H300_PAD}{1.28K, 1.28EU, 1.28J, 1.29K, 1.29J and 1.30EU.
24 \note{The US \playername{} firmware is not supported and cannot be 24 \note{The US \playername{} firmware is not supported and cannot be
25 patched to be used with the boot loader. If you wish to install Rockbox 25 patched to be used with the bootloader. If you wish to install Rockbox
26 on a US \playername, you must first install a non-US version of the 26 on a US \playername, you must first install a non-US version of the
27 original firmware and then install one of the supported versions patched 27 original firmware and then install one of the supported versions patched
28 with the Rockbox bootloader. 28 with the Rockbox bootloader.
@@ -53,7 +53,7 @@
53 to the \fname{.hex} file that you previously downloaded to your desktop. 53 to the \fname{.hex} file that you previously downloaded to your desktop.
54 % 54 %
55 \item Click \setting{Patch}. The firmware patcher will patch the 55 \item Click \setting{Patch}. The firmware patcher will patch the
56 original firmware to include the Rockbox boot loader. The \fname{.hex} 56 original firmware to include the Rockbox bootloader. The \fname{.hex}
57 file on your desktop is now a modified version of the original 57 file on your desktop is now a modified version of the original
58 \fname{.hex} file. 58 \fname{.hex} file.
59 % 59 %
@@ -68,7 +68,7 @@
68 or that it is connected to the power adaptor. Interrupting the next step 68 or that it is connected to the power adaptor. Interrupting the next step
69 due to a power failure most likely will brick your \dap{}.} 69 due to a power failure most likely will brick your \dap{}.}
70 % 70 %
71 \item Update your \daps{} firmware with the patched boot loader. To do this, turn 71 \item Update your \daps{} firmware with the patched bootloader. To do this, turn
72 the jukebox on. Press and hold the 72 the jukebox on. Press and hold the
73 \opt{IRIVER_H100_PAD,IRIVER_H300_PAD}{\ButtonSelect{} button }% 73 \opt{IRIVER_H100_PAD,IRIVER_H300_PAD}{\ButtonSelect{} button }%
74 to enter the main menu, and navigate to \setting{General $\rightarrow$ Firmware 74 to enter the main menu, and navigate to \setting{General $\rightarrow$ Firmware
@@ -79,24 +79,24 @@
79 firmware update is complete the player will turn itself off. (The update 79 firmware update is complete the player will turn itself off. (The update
80 firmware process usually takes a minute or so.) 80 firmware process usually takes a minute or so.)
81 81
82 You have now installed the Rockbox boot loader. 82 You have now installed the Rockbox bootloader.
83\end{enumerate} 83\end{enumerate}
84 84
85\note{If you install the Rockbox boot loader but do not install the 85\note{If you install the Rockbox bootloader but do not install the
86 Rockbox firmware the Rockbox boot loader will load the Iriver firmware when the 86 Rockbox firmware the Rockbox bootloader will load the Iriver firmware when the
87 jukebox is turned on. 87 jukebox is turned on.
88 To load the \playerman{} firmware press and hold \ButtonRec{} before 88 To load the \playerman{} firmware press and hold \ButtonRec{} before
89 powering up the \dap{} until the \playerman{} logo appears. 89 powering up the \dap{} until the \playerman{} logo appears.
90 } 90 }
91 91
92\note{The boot loader has a built-in ``boot loader USB mode''. This function 92\note{The bootloader has a built-in ``bootloader USB mode''. This function
93 switches to USB mode when the \dap{} is connected to a computer upon 93 switches to USB mode when the \dap{} is connected to a computer upon
94 power-up. This way you can access the \daps{} hard disk without the need 94 power-up. This way you can access the \daps{} hard disk without the need
95 to boot any firmware (which is also useful when your hard disk is 95 to boot any firmware (which is also useful when your hard disk is
96 damaged). The screen will simply display the text ``boot loader USB mode''. 96 damaged). The screen will simply display the text ``bootloader USB mode''.
97 After you disconnect the \dap{} from USB the boot loader will 97 After you disconnect the \dap{} from USB the bootloader will
98 continue booting Rockbox. As in boot loader USB mode the firmware 98 continue booting Rockbox. As in bootloader USB mode the firmware
99 itself hasn't been loaded this is also a simple way of updating Rockbox. 99 itself hasn't been loaded this is also a simple way of updating Rockbox.
100 After the disconnect the boot loader will load the updated version of 100 After the disconnect the bootloader will load the updated version of
101 Rockbox. 101 Rockbox.
102} 102}