Rockbox Development > New Ports
Creative Zen Vision:M
iSE:
Well if you can get me the info about the new firmware and how its transferred I will do what I can to figure out a way. And I do have some experience though I can't promise anything lol! You know how it is.
saratoga:
Actually, having reread the epizenter thread, it looks like the checksum is done by the firmware update utility. Or at least a checksum is. So I think I was wrong about having a way to update the firmware. Theres a possible way, once the checksum is calculated, but I don't think anyone has managed it.
At least from reading that thread, it sounds like the upgrade progress is failing on the PC side, not the device side. I could be wrong though.
http://www.epizenter.net/e107_plugins/forum/forum_viewtopic.php?69697.0
iSE:
Right, so I was wondering, when jhulst is finally able to hook up the harddrive of one to the computer (I would have a go but I'm still waiting for someone to say how to open the damn thing without using a crowbar). But yes, if its possible to explore the file system, lets hope there is a file sitting there called NK.bin. So unless the bootloader performs a CRC check (which I don't see how thats possible with updating the firmware unless the update program changes the bootloader which would be really over the top) then hopefully it will be a simple matter of replacing that file. Next step would be to find out how to replace the file through a USB cable, once we know where the file is. I am hoping once we can work out what filesystem is used, I may be able to get it to work through just the USB cable. (One of the benefits of Linux and the way it mounts things!)
saratoga:
--- Quote from: iSE on March 30, 2007, 05:15:13 PM --- So unless the bootloader performs a CRC check (which I don't see how thats possible with updating the firmware unless the update program changes the bootloader which would be really over the top) then hopefully it will be a simple matter of replacing that file.
--- End quote ---
Most players do a check in order to prevent people from hacking their firmware. Its actually very easy, they just have the bootloader compute a hash, and compare it to the hash written in the binary itself. Some even take this a step farther and use the hash to encrypt the entire firmware file. I'm expecting some sort of hash check in the bootloader, but you never know.
iSE:
A hash by using an algorithm then? I was meaning by using it size and properties to calculate a checksum, by updating the file the checksum would change however. So how to Creative get the firmware to pass then which otherways can't? Would simply replacing the file on the HD cause an abort when switching it on then?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version