Wiki > Main > FlashingRockbox (compare)
Difference: FlashingRockbox (r22 vs. r21)
Rockbox in Flash - FAQ and User Manual FlashingRockbox
by Jörg Hohensohn aka [IDC]Dragon, This page used to describe flashing Rockbox on your Archos machine, but is now out of date. If you want to view this old information, select version 21 of this page. JoergHohensohn
For current details of how to flash your Archos, please go to the BootBox page.
Please note that this page is no longer current, but is left here for background information. The files mentioned are no longer available. Instead Archos users should see BootBox for flashing information.
Flashing in the sense used here and elsewhere in regard to Rockbox means reprogramming the flash memory of the Archos unit.
When you bought your Archos, it came with the Archos firmware flashed. Now, you can add Rockbox to the built-in software.
Note: This page describes the flashing process in detail. If you don't want to read tons of technical mumbo jumbo, you can read the Blind man's guide to flashing Rockbox, which is a step-by-step guide to flashing Rockbox, originally intended for blind people.
By reprogramming the firmware, we can boot much faster. Archos has an unnecessary slow boot loader, versus the boot time for Rockbox is much faster than the disk spinup, in fact it has to wait for the disk. Your boot time will be as quick as a disk spinup (e.g. 4 seconds from powerup until resuming playback).
The replaced firmware will host a bootloader and 2 images. This is possible by compression. The first is the "permanent" backup, not to be changed any more. The second is the default one to be started, the first is only used when you hold the F1 key (all recorder models), LEFT key (Ondio) or MINUS key (player) during start. Like supplied here, the first image is the original Archos firmware, the second is empty, left for you to program and update. It can contain anything you like, if you prefer, you can program the Archos firmware to there, too.
For now, the binary contained in the brand new player flash package does contain rockbox built from current cvs in the second image slot. This is to lower the risk of flashing (at least one of the images will hopefully work) in case you don't program a second image yourself in the first step. Of course the second image can be replaced like with the other models.
There are two programming tools supplied:
The non-user tools are in the "flash" subdirectory of the cvs source files. There's an authoring tool which composed the firmware file with the bootloader and the 2 images, the bootloader project, a firmware extraction tool, the plugin sources, and the tools for the UART boot feature: a monitor program for the box and a PC tool to drive it. Feel free to review the sources for all of it, but be careful when fooling around with powerful toys!
Well, is it dangerous? Yes, certainly, like programming a mainboard BIOS, CD/DVD drive firmware, mobile phone, etc. If the power fails, your chip breaks while programming or most of all the programming software malfunctions, you'll have a dead box. We take no responsibility of any kind, you do that at your own risk. However, we tried as carefully as possible to bulletproof this code. The new firmware file is completely read before it starts programming, there are a lot of sanity checks. If any fails, it will not program. Before releasing this, we have checked the flow with exactly these files supplied here, starting from the original firmware in flash. It worked reliably, there's no reason why such low level code should behave different on your box.
The risk is slightly higher for player flashing, because (a) this is brand new and (b) it could not be tested with all hardware versions. Refer to this e-mail: http://www.rockbox.org/mail/archive/rockbox-archive-2004-12/0245.shtml
There's one ultimate safety net to bring back boxes with even completely garbled flash content: the UART boot mod, which in turn requires the serial mod. It 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 that during development, else Rockbox in flash wouldn't have been possible. Extensive development effort went into the exploitation 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 (firmware_flash.rock) for reflashing the firmware.
To comfort you a bit again: 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. ;-)"
About the safety of operation: Since we have dual boot, you're not giving up the Archos firmware. It's still there when you hold F1/LEFT/MINUS during startup. So even if Rockbox from flash is not 100% stable for everyone, you can still use the box, reflash the second image with an updated Rockbox copy, etc.
The flash chip being used by Archos is specified for 100,000 cycles (in words: one hundred thousand), so you don't need to worry about that wearing out.
You need two things:
Short explanation: copy the firmware_*.bin files for your model from the distribution to the root directory of your box, then run the "firmware_flash.rock" plugin. Long version, step by step procedure:
Now the initial procedure is done. Since the second half of the flash is still empty, there is "just" the Archos image starting when you reboot now. Not much has changed yet. The Archos software starts a bit quicker than usual, then loads Rockbox from disk. The fun really starts when you add Rockbox to the flash, as described in the next chapter.
This is not yet true for the player, since the player binary does already contain a rockbox image in the second slot. See above why.
You may delete the ".bin" files now.
Short explanation: very easy, just play an .ucl file like "rockbox.ucl" from a release or build:
The second image is the working copy, the "rockbox_flash.rock" plugin from this package reprograms it. The plugins needs to be consistant with the Rockbox plugin API version, otherwise it will detect mismatch and won't run.
It requires an exotic input, a UCL-compressed image, because that's the internal format. UCL is a nice open-source compression library. The decompression is very fast and less than a page of C-code. The efficiency is even better than Zip with maximum compression, cooks it down to about 58% of the original size. For details on UCL, see: http://www.oberhumer.com/opensource/ucl/
Rockbox developers using Linux will have to download it from there and compile it, for Win32 and Cygwin the executables are next to the packages. The sample program from that download is called "uclpack". We'll use that to compress "rockbox.bin" which is the result of the compilation. This is a part of the build process meanwhile. If you compile Rockbox yourself, you should copy uclpack to a directory which is in the path, we recommend placing it in the same dir as SH compiler.
Don't flash any "old" builds which don't have the latest coldstart ability. They won't boot. These instructions refer to builds from cvs state 2003-07-10 on (player: 2004-12-17).
Here are the steps:
You may find two .ucl files in the .rockbox folder. The classical, compressed one is "rockbox.ucl". If your model has enough flash space left, there may be an additional "rombox.ucl", which is uncompressed and can run directly from flash ROM, saving some RAM. The second way is the newer and now preferred one, use this if available. See RomBox for more details.
If you like or have to, you can also flash the Archos image as the second one, e.g. in case Rockbox from flash doesn't work for you. This way you keep the dual bootloader and you can easily try different later. The .ucl of the Archos firmware is included in the package.
If you'd like to revert to the original firmware, you can do like you did when you flashed Rockbox for the first time. You simply use the backup files you saved when flashing Rockbox for the first time and rename "internal_rom_2000000-203FFFF.bin" to "firmware_*.bin" (name varies per model, use the filename which "firmware_flash.rock" asks for) and put it in the root.
Rockbox has a charging screen, but it is not 100% perfect. You'll get it when the unit is off and you plug in the charger. The Rockbox charging algorithm is first measuring the battery voltage for about 40 seconds, after that it only starts charging when the capacity is below 85%. You can use the Archos charging (which always tops off) by holding F1 while plugging in. Some FM users reported charging problems even with F1, they had to revert to the original flash content. These problems should not arise for player users, because the player charging is hardware controlled.
If the plugin API is changed, new builds may render the plugins incompatible. When updating, make sure you grab those too, and RoLo or F1-boot into the new version before flashing it.
There are two variants of how the boxes starts, therefore the normal and the _norom firmware files. The vast majority of the Player/Recorder/FM/Ondio all have the same boot ROM content, differentiation comes later by 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 new _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, it starts with F3+On (recorders), RIGHT+ON (Ondio) or "+"+ON (player). Using that the box can be reprogrammed via serial if the first ~2000 bytes of the flash are OK.
Depending on your model (player, recorder, FM, V2 recorder, Ondio FM/SP), download one of the 6 packages:
Jörg's AVI movie (1.5MB) rockbox_flash_boot.avi showing his unit booting Rockbox from flash.
Roland's screendump from the movie:
r24 - 30 Jun 2008 - 21:52:31 - TomColeRevision r22 - 29 Jun 2008 - 03:13 - TomCole
Revision r21 - 27 Jan 2008 - 22:06 - MarcGuay
Copyright © by the contributing authors.