Cowon D2

[JdGordon]

jdgordon: I noticed one more thing: in stylus mode, the button_data doesn't seem to contain the x/y values for BUTTON_REL events. Is that intentional? It's not very useful if so...

the BUTTON_REL event is not a real one.. its sent from the general button driver... if its really needed we probaly could fix it to include the button data though

[x5062]

I'm a Korean D2 user,  so I can't English well. I already Installed rockbox in my D2, (my d2 is 2Gb dmb version, 1.55 firmwear.

In my cafe(http://cafe.naver.com/d2d2d2.cafe) , Somebody uploaded the 1.55 firmwear + Rockbox bootloader.

it is 1.55 public firmwear(http://mfiles.naver.net/508765b0abfb9c29055c/data30/2008/5/8/269/d2.bin), about 3.65 mb

and it is patched 1.55 firmwear(http://mfiles.naver.net/6dba588d96c6a1173f5f/data31/2008/5/8/129/d2_patched.zip)about 1.8mb

you know, now rockbox firmwear has a lot of problem(It's not  complete yet?)

1. Can't read SD/MMC card.
2. some plugin is failed. (doom, rockboy, notepad. etc)
3. booting is often show the "file not found", "bad checksum" . bad checksum error's solution = first booting public firmwear, and get off sd card nd put in sd card. so the rockbox booting well
4.Can't save the config-setting.
5. the battery decrease very fast.
6. Can't play the music, movie
7. touch screen often failed
... etc

so I just using rockbox firmwear to confirm the battery ....  ...I'm so sad


Ps. oh, I'm sorry, the rink is wrong.
 http://cafe.naver.com/d2d2d2/492390 <- you can see  d2_patched.zip file and d2n_patched.zip file in this rink.

[davidw89]

Could you install firmware 3.55 and give it a shot?

By the way, what kind of knowledge is required to port Rockbox successful to Cowon D2? Seems like a lot of stuff need to be done in regard to the user interface (being a touchscreen) and themes.

[Llorean]

Themes really have nothing to do with porting.

[shotofadds]

you know, now rockbox firmwear has a lot of problem(It's not  complete yet?)

1. Can't read SD/MMC card.
2. some plugin is failed. (doom, rockboy, notepad. etc)
3. booting is often show the "file not found", "bad checksum" . bad checksum error's solution = first booting public firmwear, and get off sd card nd put in sd card. so the rockbox booting well
4.Can't save the config-setting.
5. the battery decrease very fast.
6. Can't play the music, movie
7. touch screen often failed

It's not complete yet - you can see the current status at the CowonD2Info wiki page. In particular: "NOTE: The current Rockbox build is not functional - it is not in any way a replacement for the Cowon firmware. The following installation instructions are intended for a developer/test audience only."

But we are working on it (slowly)

By the way, what kind of knowledge is required to port Rockbox successful to Cowon D2? Seems like a lot of stuff need to be done in regard to the user interface (being a touchscreen) and themes.

The user interface is a secondary concern really, it works "well enough" already. The most important thing we need now is a good low-level understanding of the hardware and existing Cowon firmware, so that we can implement a more reliable driver for the internal flash and start working on sound output.

Unfortunately the only way to do this is via experimentation and disassembly of the original firmware. So the key skills are C, ARM assembly and most of all, patience.

[x5062]

if the rockbox firmwear become perfect, should I using the .bin patch file? or just change(copy) .rockbox folder and file?

[shotofadds]

The patched .bin (ie. the bootloader) only needs to be updated if there are significant changes. For example, if we improve the NAND driver to remove the "bad checksum" errors.

For other changes, eg. plugins and other general updates, just the .rockbox folder should be enough.

[AlexP]

if the rockbox firmwear become perfect, should I using the .bin patch file? or just change(copy) .rockbox folder and file?

When it becomes ready for non-developers, there *will* ( appear a manual with full installation instructions. 

[shotofadds]

I've made a change to the NAND driver, which may or may not improve reliability slightly (eg. the File Not Found, Read Error, Checksum Failed errors on boot). To test this, you'll need to compile and update both the bootloader and main build.

I'd appreciate if some of you guys could try out the new version over a period of time and report back in a few days whether the latest version is better, worse, or not much different to the existing version. Hopefully we'll see some improvement overall.

With this version I can unzip rockbox.zip to the player and boot into Rockbox straight away, without errors (most of the time!). No messing around

ps. Apologies for the lack of updates recently, I've been rather busy in Real Life(tm) recently and I need a break!

[adamorjames]

I get errors like "File not found" and such when using the new rockbox.zip. It works when I replace the iaudio file the first time usually.
Keep up the great work shotofadds.

[Bkd11]

Great job shotofadds. Boots everytime for me so far after making the new bootloader (d2_patched.bin), even with the last version of rockbox.zip I have the 8gb version by the way.

I'm still using the build (rockbox.zip) that andiator posted in Reply #352 because is has the correct pacbox control mappings. With svn version, right = down and left = up. Mabey andiator can post a patch so someone can commit it to the svn.

Thanks for all your work.

[shotofadds]

I get errors like "File not found" and such when using the new rockbox.zip. It works when I replace the iaudio file the first time usually.

Did you upgrade the bootloader as well, or just rockbox.zip?

I'm still using the build (rockbox.zip) that andiator posted in Reply #352 because is has the correct pacbox control mappings. With svn version, right = down and left = up. Mabey andiator can post a patch so someone can commit it to the svn.

Yeah, a patch would be appreciated - it'd be good to make sure things like this get committed. I'd fix the pacbox mappings myself, but I don't have the ROMs to confirm they are correct.

[andiator]

It was/is busy time for me too. Too much to do in my project, the next test is in the end of the next week and all people you (me) need have vacation 
But well, that's life...

I don't want to post a new patch only because of four lines that are different, so I'm posting it here  , could anyone commit this please?

found in apps/plugins/packbox/pacbox.h:142

#ifdef HAVE_TOUCHPAD
#ifndef PACMAN_UP
#define PACMAN_UP       BUTTON_TOPMIDDLE
#endif
#ifndef PACMAN_DOWN
#define PACMAN_DOWN     BUTTON_BOTTOMMIDDLE
#endif
#ifndef PACMAN_LEFT
#define PACMAN_LEFT     BUTTON_MIDLEFT
#endif
#ifndef PACMAN_RIGHT
#define PACMAN_RIGHT    BUTTON_MIDRIGHT
#endif
#ifndef PACMAN_1UP
#define PACMAN_1UP      BUTTON_BOTTOMLEFT
#endif
#ifndef PACMAN_2UP
#define PACMAN_2UP      BUTTON_BOTTOMRIGHT
#endif
#ifndef PACMAN_COIN
#define PACMAN_COIN    BUTTON_CENTER
#endif
#ifndef PACMAN_MENU
#define PACMAN_MENU    (BUTTON_TOPLEFT|BUTTON_REL)
#endif
#endif



[Edit1] updated ftp (new rockbox version + new patched original FW 2.57 and 3.57)
[Edit2] sorry, the ftp update gone completly wrong, I'm on it
[Edit3] the ftp is working again, the problem was, the files had the windows line end character in the names () like this: d2N...bin'\r', because I changed my patching script with windows editor...
Didn't know it's possible...

[shotofadds]

It was/is busy time for me too. Too much to do in my project, the next test is in the end of the next week and all people you (me) need have vacation 
But well, that's life...

I don't want to post a new patch only because of four lines that are different, so I'm posting it here  , could anyone commit this please?

No problem, I'll commit it later today (assuming nobody else does it first). Thanks!

[adamorjames]

Yeah, I was using an old bootloader. With the newest bootloader it works without error. Also, the plugin Doom doesn't give me lots of  errors anymore (though it stops at "Starting Graphics engine"). Pretty nice. I'm using a 4GB D2 by the way.