Rockbox Development > New Ports
Cowon D2
shotofadds:
--- Quote from: fish on September 20, 2009, 08:33:51 PM ---The screen turned on and I even can navigate with the keys - very nice :)
--- End quote ---
Ok, I'll add that change into the main build soon, then you should be able to run a full build. We'll then need to work out what needs to be fixed...
--- Quote from: grep on September 21, 2009, 03:58:29 AM ---The ManualHowTo tells me to create a new directory in Rockbox SVN root (where tools, apps, manual etc are located) and do the "configure" and "make" in there. This strikes me as odd. Doesn't that mean when I commit this to svn, the directory stays on that level? Or is that perhaps to prevent new manual targets to fuck it up for the existing entries under manual?
--- End quote ---
Only the outputs of the build will appear in the build directory you created - it's the same process as building code from SVN. All the source files (and your changes) will go in the main 'manual' folder. It's done like this so that you can have several build folders for building different manuals from the same source code.
The usual way to submit changes is to create a patch file (a set of differences from main SVN) and post it to Flyspray, our bug/patch tracker - see WorkingWithPatches on the wiki. A developer with SVN access will then look at it and commit if it's all is ok. If you get really proficient, you might eventually get commit rights yourself.
D2+Beginner:
Great!
For me the same as fish.
The screen turned on and navigation with keys work well.
Thanks!!!
grep:
--- Quote from: shotofadds on September 21, 2009, 04:15:13 AM ---The usual way to submit changes is to create a patch file (a set of differences from main SVN) and post it to Flyspray, our bug/patch tracker - see WorkingWithPatches on the wiki. A developer with SVN access will then look at it and commit if it's all is ok. If you get really proficient, you might eventually get commit rights yourself.
--- End quote ---
Ah yes, that sounds logical.
I was already wondering where the "quality assurance" would be if you would allow any noob like me to commit stuff to the svn ;)
Ok, first thing on the list now is to figure out all the prerequisites to do a successfull "manual for the D2" build.
I tried to build smt quickly in a d2 directory in the SVN root, but it's riddled with errors of missing stuff ofcourse.
I must say, having no experience in contributing in an opensource project and finding the learning curve a bit steep, it's rather interesting to see how stuff is being organized. :)
helloworld1:
--- Quote from: shotofadds on September 20, 2009, 04:18:22 PM ---To those who cannot get Rockbox to boot on D2+ players with new hardware, please try uploading this image to your player using tcctool:
http://www.mediafire.com/?rwuzjzj1ejy
You might find the backlight comes on now, so you might be able to read the screen. However, I wouldn't expect much else to work (the touchscreen certainly won't). Let me know how it goes...
@grep, I've now added an SVG drawing of the D2, so that part of the manual is already done for you! :D
--- End quote ---
Hi, I have tried flashing the 3.11 original firmware with your attached firmware. The device cannot be turned on after that and I cannot get into the recover mode by pressing and holding the "M" button and turning on. It is really sad. My D2+ is a brick now.
shotofadds:
--- Quote from: helloworld1 on September 21, 2009, 02:57:15 PM ---Hi, I have tried flashing the 3.11 original firmware with your attached firmware
--- End quote ---
You weren't supposed to do that, only upload it with tcctool. :o
Anyway, it's not possible to damage a D2/D2+ just by flashing a bad firmware, as it can always be recovered using the built-in USB boot mode. Are you sure you've reset the device properly and it has a full charge?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version