Rockbox Development > New Ports
Creative Zen Vision:M
GuybrushThreepwood:
@mcuelenaere
Hi! I've built the revised version of zenutils: everything is fine now and it extracts the updater packages v1.62.02 and v1.30.02 too. Great work! Where was the problem?
Unfortunately, I haven't still succeeded in setting up a working environment under Windows: I've tried with MinGW but, though the build process with cmake succeeds, when I try to make the executables I still get many errors... As soon as I would have some spare time, I would try with Microsoft Visual Studio 2008 Express... Have a good day! :)
---EDIT---
I've tried to flash the v1.62.02 and v1.30.02 firmwares extracted by the newer update_extract version to my ZVM: both CreativeWizard and the hacked firmware updater succeed in flashing the 1.62.02 version but not the 1.30.02 (exactly the one I was interested in :( ).
This means that update_extract correctly extracts the firmware file (otherwise the firmware v1.60.02 shouldn't be flashed too) but I don't understand what's wrong with the firmware v1.30.02. I've noticed that the file size is the greatest (21,4Mb) among all the firmwares I've seen: perhaps the problem is there and CW nor the hacked updater can handle such a big firmware file (maybe they truncate the firmware file...).
I've tried also the older versions of CW but they don't even recognize my player (though CW v0.8.4.0, Windows and Creative Media Explorer do).
mcuelenaere:
--- Quote from: GuybrushThreepwood on August 25, 2008, 02:25:22 PM ---@mcuelenaere
Hi! I've built the revised version of zenutils: everything is fine now and it extracts the updater packages v1.62.02 and v1.30.02 too. Great work! Where was the problem?
Unfortunately, I haven't still succeeded in setting up a working environment under Windows: I've tried with MinGW but, though the build process with cmake succeeds, when I try to make the executables I still get many errors... As soon as I would have some spare time, I would try with Microsoft Visual Studio 2008 Express... Have a good day! :)
---EDIT---
I've tried to flash the v1.62.02 and v1.30.02 firmwares extracted by the newer update_extract version to my ZVM: both CreativeWizard and the hacked firmware updater succeed in flashing the 1.62.02 version but not the 1.30.02 (exactly the one I was interested in :( ).
This means that update_extract correctly extracts the firmware file (otherwise the firmware v1.60.02 shouldn't be flashed too) but I don't understand what's wrong with the firmware v1.30.02. I've noticed that the file size is the greatest (21,4Mb) among all the firmwares I've seen: perhaps the problem is there and CW nor the hacked updater can handle such a big firmware file (maybe they truncate the firmware file...).
I've tried also the older versions of CW but they don't even recognize my player (though CW v0.8.4.0, Windows and Creative Media Explorer do).
--- End quote ---
Try opening it with CreativeWizard and see if it can recognize the format...
Then try calculating the checksum and see if it's correct with the one in the NULL block
BTW why can't you just use the original fw updater which contains v1.30.02 ?
GuybrushThreepwood:
--- Quote from: mcuelenaere on August 25, 2008, 08:14:04 PM ---Try opening it with CreativeWizard and see if it can recognize the format...
--- End quote ---
It recognizes and opens the firmware.
--- Quote from: mcuelenaere on August 25, 2008, 08:14:04 PM ---Then try calculating the checksum and see if it's correct with the one in the NULL block
--- End quote ---
I don't know if I've calculated the checksum well (I've used CW with the default key 'CTL:N0MAD|PDE0.DPMP.') but the checksum doesn't correspond to that in the null block while it corresponds for the other firmwares I've tested. What's wrong??? I've thoroughly tested update_extract and I'm almost sure that now it works as expected so where is the problem?
--- Quote from: mcuelenaere on August 25, 2008, 08:14:04 PM ---BTW why can't you just use the original fw updater which contains v1.30.02 ?
--- End quote ---
Because, as said, my ZVM is faulty and, among the other issues I'm working on, it doesn't correctly reports the battery charge level and the v1.30.02 updater package hangs up on the low battery warning (it's impossible to ignore it like with the newer versions also when the player is connected to the AC adapter).
p.s. You haven't told me what was wrong with the older update_extract version. I'd like to know it if you want. Have a good day!
mcuelenaere:
--- Quote from: GuybrushThreepwood on August 26, 2008, 04:24:56 AM ---It recognizes and opens the firmware.
--- End quote ---
I get the same result..
--- Quote ---I don't know if I've calculated the checksum well (I've used CW with the default key 'CTL:N0MAD|PDE0.DPMP.') but the checksum doesn't correspond to that in the null block while it corresponds for the other firmwares I've tested. What's wrong??? I've thoroughly tested update_extract and I'm almost sure that now it works as expected so where is the problem?
--- End quote ---
I also get the same result with CreativeWizard, but if you try zen_crypt it reports the checksum is correct.. (keep in mind CreativeWizard is my code & ZenUtils is zook's; so there could be some mistakes in mine)
I also decrypted FRESC (v.1.30.02) and checked for the checksum key and it's exactly the same; so that can't be the problem either.
--- Quote ---Because, as said, my ZVM is faulty and, among the other issues I'm working on, it doesn't correctly reports the battery charge level and the v1.30.02 updater package hangs up on the low battery warning (it's impossible to ignore it like with the newer versions also when the player is connected to the AC adapter).
--- End quote ---
Try using other/older versions? I found this site.
--- Quote ---p.s. You haven't told me what was wrong with the older update_extract version. I'd like to know it if you want. Have a good day!
--- End quote ---
The problem was the find_firmware_offset() routine, like I explained previously.
GuybrushThreepwood:
--- Quote from: mcuelenaere on August 26, 2008, 09:27:59 AM ---I also decrypted FRESC (v.1.30.02) and checked for the checksum key and it's exactly the same; so that can't be the problem either.
--- End quote ---
What do you mean by "FRESC"? Excuse me for the dumb question! :-[ I'm wondering if CW checks the correspondence between the checksum and the checksum stored in the NULL block and, if the check fails, doesn't go on with uploading the firmware... I think it could be a useful check but I don't know if you've included it: that's why I'm just guessing.
Maybe even the hacked updater makes that check... I don't know.
--- Quote from: mcuelenaere on August 26, 2008, 09:27:59 AM ---Try using other/older versions? I found this site.
--- End quote ---
It's exactly the place I get older firmwares from! ;) All the older firmwares have that check on the battery level which isn't possible to ignore... :(
--- Quote from: mcuelenaere on August 26, 2008, 09:27:59 AM ---The problem was the find_firmware_offset() routine, like I explained previously.
--- End quote ---
Thanks for letting me know!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version