Rockbox Development > New Ports
SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2
csavery:
Yes, but look further down. It does a check in a function called get_model - this returns unknown with the new 2.03.33 image - well, the one I have anyway - just downloaded from sansa site.
I added,
case 0x71:
and then compiled and ran mkamsboot. It succeeds with this model_id value added. I haven't copied it to my Fuze yet because I'd like to confirm somehow that others have seen this new model_id in 2.03.33. The md5 checks out so I don't see how others could not have 0x71 in their OF file as well.
The model_id is not the version # but seems it should refer to the device model. Of course, my device has changed but I am definitely seeing the value 0x71 in location 0x219 in the latest OF image fuzpa.bin
Maybe this is why they rolled 2.02.31 -> 2.03.33 ?
Jennifur:
--- Quote from: csavery on May 21, 2010, 04:23:56 PM ---Yes, but look further down. It does a check in a function called get_model - this returns unknown with the new 2.03.33 image - well, the one I have anyway - just downloaded from sansa site.
I added,
case 0x71:
and then compiled and ran mkamsboot. It succeeds with this model_id value added. I haven't copied it to my Fuze yet because I'd like to confirm somehow that others have seen this new model_id in 2.03.33.
The model_id is not the version # but seems it should refer to the device model. Of course, my device has changed but I am definately seeing the value 0x71 in location 0x219 in the latest OF image fuzpa.bin
--- End quote ---
I see it too. Yet when I patched the OF I didn't get(notice) the error. I can try again and see if I get it.
EDIT:
I didn't get the error at all. This is the output from mkamsboot
--- Code: ---jennifur@alice:/mnt/disk$ mkamsboot fuzpa_orig.bin bootloader-fuzev2.sansa boot.bin
mkamsboot Version r26241-100521
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
[INFO] Original firmware MD5 checksum match
[INFO] Model: Sansa Fuze v2 - Firmware version: 2.03.33
[INFO] Firmware patching has begun !
[INFO] Original firmware size: 168920 bytes
[INFO] Packed OF size: 90016 bytes
[INFO] Bootloader size: 76240 bytes
[INFO] Packed bootloader size: 33945 bytes
[INFO] Dual-boot function size: 364 bytes
[INFO] UCL unpack function size: 168 bytes
[INFO] Total size of new image: 124493 bytes
[INFO] Patching succeeded!
jennifur@alice:/mnt/disk$
--- End code ---
csavery:
That's weird. It's exactly what I get after I add the model id.
How could the md5 match the one embedded in mkamsboot when the model byte 0x71 != 0x70 ?
Baffling... I guess I'll wait a bit before trying to boot on it.
Jennifur:
I ran md5sum on the OF and got the same result as in mkamsboot.c. Can you try downloading the firmware once again and run md5sum on it?
funman:
get_model() isn't called if the md5sum of the OF is in the list.
Btw, before we add an OF release it is always tested on a real device first.
I see indeed that the model id has changed from 0x70 to 0x71 so it makes me wonder:
Perhaps we should not rely on this field to detect model of the OF ?
What if Sandisk decides to release a Clip+ firmware with model id = 0x71 too ?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version