devs/foxbox
1
0
Fork 0
forked from len0rd/rockbox
Code Pull requests Activity

note about different boot rom ROM, charging

Browse source 
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@3861 a1c6a512-1295-4272-9138-f99709370657
This commit is contained in:
Jörg Hohensohn 2003-07-21 18:17:32 +00:00
parent fb40e3963c
commit 216407f741
1 changed files with 24 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

37
www/docs/flash.t
View file

@ -90,7 +90,7 @@ one hundred thousand), so you don't need to worry about that wearing out.
<h2>4. Will it work for me?</h2> <h2>4. Will it work for me?</h2>
<p> <p>
You need two things: You need three things:
<ul> <ul>
<li> The first is a Recorder or FM model. Be sure you're using the correct <li> The first is a Recorder or FM model. Be sure you're using the correct
package, Recorder and FM are different! In principle, the technology works for package, 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
flash info gives you question marks, you're out of luck. The only chance then 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 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. in. If the chip is blank, you'll need the UART boot mod as well.
<li> Third, your boot ROM (within the CPU) has to contain the right stuff.
The vast majority of the Player/Recorder/FM all have the same boot ROM content,
differenciation comes later by flash content. So far very few people had a
different, presumable later boot ROM. It uses a different flash layout.
For these the tools will refuse to work, the only
way to find out is to try if the sanity check fails.
Flashing these is not impossible, but the firmware authoring has to be
different. It takes a developer with the UART boot mod to go ahead with it.
</ul> </ul>
<h2>5. How do I flash the firmware?</h2> <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.
<li> Backup the current firmware, using the first option of the debug menu <li> 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 (Dump ROM contents). This creates 2 files in the root directory, which you may
not immediately see in the Rockbox browser. The 256kB-sized not immediately see in the Rockbox browser. The 256kB-sized
"internal_rom_2000000-203FFFF.bin" one is your present firmware. Back it up to "internal_rom_2000000-203FFFF.bin" one is your present firmware. Back both up
your PC. to your PC.
<li> (optional) While you're in this Rockbox version, I recommend to give it a <li> (optional) While you're in this Rockbox version, I recommend to give it a
test and play around with it, this version is identical to the one about to be test 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
mask value will be kept, it won't overwrite it. Hitting F2 gives you a big mask value will be kept, it won't overwrite it. Hitting F2 gives you a big
warning. If I still didn't manage to scare you off, you can hit F3 to warning. If I still didn't manage to scare you off, you can hit F3 to
actually program and verify. The programming takes just a few seconds. 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.
<li> In the unlikely event that the programming should give you any error, <li> 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 don'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
Rockbox versions works OK. If you feel homesick, hold F1 during powerup. Rockbox versions works OK. If you feel homesick, hold F1 during powerup.
<p> <p>
The behavior with plugged charger differs from original: the box starts when Latest Rockbox now has a charging screen, but it is in an early stage. You'll
you plug it in (no charging screen). You can't power it off while the charger get it When the unit is off and you plug in the charger. The Rockbox charging
is plugged in, instead it kindof restarts in an odd way, can give ATA init algorithm is first measuring the battery voltage for about 40 seconds, after
errors in this case. This is not harmful, sortof reminds to unplug before that it only starts charging when the capacity is below 85%.
powering off. You can use the Archos charging (which always tops off) by holding F1
while plugging in.
<p> <p>
Rockbox currently insists on starting the HD before doing anything useful. The plugin API is currently changed often, new builds may render the plugins
This can be a problem if the batteries are deeply discharged and too weak to incompatible. When updating, make shure you grab those too, but don't
power up the HD, preventing rockbox to start up and charge them. Current overwrite the rockbox_flash.rock yet, since you still need it matching the
workaround is to hold F1 while plugging in, this gives the Archos charging currently running Rockbox to flash.
screen.
#include "foot.t" #include "foot.t"