Cowon D2

[shotofadds]

Wow, nice work!

Really interesting too - I had no idea that so relatively few hardware registers would be needed to boot the OF under emulation. If the D2 used the hardware I2C controller instead of bit-banging GPIOs I guess it'd be even simpler...

I wonder how hard it would be to incorporate a gdb stub for interactive debugging? Or to incorporate this into something like QEMU which already has one... that would certainly open up some possibilities!

Edited to add: if you modify the emulator to boot from the EEPROM rather than loading in the executable to DRAM, does it successfully boot the OF from the NAND dump?

[Toni]

I have no experience with gdb, but my sansa emulator, I think, has been successfully ported to gdb. I tried to execute the eeprom, but it fails after basic register initialization, when it comes to flash commands. After the reset command 0xffff the second command is 0x50 at location 0xe0000980, which I don't know, what it does. After issuing the command the bootloader reads 16 Byte, but I have no idea, how to fill them.

[saratoga]

You should consider cleaning that up and getting it into SVN.  It'd be a nice tool.

[Llorean]

Shouldn't it be on the wiki, rather than renamed and attached to a forum post?

[karashata]

Removed attachment and moved it to the CowanD2Info wiki page.

[grep]

I have been using rockbox with great satisfaction on my D2 so far, and have been looking for a way to "give back" something to this wonderful project.
Since I'm not a programmer and can't help with all the technical stuff, I've got my eye on that "Write the manual" item on the todo list and have been reading the ManualHowto page.

But before I get started with all that I'd like some confirmation if it's the right time to start with this. Is it perhaps too soon to start writing the D2 manual, since the release is still not a supported rockbox target?

[shotofadds]

I'd say it's a great time, since it's unlikely to ever become supported without a manual

[shotofadds]

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!

[fish]

I'v gave it short try and it works.
The screen turned on and I even can navigate with the keys - very nice

[grep]

@grep, I've now added an SVG drawing of the D2, so that part of the manual is already done for you!

Thanks mate! 

I'm still in the process of "finding my bearings" of the processes surrounding the rockbox manual. I've installed Latex and svn and been doing some test building of manuals to see how that all works.

There's one thing that I don't understand atm:

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?

[shotofadds]

The screen turned on and I even can navigate with the keys - very nice

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...

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?

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]

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.

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]

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!

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]

Hi, I have tried flashing the 3.11 original firmware with your attached firmware

You weren't supposed to do that, only upload it with tcctool.

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?