Cowon D2

[man.dovvn]

 

Nifty, but decompiling/decyphering the firmware is still potentially a huge task.

If we've got it in assembly... hmmm... I've only done one semester of assembly, but if I can deterimine the subroutines for common tasks I can be writing custom programs in hours.

I'll keep an eye on all this but it's coming up to exams for me, so I'm unlikely to have any time for a bit.

[shotofadds]

Apologies, I was referring to this post:

http://www.rockbox.org/mail/archive/rockbox-dev-archive-2007-07/0081.shtml

which has datasheets for the TCC76x - I'd misread this as directly relating to the D2. Hopefully there is some common ground, however. As for the other components, your guess is as good as mine.

[linuxstb]

Would someone be able to make a usb log of the recovery mode driver working with the D2 and make it available to me?

There are various USB sniffers, I've used usbsnoop with success - http://sourceforge.net/projects/usbsnoop/

With this information, I should be able to add support for the D2 for uploading code in USB boot mode to tcctool, which I've just committed to Rockbox SVN:

http://svn.rockbox.org/viewvc.cgi/trunk/utils/tcctool/

[dalmane98]

Would someone be able to make a usb log of the recovery mode driver working with the D2 and make it available to me?

I do not know how to do what you are asking for, but I can provide you with a link to the recovery files.

[linuxstb]

I'm asking for someone with a D2 and the recovery tool to use it to recover their D2, and to make a log (using usbsnoop or another usb logger) of the resulting USB communication.

I don't own a D2, so the recovery tool is no use to me.

[dalmane98]

I have a D2 and the files.

I downloaded usbsnoop and got it installed for the D2 and got a log file from an unbricked D2. Not sure how long I should let it capture data, though.

I am willing to use usbsnoop and the recovery files, but I am not sure how to brick my D2 or at least configure my computer so that it will not recognize the player. Can you help me out here?

My OS is windows XP w/SP2.

Could I just load the USB driver files that the recovery files come with and then try and use them by installing and restarting them using usbsnoop?

I just need a little guidance. I am comfortable with hardware, but not programming.

Someone at  iAudiophile posted his lsusb output for the D2, but it was not bricked:

http://iaudiophile.net/forums/showpost.php?p=149740&postcount=26

Not sure if that will help.

I am willing, just need help.

[linuxstb]

Thanks for the link to the lsusb output, but that's not useful at all.

I've now been given a copy of the recovery application, and the documentation that it came with gave me the info I need.

To give some background, I'm working on a port to the Logik DAX DAB/MP3 player - a cheap 1GB flash player with DAB radio.  It has a TCC773L processor, so similar to the D2.

All Telechips CPUs have a "usb boot" mode.  When a device in USB boot mode is connected to a PC, a firmware binary can be uploaded to the device's RAM and executed - this is a safe way to test-run a new firmware before flashing it.

The recovery mode tool uses this boot mode to upload a small "recovery firmware" to the device, which then continues to talk to the host PC via USB and perform the actual recovery firmware upgrade.

tcctool is a relatively simple tool which implements the PC-side of a USB boot - this is how I've been testing code on my device, and how someone wishing to port Rockbox to the D2 can also safely test code.

If there are any Linux users that would like to test tcctool with the D2, please visit the #rockbox IRC channel and talk to me.  It requires libusb, and hence isn't trivial to get to work in Windows (and I can't help with that).  Hence my request for a Linux user.

[Yeeze]

I posted the lsusb output over at the iaudiophile forum!
I am pretty new to linux, and I don't have the recovery drivers for the D2...
But I want to help!
So if someone can give me the recovery driver, I can see what I can do...
At first I will try to install tcctool... [Done]

[linuxstb]

Unless my tcctool changes don't work, I don't need anyone to test and log the recovery tool.

Can a Linux user do the following:

1) Download the tcctool source from the Rockbox SVN?  You'll need the "subversion" tool installed:

svn co svn://svn.rockbox.org/rockbox/trunk/utils/tcctool tcctool

2) Type "cd tcctool" followed by "make" to compile tcctool.  You'll need libusb installed (including the libusb-dev package).

[NOTE: For the following steps, you will need to become root]

3) Connect your D2 to your PC in USB boot mode - hold the MENU button as you switch the D2 on.  The LCD won't display anything, but typing "lsusb" should show a device with IDs 140e:b021.

If it shows as 140e:b011, then let me know - tcctool won't work if that's the case.

4) If your device is showing as 140e:b021, then you can test tcctool by uploading the "d2N.bin" file from the original firmware.  You should test with the d2N.bin file from the same version of the original firmware that is installed on your device:

./tcctool -d cowond2 /path/to/d2N.bin


This will take a few seconds to upload the firmware file, after which you should see the original firmware run.

[Yeeze]

The D2 boots automatically when conected to the USB...
So I pressed the Menu button and connected the D2, the screen remained black.
When I typed in lsusb it took like 3 seconds longer than normal, but it did not show the D2...
I tried it with sudo lsusb and with lsusb logged in as root, but same result...

Do you know what I did wrong?

[linuxstb]

Can you try typing "sudo lsusb -t" when your D2 is connected in recovery mode and post the output?

[Yeeze]

Yep that worked:

Code: [Select]

Bus#  5
`-Dev#   1 Vendor 0x0000 Product 0x0000
  `-Dev#  22 Vendor 0x140e Product 0xb011
Bus#  4
`-Dev#   1 Vendor 0x0000 Product 0x0000
Bus#  3
`-Dev#   1 Vendor 0x0000 Product 0x0000
Bus#  2
`-Dev#   1 Vendor 0x0000 Product 0x0000
  `-Dev#   2 Vendor 0x0db0 Product 0x6982
Bus#  1
`-Dev#   1 Vendor 0x0000 Product 0x0000
  `-Dev#   4 Vendor 0x046d Product 0xc01d


[linuxstb]

OK, so we know it's using product id b011, rather than b021 like the other Telechips devices.

Unfortunately, it seems the D2 is exhibiting the same behaviour in Linux as my Logik MP3 player, a problem I haven't solved.  tcctool is only actually working under Mac OS X for me - I don't know a solution.

However, tcctool is working fine with the iaudio 7 under Linux, which is why I thought the D2 may also work.

What happens with my Logik player is that the device appears in /proc/bus/usb/devices (which is what the lsusb -t option is parsing), but it's not actually accessible as a usb device, and hence isn't showing up in a normal lsusb - the device times out during the get_configuration() call.

Strangely, I don't get the same problems when running tcctool under Mac OS X.

So there's probably nothing more that can be done unless you're a Linux developer willing to investigate the USB connection issues...

If by any chance, a D2 owner with Mac OS X is reading this, you could try the same test.  I will update tcctool to also look for product ID b011 for the D2.

[Yeeze]

I only got windows XP and linux...

So the problem here is how linux handles usb devices with product ID b011?
And there is nothing that can be done about that?

I will ask over at the iAudiophile forums, I know some people got macs there...!

[punit]

If by any chance, a D2 owner with Mac OS X is reading this, you could try the same test.  I will update tcctool to also look for product ID b011 for the D2.

I couldn't find lsusb on Mac. I tried searching for it on fink but couldn't find the package. Where did you install it from?