Cowon D2

[helloworld1]

Yes, It didn't boot with dual boot mktccboot.
Flashing it with tcctool is OK.

I have found why I cannot use tcctool before. The correct procedure is:
1. Hold "M" button, press reset and then turn on.
2. I should add sudo before tcctool, like:
$sudo ./tcctool -d cowond2 rockbox-newbacklight.bin

lsusb will get this device.
140e:b011 Telechips, Inc. TCC780X-based player (USB Boot mode)

The battery is completely drained. Rockbox cannot charge my battery, so I need to charge it in the original firmware before test it. The backlight is working!

EDIT:
I have tested it briefly. The backlight is working, many else is not including sound ,touch screen. Of course, it is a very good starting point to get the backlight working.

[grep]

After some usefull chatting on IRC, I have decided that for the time being I'm going to concentrate on getting the D2 manual in a somewhat working state added to the svn, and focus first on the hardware buttons and add touchscreen functions later.

To this end I have been making inventory of the button functions and like to run it by you to see if I'm missing something:

In general: Power (long) = Shutdown

In Main Menu:
Minus = up
Plus = Down
Menu = Select

In WPS:
Minus = Volume Down
Plus = Volume Up
Menu = Main menu
Menu (long) = Context Menu

In Context Menu:
Minus = up
Plus = Down
Menu = Select
Power = Back

Ofcourse I need to look at all the plugins and their button assignments, but I want to get the manual going first.

Have I missed anything?

[Maike]

Moin Grep,

in WPS (=While playing screen?) you missed the:

power-button (short): stop (and if selected in bookmarks: create or update bookmark)

Greetings Maike

[Bkd11]

The (Stop) button was changed to a long press of the top-right touchscreen back in 22594 so that you don't accidentally hit it going from hold.

[Maike]

Sorry,
I will search for a newer version of Rockbox.

Greetings Maike

[shotofadds]

@grep,

I think that's the right approach. Getting a manual of any description to build first is definitely a good step! We can add a touchscreen description later once we know exactly how it's going to work. Once you get something that builds, do post it on Flyspray so that others can contribute.

As far as the hardware keys go, it's unfortunately not as straightforward as it should be:

The POWER key should generally be seen as 'back' or 'cancel'. This should apply to all menus/settings/plugins. However there are a few exceptions currently....

In the main menu I'd like to use POWER to go back to the WPS (ie. effectivley 'cancel' the menu), but I'm not quite sure how to achieve that.

Plugins are a bit more complicated since there are effectively three types and each has been implemented differently:

- simple plugins that don't use a menu (eg. demos). POWER is always 'exit'.

- 'application' style plugins that are effectively an extension of the menu system (eg. disktidy) . POWER is 'back' as usual, and going 'back' from the plugin's main menu exits the plugin.

- 'game' style plugins (eg. blackjack, brickmania), where POWER does nothing at all in the menu! Certain others like the JPEG viewer suffer from this as well, which is a rather nasty and inconsistent UI. I think we should look at fixing these...

@helloworld1, thanks for the report. That's about what I expected, so there's plenty of work still to do! Also, did you try an SD card?

[helloworld1]

I used the rockbox on my 16G SD card. It is working fine and I can play music on the card(no sound). The file browser called the internal flash microsd1. and the root is the sd card.

The battery driver is a problem, the battery is empty in default and the rockbox will turn off after a while because of the empty battery.

[shotofadds]

Ok, I will add a section to the wiki to say that battery monitoring, DAC power and the touchscreen all need to be updated for the new power management chip.

I'd guess the FM radio won't work either, can you check if it says "HW detected: yes" in System > Debug > FM Radio ?

[helloworld1]

The fm Hw detected is YES, everything else is 0.

The battery voltage is 3.925V at first, after a while it will jump to 0v.

[grantmasterflash]

A few pages back (while using r22286) I posted about receiving 9 duplicate entries in the database for each music file on my 16gb SDHC card only.  It seemed to only start once I had filled the card with files until there wasn't much space left (~250mb free).  After trying to get to the bottom of what was causing the issue and failing, I eventually reformatted the SDHC card and the problem stopped occurring.  However, I did not fill the card close to capacity immediately after the reformat.  I've been slowly adding tracks from my collection over time.

This has started happening again.  I noticed it first yesterday after upgrading to r22843 and adding more files to the SDHC card so that only 136.8mb were free (14.8gb used).  Again, the dupes only appear for tracks that are on the SDHC card; tracks on the D2 internal memory are not duplicated.  This time, the tracks are duplicated 4-5 times (some tracks appear 4 times, some 5 times). 

