Rockbox Development > New Ports
Creative Zen Vision:M
GuybrushThreepwood:
--- Quote from: BigBambi on August 23, 2008, 12:57:46 PM ---You only need to svn username and password to commit. To check out source you don't need anything.
http://www.rockbox.org/twiki/bin/view/Main/UsingSVN
--- End quote ---
Thanks for your reply. I've downloaded the sources: it was my mistake; to download no username or password is required. Now that I have all the right files, I would try to use cmake again then let you know. Excuse me for the dumb questions but I'm quite new to these things... :-[
mcuelenaere:
--- Quote from: GuybrushThreepwood on August 23, 2008, 01:06:10 PM ---Thanks for your reply. I've downloaded the sources: it was my mistake; to download no username or password is required. Now that I have all the right files, I would try to use cmake again then let you know. Excuse me for the dumb questions but I'm quite new to these things... :-[
--- End quote ---
Instead of directly downloading through SVN, you could've also downloaded the most recent source tarball..
Also it is possible you'll have problems with update_extract recognizing the correct offset; I've got a fix for it ready but as I'm not at home I can't commit it now (though this doesn't affect ZVM v.1.62.02 AFAIK).
For help compiling, don't forget to read utils/zenutils/notes.txt.
--- Quote from: GuybrushThreepwood ---p.s. Is there a manual way alternative to using update extract to extract the firmware from the package executable?
--- End quote ---
Yes there is. While upgrading your ZVM, copy C:\CtJbFW\cttemp\nk.bin to a safe place.
GuybrushThreepwood:
--- Quote from: mcuelenaere on August 23, 2008, 03:13:09 PM ---Instead of directly downloading through SVN, you could've also downloaded the most recent source tarball..
--- End quote ---
Yes, you're right: I've realized this reading the guide on the wiki but this isn't the problem because now I have no problems using the SVN.
--- Quote from: mcuelenaere on August 23, 2008, 03:13:09 PM ---For help compiling, don't forget to read utils/zenutils/notes.txt.
--- End quote ---
Thanks. I've read it and followed the instructions.
--- Quote from: mcuelenaere on August 23, 2008, 03:13:09 PM ---
--- Quote from: GuybrushThreepwood ---p.s. Is there a manual way alternative to using update extract to extract the firmware from the package executable?
--- End quote ---
Yes there is. While upgrading your ZVM, copy C:\CtJbFW\cttemp\nk.bin to a safe place.
--- End quote ---
I already know this trick: it's described on many forums and I've already used it to extract the 1.62.02 nk.bin. The problem is that I've a faulty Zen and on some forums I've read that flashing back to 1.30.02 could help. Though I don't believe this, I'd like to make a try but the 1.30.02 updater doesn't even recognize my player (this isn't the problem with the player which is instead recognized by the other updaters, the problem is another) and because of this doesn't extract the firmware and I can't use that trick.
Updater 1.30.02 is among those that don't work with update_extract and I can't succeed in compiling the revised version. Here's what I did:
- downloaded the sources from the SVN
- set up the build environment for Watcom (I use open-watcom-c-win32-1.7a) by cmake
but, when I try to launch wmake, I get a lot of errors and can't go on any further...
I certainly miss something (as said, I'm quite new to these things) though it seems to me that everything is fine (obviously the situation is different: my environment has certainly some kind of issue)...
mcuelenaere:
--- Quote from: GuybrushThreepwood on August 23, 2008, 04:24:28 PM ---...
I already know this trick: it's described on many forums and I've already used it to extract the 1.62.02 nk.bin. The problem is that I've a faulty Zen and on some forums I've read that flashing back to 1.30.02 could help. Though I don't believe this, I'd like to make a try but the 1.30.02 updater doesn't even recognize my player and because of this doesn't extract the firmware and I can't use that trick.
fw 1.30.02 is among those firmwares that don't work with update_extract and I can't succeed in compiling the revised version. Here's what I did:
- downloaded the sources from the SVN
- set up the build environment for Watcom (I use open-watcom-c-win32-1.7a) by cmake
but, when I try to launch wmake, I get a lot of errors and can't go on any further...
I certainly miss something (as said, I'm quite new to these things) though it seems to me that everything is fine (obviously the situation is different: my environment has certainly some kind of issue)...
--- End quote ---
I'm sorry, but this forum (and this thread) is dedicated to porting Rockbox to the Zen Vision (:M), not helping people fix their player.
And I've never tested Watcom, but as I heard MingW on Windows requires some patches to the source I can imagine open-watcom won't compile zenutils magically without changes...
GuybrushThreepwood:
--- Quote from: mcuelenaere on August 23, 2008, 04:35:33 PM ---I'm sorry, but this forum (and this thread) is dedicated to porting Rockbox to the Zen Vision (:M), not helping people fix their player.
And I've never tested Watcom, but as I heard MingW on Windows requires some patches to the source I can imagine open-watcom won't compile zenutils magically without changes...
--- End quote ---
I understand, in fact I've written about update_extract (I see that many other people did this in this thread) and not about the issue with my player: I don't think I have done something wrong or at least I hope and I think that many other people would like to learn how to compile Rockbox and the tools related to it. At least, this is what I'd like to do. Thank you anyway.
p.s. If the code has to be modified to be compiled under Windows, how was the version on pimpmyzen compiled? Was it cross-compiled?
p.p.s What I meant by "manual way to extract the firmware" was asking what's the updater file structure and how to manually extract the firmware from it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version