Rockbox Development > New Ports
Creative Zen Vision:M
jhulst:
--- Quote from: iSE on March 28, 2007, 07:30:48 PM ---I am extremely interested in this issue and would very much like to help if I can.
--- End quote ---
Right now our biggest need is figuring out how to load our own firmware. Any help is appreciated.
On another note, a test player is being sent to me. Is there someone who could download the EEPROM contents if I sent it to them?
jwh
iSE:
I know exactly what you mean mrsubway, theres a fair few things which just niggle at you and serve to ruin an otherwise excellent machine.
jhulst - im assuming that if we can find the file on the harddrive which is the firmware, it would be fairly simple to transfer something else in its place? I'm wondering if it may be worth comparing the firmware update file for two completely different Creative Zen's. The firmware would then be different and the simularities between the files code (using decompilers) would be how the firmware is transferred to the player?
saratoga:
--- Quote from: iSE on March 29, 2007, 04:27:47 PM ---jhulst - im assuming that if we can find the file on the harddrive which is the firmware, it would be fairly simple to transfer something else in its place?
--- End quote ---
We've been over this 5 or 6 times in this thread. I'll summarize it once again, but if you want details, you'll need to read the last 2 pages or so. We have the firmware already and a way to upload whatever firmware we want to the Vision:M. Theres a link to it in this thread and info about hows its done. What we don't have is a way to sign our own code so that the bootloader on the Vision:M will run it.
--- Quote from: iSE on March 29, 2007, 04:27:47 PM ---I'm wondering if it may be worth comparing the firmware update file for two completely different Creative Zen's.
--- End quote ---
Yes I've been suggesting this to people. Its how the Sansa port began.
iSE:
Sorry, I read the first like 4 pages and the last one, i didnt know you already had a way to upload it. So i'm guessing the bootloader runs a CRC check, using the MD5 checksum? Or is it creative's own cryptochecksum lol.
saratoga:
--- Quote from: iSE on March 30, 2007, 11:06:02 AM ---Sorry, I read the first like 4 pages and the last one, i didnt know you already had a way to upload it. So i'm guessing the bootloader runs a CRC check, using the MD5 checksum? Or is it creative's own cryptochecksum lol.
--- End quote ---
I don't think anyone knows. The extent of the effort so far has been to try and change strings and then upload them to the device. Since this fails whatever check there is, it doesn't work. I don't think anyone has made any serious attempt to figure out why.
Edit: You could be the first.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version