I started deleting files gradually from the SDHC card to see if this would resolve the problem.  Each time, I also deleted the .tcd files from .rockbox and reinitialized the db.  After several iterations of this, I now have 1.8 GB of free space on the SDHC card, but still I'm experiencing the dupe db entries problem.

During the initialization of the db, I watch the "Building database" message.  Despite the fact that there are slightly less than 2000 tracks on both the int memory and SDHC, the # of files found in the "Building database" message will go all the way to around 10000 before stopping and informing me of the need to reboot.

The only bug I can find that is similar is FS#8414, although it doesn't appear that it was ever determined exactly what caused the problem.  People there reported resolving it by toggling Directory cache, load db to ram, and auto update, but I've tried these to no avail.  Of course, that bug was reported on an iPod and may not be a good reference point for this problem on a D2, due to the use of an SD card to run Rockbox and save settings.

I defragmented the SDHC card, but it did not resolve the dupe problem.

Anyone else experiencing this with Rockbox on the D2? 

[GodEater]

This doesn't sound like a bug that is specific to the D2, more a general Rockbox one. There have been reports of duplicates being created in the database for a long time, but no-one has figured out what triggers it yet.

I can't personally think of anything specific to the D2 which would cause that at all - so you're likely posting this in the wrong place.

Do a search of the forums for other threads about duplicates in the database, and see if you can't contribute some more info there.

[grantmasterflash]

This doesn't sound like a bug that is specific to the D2, more a general Rockbox one. There have been reports of duplicates being created in the database for a long time, but no-one has figured out what triggers it yet.

I can't personally think of anything specific to the D2 which would cause that at all - so you're likely posting this in the wrong place.

Do a search of the forums for other threads about duplicates in the database, and see if you can't contribute some more info there.

OK.  I thought it might be significant that the only files that are duplicated are ones that reside on the SD card and that files on the D2 internal memory are not duplicated.  Since the SD functionality is a bit unique on the D2 at the moment and my searches didn't turn up any hits where anyone described partial duplicates, I figured I would start here.

Update:

First I noticed that enabling Directory Cache was not being retained after reboots of Rockbox.  Every time I set it to yes, then rebooted, it would be set back to no.

Next I used rbdb.py (from http://www.rockbox.org/wiki/TagcacheDBFormat) to parse my database files, and found that database_4.tcd contained incorrect repeating filenames for every file on my SDHC card. 

For example:

/The Beatles in Mono/With The Beatles/The Beatles in Mono/With The Beatles/The Beatles in Mono/With The Beatles/The Beatles in Mono/With The Beatles/Birthday Party, The/Hits/12_Dead Joe.mp3

/The Beatles in Mono/With The Beatles/The Beatles in Mono/With The Beatles/The Beatles in Mono/With The Beatles/Birthday Party, The/Hits/12_Dead Joe.mp3

/The Beatles in Mono/With The Beatles/The Beatles in Mono/With The Beatles/Birthday Party, The/Hits/12_Dead Joe.mp3

/The Beatles in Mono/With The Beatles/Birthday Party, The/Hits/12_Dead Joe.mp3

/Birthday Party, The/Hits/12_Dead Joe.mp3

That last one is the only one that is correct.  So every file on the SDHC card had one correct filename entry and then 4 incorrect entries under some repetition of /The Beatles in Mono/With The Beatles/.  I checked the /The Beatles in Mono/With The Beatles/ and found that it was empty, had a 0 byte filesize, and had a modified date that was several weeks after all the other directories within /The Beatles in Mono (I put all the albums from that boxset on the card at the same time, so they should all have the same modified date).

I removed /The Beatles in Mono/With The Beatles/ from the card, re-initialized the db in Rockbox, and, of course, no dupes.

I also noticed after this that the Directory Cache setting is being retained from boot to boot.

I can only conclude that some unknown corruption to that /The Beatles in Mono/With The Beatles/ directory occurred at some point after I put those files on the card, because I had previously listened to those files without a problem (and as I said earlier, the dupe problem only started occurring again a few days back - which was a few weeks after those files were already in place).  I'm not blaming Rockbox, but it's something I'll keep an eye on since this is the second time the dupe problem has occurred for me.  The next time it happens, I will be much more diligent about noting exactly what changes I made right beforehand, what OS I used to unmount/eject the card (Windows or Linux, I use both), etc.  I know without a doubt though that I made no changes whatsoever to that problematic directory when the dupes began to occur.

The main thing that can be concluded at this point is that using rbdb.py is a very good way to figure out what files/directories are causing duplicated entry problems.  It also seems that the Directory Cache setting may be a clue as to what's going on.

[shotofadds]

I need a volunteer... somebody who has a D2+ that currently does not work with Rockbox (ie. one with the updated power management chip - PCF50635).

Could you unzip this Rockbox build to the root of your D2 (or SD card), then upload this image using tcctool?  Then tell me:

a) if Rockbox boots
b) if the backlight works
c) if you can adjust the brightness in the General > Display > LCD settings menu
d) if battery voltage monitoring works (in the System > Debug menu)
e) if sound works

