Rockbox Development > New Ports
SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2
Bagder:
Didn't someone already provide a fdisk -l output for one of the v2s? Has anyone tried to scan the disk for the firmware image?
rondestvedt:
--- Quote from: jcollie on January 04, 2008, 05:28:51 PM ---
--- Quote from: Bagder on January 04, 2008, 05:04:37 PM ---I'd say the main problem is that nothing much is actually going on, it is much more talk about what is going on or what could go on...
--- End quote ---
Well, I'm extremely interested in making this port happen, I just don't have a lot of experience with this sort of development...
What's the next step? From what I've seen the next big hurdle is figuring out how to upload new firmware to the v2s. Unfortunately I didn't have a USB monitor set up when I updated my e250v2 using the SanDisk's updater. It does not appear that there's a way to downgrade using SanDisk's updater and who knows when a new OF update will be issued.
--- End quote ---
I was able to successfully downgrade the firmware on a e250v2 from 3.01.14A back to 3.01.11A just by using the e200pA.bin file from Daniel's page here -> http://daniel.haxx.se/sansa/v2.html. After putting the .bin file in the root directory while in MSC mode, and after unplugging the USB cable it brought up a screen saying "Firmware update in progress".After it restarted the info page showed 3.01.11A as the firmware. The only problem is if the firmware update is bad, will it still be able to do another update?
Bagder:
So, a daring person can thus get the .bin file, modify the 32bit value at index 4 (the checksum) and try to upgrade to that, just to see what happens... It might cause trouble, but I expect SanDisk to have some kind of precaution against damaged binaries so my hope is that this triggers some kind of recovery mode.
Another test is to modify a few strings in the image and recalc an updated checksum (based on the algorithm posted on the v2 page) and see if that is accepted and works.
rondestvedt:
I just tried a simple test. I switched the positions of two letters in the message that comes up when you power on with the hold button on. The message saying that the firmware update was in progress came up, then after a few seconds it powered down without a firmware update complete, and the firmware was unchanged. I'll try again later using the checksum calculator with the same changes.
jcollie:
--- Quote from: Bagder on January 04, 2008, 05:59:17 PM ---Didn't someone already provide a fdisk -l output for one of the v2s? Has anyone tried to scan the disk for the firmware image?
--- End quote ---
The v2 disk does not appear to be partitioned, so "fdisk -l" will likely just print garbage. I dumped the entire drive and tried searching for "AS3525" (which is a string I saw in e200pA.bin) and couldn't find it, however that could because I'm running the newer firmware version. Could the v2s have a separate flash memory area for storing the active firmware that isn't exposed by the USB interface.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version