diff options
Diffstat (limited to 'manual/advanced_topics')
-rw-r--r-- | manual/advanced_topics/archos-flashing.tex | 30 |
1 files changed, 15 insertions, 15 deletions
diff --git a/manual/advanced_topics/archos-flashing.tex b/manual/advanced_topics/archos-flashing.tex index 58535c968a..fe36d53f83 100644 --- a/manual/advanced_topics/archos-flashing.tex +++ b/manual/advanced_topics/archos-flashing.tex | |||
@@ -20,13 +20,13 @@ Now, you can add Rockbox to the built-in software. | |||
20 | 20 | ||
21 | By reprogramming the firmware, we can boot much faster. \playerman\ has an | 21 | By reprogramming the firmware, we can boot much faster. \playerman\ has an |
22 | unnecessary slow boot loader, versus the boot time for Rockbox is much faster | 22 | unnecessary slow boot loader, versus the boot time for Rockbox is much faster |
23 | than the disk spinup, in fact it has to wait for the disk. Your boot time will | 23 | than the disk spin-up, in fact it has to wait for the disk. Your boot time will |
24 | be as quick as a disk spinup (e.g. 4 seconds from powerup until resuming | 24 | be as quick as a disk spin-up (e.g. 4 seconds from power-up until resuming |
25 | playback). | 25 | playback). |
26 | 26 | ||
27 | \subsection{Method} | 27 | \subsection{Method} |
28 | 28 | ||
29 | The replaced firmware will host a bootloader and 2 images. This is possible by | 29 | The replaced firmware will host a boot loader and 2 images. This is possible by |
30 | compression. The first is the \emph{permanent} backup, not to be changed any | 30 | compression. The first is the \emph{permanent} backup, not to be changed any |
31 | more.The second is the default one to be started, the first is only used when | 31 | more.The second is the default one to be started, the first is only used when |
32 | you hold the \opt{recorder,recorderv2fm}{\ButtonFOne}\opt{ondio}{\ButtonLeft}\opt{player}{\ButtonLeft} -key during start. Like supplied here, the first image | 32 | you hold the \opt{recorder,recorderv2fm}{\ButtonFOne}\opt{ondio}{\ButtonLeft}\opt{player}{\ButtonLeft} -key during start. Like supplied here, the first image |
@@ -35,7 +35,7 @@ and update. It can contain anything you like. If you prefer, you can program | |||
35 | the Archos firmware to there, too. | 35 | the Archos firmware to there, too. |
36 | 36 | ||
37 | \note{For now, the binary contained in the brand new player flash package does | 37 | \note{For now, the binary contained in the brand new player flash package does |
38 | contain rockbox built from current cvs in the second image slot. This is to | 38 | contain Rockbox built from current CVS in the second image slot. This is to |
39 | lower the risk of flashing (at least one of the images will hopefully work) in | 39 | lower the risk of flashing (at least one of the images will hopefully work) in |
40 | case you don't program a second image yourself in the first step. Of course the | 40 | case you don't program a second image yourself in the first step. Of course the |
41 | second image can be replaced like with the other models.} | 41 | second image can be replaced like with the other models.} |
@@ -50,14 +50,14 @@ There are two programming tools supplied: | |||
50 | with the desired image structure. | 50 | with the desired image structure. |
51 | \item The second one is called \fname{rockbox\_flash.rock} and is used to | 51 | \item The second one is called \fname{rockbox\_flash.rock} and is used to |
52 | reprogram only the second image. It won't touch any other byte, should be | 52 | reprogram only the second image. It won't touch any other byte, should be |
53 | safe to fool around with. If the programmed firmware is inoperational, you | 53 | safe to fool around with. If the programmed firmware is in-operational, you |
54 | can still use the \opt{recorder,recorderv2fm}{\ButtonFOne}\opt{ondio}{\ButtonLeft}\opt{player}{\ButtonLeft} start with the Archos firmware and Rockbox booted | 54 | can still use the \opt{recorder,recorderv2fm}{\ButtonFOne}\opt{ondio}{\ButtonLeft}\opt{player}{\ButtonLeft} start with the Archos firmware and Rockbox booted |
55 | from disk to try better. | 55 | from disk to try better. |
56 | \end{itemize} | 56 | \end{itemize} |
57 | 57 | ||
58 | The non-user tools are in the \fname{flash} subdirectory of the cvs source | 58 | The non-user tools are in the \fname{flash} subdirectory of the CVS source |
59 | files. There's an authoring tool which composed the firmware file with the | 59 | files. There's an authoring tool which composed the firmware file with the |
60 | bootloader and the 2 images. The bootloader project, a firmware extraction | 60 | boot loader and the 2 images. The boot loader project, a firmware extraction |
61 | tool, the plugin sources, and the tools for the UART boot feature: a monitor | 61 | tool, the plugin sources, and the tools for the UART boot feature: a monitor |
62 | program for the box and a PC tool to drive it. Feel free to review the sources | 62 | program for the box and a PC tool to drive it. Feel free to review the sources |
63 | for all of it, but be careful when fooling around with powerful toys! | 63 | for all of it, but be careful when fooling around with powerful toys! |
@@ -89,12 +89,12 @@ your box. | |||
89 | There's one ultimate safety net to bring back boxes with even completely | 89 | There's one ultimate safety net to bring back boxes with even completely |
90 | garbled flash content: the \emph{UART} boot mod, which in turn requires the | 90 | garbled flash content: the \emph{UART} boot mod, which in turn requires the |
91 | serial mod. It can bring the dead back to life, with that it's possible to | 91 | serial mod. It can bring the dead back to life, with that it's possible to |
92 | reflash independently from the outside, even if the flash is completely erased. | 92 | re-flash independently from the outside, even if the flash is completely erased. |
93 | It has been used that during development, else Rockbox in flash wouldn't have | 93 | It has been used that during development, else Rockbox in flash wouldn't have |
94 | been possible. Extensive development effort went into the exploitation of the | 94 | been possible. Extensive development effort went into the exploitation of the |
95 | UART boot mod. Mechanically adept users with good soldering skills can easily | 95 | UART boot mod. Mechanically adept users with good soldering skills can easily |
96 | perform these mods. Others may feel uncomfortable using the first tool | 96 | perform these mods. Others may feel uncomfortable using the first tool |
97 | (\fname{firmware\_flash.rock}) for reflashing the firmware. | 97 | (\fname{firmware\_flash.rock}) for re-flashing the firmware. |
98 | 98 | ||
99 | 99 | ||
100 | To comfort you a bit again: If you are starting with a known-good image, you | 100 | To comfort you a bit again: If you are starting with a known-good image, you |
@@ -105,7 +105,7 @@ Although it worked, it's not the recommended method. | |||
105 | About the safety of operation: Since we have dual boot, you're not giving up | 105 | About the safety of operation: Since we have dual boot, you're not giving up |
106 | the Archos firmware. It's still there when you hold | 106 | the Archos firmware. It's still there when you hold |
107 | \opt{recorder,recorderv2fm}{\ButtonFOne}\opt{ondio}{\ButtonLeft}\opt{player}{\ButtonLeft} during startup. So even if Rockbox from flash is not 100\% stable for | 107 | \opt{recorder,recorderv2fm}{\ButtonFOne}\opt{ondio}{\ButtonLeft}\opt{player}{\ButtonLeft} during startup. So even if Rockbox from flash is not 100\% stable for |
108 | everyone, you can still use the box, reflash the second image with an updated | 108 | everyone, you can still use the box, re-flash the second image with an updated |
109 | Rockbox copy, etc. | 109 | Rockbox copy, etc. |
110 | 110 | ||
111 | The flash chip being used by Archos is specified for 100,000 cycles, so you don't need to worry about that wearing out. | 111 | The flash chip being used by Archos is specified for 100,000 cycles, so you don't need to worry about that wearing out. |
@@ -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 bootloader and the | 141 | directory (the initial firmware for your model, with the boot loader 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 |
@@ -187,7 +187,7 @@ Short version: very easy, just play an \fname{.ucl} file like | |||
187 | Long version: | 187 | Long version: |
188 | 188 | ||
189 | The second image is the working copy, the \fname{rockbox\_flash.rock} plugin from | 189 | The second image is the working copy, the \fname{rockbox\_flash.rock} plugin from |
190 | this package reprograms it. The plugins needs to be consistant with the Rockbox | 190 | this package re-programs it. The plugins needs to be consistent with the Rockbox |
191 | plugin API version, otherwise it will detect mismatch and won't run. | 191 | plugin API version, otherwise it will detect mismatch and won't run. |
192 | 192 | ||
193 | It requires an exotic input, a UCL-compressed image, because that's the internal | 193 | It requires an exotic input, a UCL-compressed image, because that's the internal |
@@ -202,7 +202,7 @@ program from that download is called \fname{uclpack}. We'll use that to compress | |||
202 | \fname{rockbox.bin} which is the result of the compilation. This is a part of the | 202 | \fname{rockbox.bin} which is the result of the compilation. This is a part of the |
203 | build process meanwhile. If you compile Rockbox yourself, you should copy | 203 | build process meanwhile. If you compile Rockbox yourself, you should copy |
204 | \fname{uclpack} to a directory which is in the path, we recommend placing it in | 204 | \fname{uclpack} to a directory which is in the path, we recommend placing it in |
205 | the same dir as SH compiler. | 205 | the same directory as SH compiler. |
206 | 206 | ||
207 | 207 | ||
208 | Here are the steps: | 208 | Here are the steps: |
@@ -230,7 +230,7 @@ and now preferred one. Use this if available. | |||
230 | 230 | ||
231 | If you like or have to, you can also flash the Archos image as the second one. | 231 | If you like or have to, you can also flash the Archos image as the second one. |
232 | E.g. in case Rockbox from flash doesn't work for you. This way you keep the dual | 232 | E.g. in case Rockbox from flash doesn't work for you. This way you keep the dual |
233 | bootloader and you can easily try different later. The \fname{.ucl} of the Archos | 233 | boot loader and you can easily try different later. The \fname{.ucl} of the Archos |
234 | firmware is included in the package. | 234 | firmware 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 |
254 | ROM content, differentiation comes later by flash content. Rockbox identifies | 254 | ROM content, differentiation comes later by flash content. Rockbox identifies |
255 | this 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 | 255 | this 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 bootloader.} | 256 | \_norom firmware that has a slightly different boot loader.} |
257 | Without a boot ROM there is no UART boot safety net. To compensate for that as | 257 | Without a boot ROM there is no UART boot safety net. To compensate for that as |
258 | much as possible the MiniMon monitor is included, it starts with \opt{recorder,recorderv2fm}{\ButtonFThree+\ButtonOn}\opt{ondio}{\ButtonRight+\ButtonOff}\opt{player}{\ButtonRight+\ButtonOn}. | 258 | much as possible the MiniMon monitor is included, it starts with \opt{recorder,recorderv2fm}{\ButtonFThree+\ButtonOn}\opt{ondio}{\ButtonRight+\ButtonOff}\opt{player}{\ButtonRight+\ButtonOn}. |
259 | Using that the box can be reprogrammed via serial if the first 2000 bytes of the | 259 | Using that the box can be reprogrammed via serial if the first 2000 bytes of the |