@grantmasterflash, I didn't see your update until now - glad you got your problem sorted in the end (and for pointing out how these kind of issues can be diagnosed). I wonder what caused that corruption....?

[GMelchett]

I'm not 100% sure that I got an D2+ with PCF50635. I bought the 16 GB variant a few days ago and it came with firmware 2.11 installed and my own built rockbox.bin (3.4.7) didn't work when loading it via tcctool.

However, all tests with provided binaries were executed successfully, except sound. It is very quiet.

@shotofadds, I'm willing to do futher testing. I though about trying to do the needed changes to rockbox to get PCF50635 supported myself. I write Linux drivers on the same ARM architecture as the D2 got for a living.


Another question, I've been looking at Toni's cowond2 emulator, just got it to compile under linux.
However, I'm confused regarding the input data. A few files are required, "d2.bin" which I assume is
the original firmware, then there are two other files "eeprom.bin", and "wrdata.bin" (or rather "test11.bin" that is currently in use.). I can't figure out how to get them. I know what an eeprom is, but
how do I get it out from the player? Also, Toni mention that a complete flash memory dump is
required. Where is that used in the emulator? wrdata.bin? How do you dump the complete flash,
I assume including the flash oob. (Simple "dd if=/dev/<player device>" does the job?)

Maybe the emulator can be useful for find out how flash wear-n-tear is handled.



 

[shotofadds]

I'm not 100% sure that I got an D2+ with PCF50635. I bought the 16 GB variant a few days ago and it came with firmware 2.11 installed and my own built rockbox.bin (3.4.7) didn't work when loading it via tcctool.

However, all tests with provided binaries were executed successfully, except sound. It is very quiet.

That sounds very much like you have the hardware I'm talking about - thanks for testing it out. If that is the case, you will also find the touchscreen won't work because I haven't written the driver for it yet (although it's in progress). If the touchscreen works, you have the older hardware revision.

I'm a bit confused by the quiet sound - I'm not sure what would cause that. Can I ask you a really stupid question, just to check the obvious things like the volume settings and whether you have replaygain enabled? Also, does the FM radio work (is that quiet too)?

@shotofadds, I'm willing to do futher testing. I though about trying to do the needed changes to rockbox to get PCF50635 supported myself.

I've done a fair amount of work on it already to build the above test images, so I'll get those changes into SVN so you and/or others can test things out some more and try tweaking things yourself... help is always welcome!

I write Linux drivers on the same ARM architecture as the D2 got for a living.

Excellent, we need more people with low-level experience to get interested in this port! What sort of devices are you working with?

Another question, I've been looking at Toni's cowond2 emulator, just got it to compile under linux.
However, I'm confused regarding the input data. A few files are required, "d2.bin" which I assume is
the original firmware, then there are two other files "eeprom.bin", and "wrdata.bin" (or rather "test11.bin" that is currently in use.). I can't figure out how to get them. I know what an eeprom is, but
how do I get it out from the player?

I haven't had the chance to get the emulator working yet myself,

The EEPROM is mapped to an 8KB section of memory at 0xE0000000. You'll need to write some code to dump this from the player - either to SD card or via USB. Maybe ask Toni if he already has the code to do it?  Or you/I could write a plugin to do the job.

Similarly the raw NAND flash needs to be dumped either to SD card (if you have a large enough card!) or over USB. Again some custom code will be needed to do this (dd isn't enough as that won't get you the raw NAND blocks / oob).

I haven't looked at the code, but I assume wrdata.bin is a file that gets written to disk by the emulator  (containing NAND writes)?

What I might do is write a plugin that can dump all this stuff to SD card, and then get someone with a 2GB D2 to run it for us. That should make things a bit easier to handle...!

EDIT: The above changes for PCF50635 support are now in SVN. Lots more work to do though!