rockbox

mirror of https://github.com/Rockbox/rockbox.git synced 2025-10-13 18:17:39 -04:00

History

Rafaël Carré ff6b0425e4 mkamsboot/rbutil/amsinfo : do not try to detect the model of a given Sansa AMS OF The field we thought was representative of the model is not, it has changed in the past for fuzev1 and fuzev2. For example the value 0x23 is found in 2 old fuzev1 OF versions, and in the c200v2 OF The only reliable way to detect the model of a given OF is by using the built-in list of md5sums. Modify mkamsboot and rbutilqt to load the rockbox bootloader first, and then check if the model in the bootloader corresponds to the model of the known md5sum of the given OF. That way we can continue to present the user with a list of known OF versions in case the OF is unknown to mkamsboot Also explicit the dependency of main.c on mkamsboot.h in case the prototypes change Correct the header's description not updated in r21648 git-svn-id: svn://svn.rockbox.org/rockbox/trunk@26248 a1c6a512-1295-4272-9138-f99709370657		2010-05-24 10:06:52 +00:00
..
dualboot	Fuzev2: use enrd0 for USB detection, GPIO didn't work on some models	2010-05-18 00:11:42 +00:00
dualboot.c	Fuzev2: use enrd0 for USB detection, GPIO didn't work on some models	2010-05-18 00:11:42 +00:00
dualboot.h	Fuzev2: use enrd0 for USB detection, GPIO didn't work on some models	2010-05-18 00:11:42 +00:00
main.c	mkamsboot/rbutil/amsinfo : do not try to detect the model of a given Sansa AMS OF	2010-05-24 10:06:52 +00:00
Makefile	mkamsboot/rbutil/amsinfo : do not try to detect the model of a given Sansa AMS OF	2010-05-24 10:06:52 +00:00
md5.c	FS#10253 : mkamsboot v1.0	2009-05-28 18:27:08 +00:00
md5.h	Add MD5 checksumming of the original firmware images - for extra safety, and also because some Fuze firmwares have the same ID (or what we thought was the ID) as the M200 firmwares. Plus a few minor cleanups.	2008-10-30 00:13:29 +00:00
mkamsboot.c	mkamsboot/rbutil/amsinfo : do not try to detect the model of a given Sansa AMS OF	2010-05-24 10:06:52 +00:00
mkamsboot.h	mkamsboot/rbutil/amsinfo : do not try to detect the model of a given Sansa AMS OF	2010-05-24 10:06:52 +00:00
README	Clip+: boot to OF if USB is connected	2010-05-17 21:57:46 +00:00

README

mkamsboot
---------

A tool to inject a bootloader into a Sansa V2 (AMS) firmware file.


Usage
-----

mkamsboot <firmware file> <boot file> <output file>

<firmware file> is an original Sansa firmware file obtained from the Sansa
    forums for example : http://forums.sandisk.com/sansa/?category.id=devices

<boot file> is the code you want to execute (a rockbox bootloader), previously
    scrambled with tools/scramble utility.

<output file> is the resulting firmware file which you'll have to copy on your
    Sansa player. See "Firmware filenames".


Supported models
----------------

Sansa Clip  :   firmware version starting with "01."
Sansa Clip+ :   firmware version starting with "01."
Sansa Clipv2:   firmware version starting with "02."
Sansa Fuze  :   firmware version starting with "01."
Sansa Fuzev2:   firmware version starting with "02."
Sansa E200v2:   firmware version starting with "03."
Sansa C200v2:   firmware version starting with "03."
Sansa M200v4:   firmware version starting with "4."


Firmware filenames
------------------

For the firmware upgrade to happen, the firmware has to be named specially:

clip v2 :   m30pa.bin
clip    :   m300a.bin
clip+   :   clppa.bin
fuze    :   fuzea.bin
fuzev2  :   fuzpa.bin
e200v2  :   e200pa.bin
c200v2  :   c200pa.bin
m200v4  :   m200a.bin


Dual-Boot
---------

  The purpose of this program is to provide dual-boot between the original
firmware and the new (rockbox) firmware.

  By default the player will boot into the new firmware.

  To boot into the Original Firmware, you need to press the Left key.
  ***Note : on the c200v2 you need to press the Right key.
  ***Note : on the Clip+ you can alternatively press the Home key.

  The player will boot into the Original Firmware as well if it is powered up by
inserting an usb cable.
  ***Note : on the m200v4 powering up by usb will cause booting into the new firmware.

Hacking
-------

See comments in mkamsboot.c and dualboot/dualboot.S for more information.