summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--www/docs/flash.t37
1 files changed, 24 insertions, 13 deletions
diff --git a/www/docs/flash.t b/www/docs/flash.t
index 7617b1da39..84d679f29d 100644
--- a/www/docs/flash.t
+++ b/www/docs/flash.t
@@ -90,7 +90,7 @@ one hundred thousand), so you don't need to worry about that wearing out.
90 90
91<h2>4. Will it work for me?</h2> 91<h2>4. Will it work for me?</h2>
92<p> 92<p>
93You need two things: 93You need three things:
94<ul> 94<ul>
95<li> The first is a Recorder or FM model. Be sure you're using the correct 95<li> The first is a Recorder or FM model. Be sure you're using the correct
96package, Recorder and FM are different! In principle, the technology works for 96package, Recorder and FM are different! In principle, the technology works for
@@ -103,6 +103,15 @@ trick. You can find out via Rockbox debug menu, entry Hardware Info. If the
103flash info gives you question marks, you're out of luck. The only chance then 103flash info gives you question marks, you're out of luck. The only chance then
104is to solder in the right chip (SST39VF020), at best with the firmware already 104is to solder in the right chip (SST39VF020), at best with the firmware already
105in. If the chip is blank, you'll need the UART boot mod as well. 105in. If the chip is blank, you'll need the UART boot mod as well.
106
107<li> Third, your boot ROM (within the CPU) has to contain the right stuff.
108The vast majority of the Player/Recorder/FM all have the same boot ROM content,
109differenciation comes later by flash content. So far very few people had a
110different, presumable later boot ROM. It uses a different flash layout.
111For these the tools will refuse to work, the only
112way to find out is to try if the sanity check fails.
113Flashing these is not impossible, but the firmware authoring has to be
114different. It takes a developer with the UART boot mod to go ahead with it.
106</ul> 115</ul>
107 116
108<h2>5. How do I flash the firmware?</h2> 117<h2>5. How do I flash the firmware?</h2>
@@ -127,8 +136,8 @@ flow. If the flash info shows question marks, you can stop here, sorry.
127<li> Backup the current firmware, using the first option of the debug menu 136<li> Backup the current firmware, using the first option of the debug menu
128(Dump ROM contents). This creates 2 files in the root directory, which you may 137(Dump ROM contents). This creates 2 files in the root directory, which you may
129not immediately see in the Rockbox browser. The 256kB-sized 138not immediately see in the Rockbox browser. The 256kB-sized
130"internal_rom_2000000-203FFFF.bin" one is your present firmware. Back it up to 139"internal_rom_2000000-203FFFF.bin" one is your present firmware. Back both up
131your PC. 140to your PC.
132 141
133<li> (optional) While you're in this Rockbox version, I recommend to give it a 142<li> (optional) While you're in this Rockbox version, I recommend to give it a
134test and play around with it, this version is identical to the one about to be 143test and play around with it, this version is identical to the one about to be
@@ -145,6 +154,8 @@ and the file it's gonna program. After F1 it checks the file. Your hardware
145mask value will be kept, it won't overwrite it. Hitting F2 gives you a big 154mask value will be kept, it won't overwrite it. Hitting F2 gives you a big
146warning. If I still didn't manage to scare you off, you can hit F3 to 155warning. If I still didn't manage to scare you off, you can hit F3 to
147actually program and verify. The programming takes just a few seconds. 156actually program and verify. The programming takes just a few seconds.
157If the sanity check fails, you have the wrong kind of boot ROM and are
158out of luck by now, sorry.
148 159
149<li> In the unlikely event that the programming should give you any error, 160<li> In the unlikely event that the programming should give you any error,
150don't switch off the box! Otherwise you'll have seen it working for the last 161don't switch off the box! Otherwise you'll have seen it working for the last
@@ -245,17 +256,17 @@ from flash. This is some initialization problem which I hope to fix, rolo-ing
245Rockbox versions works OK. If you feel homesick, hold F1 during powerup. 256Rockbox versions works OK. If you feel homesick, hold F1 during powerup.
246 257
247<p> 258<p>
248The behavior with plugged charger differs from original: the box starts when 259Latest Rockbox now has a charging screen, but it is in an early stage. You'll
249you plug it in (no charging screen). You can't power it off while the charger 260get it When the unit is off and you plug in the charger. The Rockbox charging
250is plugged in, instead it kindof restarts in an odd way, can give ATA init 261algorithm is first measuring the battery voltage for about 40 seconds, after
251errors in this case. This is not harmful, sortof reminds to unplug before 262that it only starts charging when the capacity is below 85%.
252powering off. 263You can use the Archos charging (which always tops off) by holding F1
264while plugging in.
253 265
254<p> 266<p>
255Rockbox currently insists on starting the HD before doing anything useful. 267The plugin API is currently changed often, new builds may render the plugins
256This can be a problem if the batteries are deeply discharged and too weak to 268incompatible. When updating, make shure you grab those too, but don't
257power up the HD, preventing rockbox to start up and charge them. Current 269overwrite the rockbox_flash.rock yet, since you still need it matching the
258workaround is to hold F1 while plugging in, this gives the Archos charging 270currently running Rockbox to flash.
259screen.
260 271
261#include "foot.t" 272#include "foot.t"