Wiki > Main > SansaAMS (compare)
Difference: SansaAMS (r281 vs. r280)
The term "Sansa AMS" is applied to all Sansas with the AMS AS3525 SoC: namely the Fuze v1, Clip v1, e200 v2, c200 v2, and m200 v4 (m200 with firmware v04.xx.xx) or the AS3525v2 SoC: namely the Fuze v2, Clip v2, Clip+, and Clip Zip. "Samsa" is a pet name sometimes applied to the AMS Sansas.
Rockbox is considered Stable on Fuze v1, e200 v2, Clip v1, Clip v2, Clip+ and Fuze v2; Unstable on C200 v2 and Clip zip; and Unusable on m200 v4.
m200v4: sporadic (volume related) shutdowns, probably due to misconfigured voltage regulator.
AMSv2 issues (Fuzev2, Clipv2, Clip+, ClipZip?)
Port status as of March 23, 2012.
Automatic installation with RockboxUtility is recommended and far easier
Note: M200 v4 automatic installation is currently disabled. You can try a Development build of Rockbox Utility. Beware that development builds might not be fully tested. Make sure to read the RockboxUtility wiki page first and check the changes listed on that page.
MANUAL INSTALLATION IS DISCOURAGED IF YOU DON'T FEEL CONFIDENT ABOUT IT, USE THE AUTOMATIC METHOD ABOVE
Files to download:
For all models
Linux & Mac OSX
You can power off a hanging and/or nonresponsive player by holding the power button for at least 30 seconds. On many Sansas this is forces a hardware power-off and will always succeed; on some Sansas it's possible for this to fail, in which case letting the battery run down until the player is forced off may be the best solution. No one has confirmed whether the power button method works on the m200 v4.
It is quite uncommon to brick a player under normal operation.
Some Clip v2 users have found their players bricked by the standard installer, but they're a minority; it's suspected that there's an unusual and problematic sub-revision of the hardware.
Rockbox tools are designed to minimize the danger of bricking the device; outside of the problematic minority of Clip v2 players, it's practically impossible to brick your player without modifying the mkamsboot tool. Quite often people think their device is bricked when it is actually just hung/nonresponsive; try the above methods first.
The unbricking procedures which follow require hardware modification and are therefore somewhat dangerous. IF YOU TRY THESE WHEN YOUR DEVICE IS NOT ACTUALLY BRICKED, YOU ARE RUNNING AN UNNECESSARY RISK OF DESTROYING YOUR PLAYER. If you think your device is bricked, please chat with us on IRC to confirm this is the case before pulling out your soldering iron.
Some models can be put in a recovery mode by shorting a couple of pins on the PCB, see SansaAMSUnbrick for details.
Extensive tutorial using this procedure exists for Sansa Clip v2, see SansaClipV2UnbrickingTutorial for details.
The other AMS Sansas can also get into this mode, but can not be unbricked this way (they present as an USB disk of size 0 that cannot be written).
If your Sansa can not be unbricked using the above method and you feel comfortable about soldering some wires to your device, you can try to unbrick using a JTAG debugger.
If you damage the filesystem on the internal SD you can find yourself in a situation where the database refresh in the OF hangs up and you will be unable to boot into the OF and also unable to connect via usb to correct the problem. If you find yourself in this situation you can bypass the OF database refresh by connecting your player via usb and disconnecting it just after the Sandisk logo appears on the screen. This will bring you into the normal top menu in the OF and you can then format your player through the settings menu.
ARM922T datasheet as used in Fuze v1, e200 v2, Clip v1, C200 v2, M200 v4.
ARM926EJS datasheet as used in Fuze v2, Clip v2 and Clip +.
The SD/MMC controller used in the AMSv2 seems to be a Synopsys Designware block, more info at:
r287 - 19 Jan 2014 - 01:07:37 - MichaelGiacomelliRevision r281 - 20 Aug 2012 - 22:54 - IainCheyne
Revision r280 - 16 Aug 2012 - 18:16 - MichaelGiacomelli
Copyright © by the contributing authors.