Rockbox Development > New Ports
Creative Zen Vision:M
zook:
--- Quote from: wesmo on November 12, 2007, 07:55:36 PM ---Awesome work there mcuelenaere and zook :D
Once zooks firmware utilities are up and running whats next?
err if creative has modified nano-x dramatically we should be able to get their original source http://www.microwindows.org/faq.html
--- End quote ---
The short-term goal is to get a build tool chain up and running.
Once that's ready, the actual porting process can begin.
Which I think entails writing a bootloader, working out (reversing/reading specs) how the various devices work and writing the code to integrate them into the rockbox source.
But I have yet to look into the rockbox source, so I have no idea how much work is generally involved.
I'll have plenty of reading up, on various subjects, ahead of me. This is still new ground to me.
Bagder:
--- Quote from: zook on November 13, 2007, 02:40:59 PM ---The short-term goal is to get a build tool chain up and running.
--- End quote ---
If you get the rockbox sources, running the tools/rockboxdev.sh (and select arm) should be enough...
--- Quote ---Once that's ready, the actual porting process can begin.
Which I think entails writing a bootloader, working out (reversing/reading specs) how the various devices work and writing the code to integrate them into the rockbox source.
But I have yet to look into the rockbox source, so I have no idea how much work is generally involved.
--- End quote ---
There's really no "generally" here since it all depends on the particular hardware, what has been done on this or very similar hardware before and how fluent the people doing it are in these things.
Since the main SoC is the same one the mrobe500 uses, I figure some inspiration can be gotten from there.
BTW, given that you seem to start figuring out the file format for firmware upgrades, do you know if or how you can restore back to a sane environment if you upgrade to a totally broken firmware (like for example your own attempts) ?
zook:
--- Quote from: Duffman90 on November 13, 2007, 04:12:43 PM ---First: Congratulations! Great work zook and mcuelenaere!
I followed this thread for half a year now and am quite happy that you finally made it.
Now i wanted to ask, if there already is some (rather easy) work to do. I'm quite motivated, but my programming knowledge doesn't go far beyond basic delphi skills and even less in C. If there is anything which is possible to learn in a few weeks, i would like to help.
--- End quote ---
I can't think of anything suitable. A good grasp of C is required at this point.
--- Quote from: Bagder on November 13, 2007, 04:22:27 PM ---
--- Quote from: zook on November 13, 2007, 02:40:59 PM ---The short-term goal is to get a build tool chain up and running.
--- End quote ---
If you get the rockbox sources, running the tools/rockboxdev.sh (and select arm) should be enough...
--- End quote ---
I should probably have been more clear. Regardless of how rockbox works, we'll need to produce a firmware archive, which contains an executable in the specific file format which creative players use. This is what I mean't by build tools.
--- Quote from: Bagder on November 13, 2007, 04:22:27 PM ---
--- Quote ---Once that's ready, the actual porting process can begin.
Which I think entails writing a bootloader, working out (reversing/reading specs) how the various devices work and writing the code to integrate them into the rockbox source.
But I have yet to look into the rockbox source, so I have no idea how much work is generally involved.
--- End quote ---
There's really no "generally" here since it all depends on the particular hardware, what has been done on this or very similar hardware before and how fluent the people doing it are in these things.
--- End quote ---
OK. I just wanted to address the anticipation that some people might have.
--- Quote from: Bagder on November 13, 2007, 04:22:27 PM ---Since the main SoC is the same one the mrobe500 uses, I figure some inspiration can be gotten from there.
--- End quote ---
Thanks, I didn't know that.
--- Quote from: Bagder on November 13, 2007, 04:22:27 PM ---BTW, given that you seem to start figuring out the file format for firmware upgrades, do you know if or how you can restore back to a sane environment if you upgrade to a totally broken firmware (like for example your own attempts) ?
--- End quote ---
Yes. The bootloading of the player software is split into 3 phases:
1) The built-in boot loading, which loads a limited sized secondary boot loader from a fixed location in flash memory, to a fixed address.
2) The secondary boot loader (named FBOOT in the firmware) which decrypts and loads the Rescue Mode software (FRESC) also from flash memory.
3) The Rescue Mode software decrypts, decompresses and loads the actual player software (CENC/TL) from a file named Jukebox2.jrm on the HDD. If the validation checks fail, it'll load a Resuce Mode menu, which allows you to "reload" the firmware amongst other things.
I've described the file formats, hashing, compression and encryptions algorithms involved in the process. However, the information is a bit scattered around at the moment.
Anyway, you've got a way of recovering as long as you don't corrupt the code in flash.
mcuelenaere:
http://rapidshare.com/files/69725358/sendfile.c
This file is a modified libmtp example file, which should upload a firmware correctly.
Only problem is I can't compile it (cygwin complains about missing libiconv and when I installed it, it still complains)
mcuelenaere:
TI releases free c54x compiler!!
http://open.neurostechnology.com/node/1020
P.S.: wiki is updated
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version