Cowon D2

[Yeeze]

I think I found some useful information about the display...
I hope it is actually about the display of the D2, I found it through the number on it:

Its an adobe reader document, I found it here (http://www.neodns.co.kr/sub_tft(1).htm), choose the first one
If you want to download it directly from rapidshare, click here
I hope it helps when writing the driver for the LCD Screen.
Actually, I would like to help writing a driver, but I never did this, I got programming experience in c, c++ and java...

[LambdaCalculus]

Actually, I would like to help writing a driver, but I never did this, I got programming experience in c, c++ and java...

Rockbox is mostly written in C, with touches of assembler here and there. You've got C experience, so you're good to go. Grab the source and start reading it to see how it's structured.

[mkdf]

Just tried to load firmware with tcctool under linux - and it works. Firmware was successfully loaded, but after restarting all my settings were destroyed :(
Interesting that after executing "lsusb -v" which gives error "cannot read device status, Connection timed out (110)" tcctool no longer works: "[ERR]  usb_set_configuration failed (-110)".
BTW, I'm using gentoo linux, kernel 2.6.22-gentoo-r8. D2 shows as 140e:b011.

[linuxstb]

Just tried to load firmware with tcctool under linux - and it works. Firmware was successfully loaded, but after restarting all my settings were destroyed
Interesting that after executing "lsusb -v" which gives error "cannot read device status, Connection timed out (110)" tcctool no longer works: "[ERR]  usb_set_configuration failed (-110)".
BTW, I'm using gentoo linux, kernel 2.6.22-gentoo-r8. D2 shows as 140e:b011.

Good to know that it's actually working under Linux as well - to some extent...

Did you use tcctool to load the same version of the firmware that you currently have installed on your device?  A version mismatch would probably cause the settings to be reset.

[mkdf]

Did you use tcctool to load the same version of the firmware that you currently have installed on your device?  A version mismatch would probably cause the settings to be reset.

Yes, that was the reason.

[Yeeze]

So it seems it got a little quiet around here...

First of all, I got the recovery drivers, so if anybody already bricked their device tell me =)

Further more, after mkdf posted he got the firmware loaded on the D2 using tcctool with Gentoo linux I tried to get it working under ubuntu, but no luck, do I need to change the value in the source of tcctool, or what did you do to make it work?

And what can I do, if I got tcctool working?

I looked over the rockbox source code and WOW, I mean I wrote some programs, but I never programmed a driver, and that looks kinda wired for me, are there any tutorials for writing drivers, or how to get the values for the buttons?
(for example the 0x10 for the left button on the iPod)

Another thing I am interested in, could it be possible to implement multitouch? Or is this an issue of the hardware? I mean when I use the paint program on the D2, I can see when I press with two fingers on the screen, it will paint exactly between them, and it is even pressure sensitive... But maybe it would just be too cool to have multitouch...

Is the document about the screen, I posted the other day, useful at all?

One more thing, how a bout an entry in the wiki for the D2? I never did this, and I don't know how to do this, but I think then it is easier, to see the progress.
I found a lot of pictures of the inside on the internet, are those useful, or is it thwe best to take those by ourselves?

[AlexP]

As regards the touch screen you probably want to talk to JDGordon on IRC.  He is currently working on the first touch screen target rockbox has, the M:ROBE 500 and has done some work on adapting rb for it.  None of the existing targets are touch screen

[linuxstb]

Yeeze,

Nice find with the LCD - that PDF is indeed very useful, as it's a datasheet including programming information for the LCD.

That's only half the story though, you also need to determine how the CPU communicates to the LCD controller.  I've just had a quick look at a disassembly of v2.20 of the D2 original firmware, and you can see a function (at offset 0x6b404) which implements the Power On sequence of the LCD as described on page 22 of the datasheet.  (I found it by searching the firmware for constants used in the power-on sequence).

[EDIT: This datasheet doesn't appear to be as useful as first impressions would suggest - it refers to the datasheet for the "S6F2002 IC" for detailed information on the command list and instruction description.  So more googling is needed.]

The purpose of tcctool is to implement the PC side of the Telechips "USB boot mode".  Basically, this means that you can safely upload test code to the D2's RAM and execute it.  When this code inevitably crashes, you just power-cycle/reset the D2, and it will be back to normal.

The tests people have done so far is just to upload the original firmware to the D2.  Its real use is for developers to upload test code.

Yes, a wiki page is very useful for gathering information about a port (this forum thread should be considered temporary, and used for discussion only).  Regarding photos, remember to respect the copyright of others, so yes, it's best to only upload your own photos to the wiki.

[punit]

Couldn't find the datasheet on a quick google search. But came across the LCD driver in the Linux kernel. Here are the links. Maybe prove useful for somebody writing LCD driver for rockbox -

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/video/backlight/ltv350qv.h;h=189112e3fc7aedf5532364c783011f7cdf804607;hb=HEAD
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/video/backlight/ltv350qv.c;h=2eb206bf73e65fb54026d318f281107ab601ec3f;hb=HEAD

linuxstb: Nice trick of finding the function in the disassembly. I guess that'll give some idea about the board layout and connections in the D2.

[linuxstb]

I've started a wiki page for the D2 here:

http://www.rockbox.org/twiki/bin/view/Main/CowonD2Info

Everyone should feel free to edit it and add more info.

Regarding the S6F2002, I found a Linux driver as well, and the comments in it refer to the datasheet being available on the "AVR32 Linux BSP CD".

A quick google shows that CD iso image being available here:

http://www.atmel.com/dyn/products/tools_card.asp?tool_id=3918

[EDIT: No, it's not there...]
I'm currently downloading it, and will post here to say if the datasheet is in fact there.

[shotofadds]

I'm sure one of you guys has figured this already, but looking at the firmware disassembly, the SPI interface to the LCD is accessed by writing the following bits to either 0xF005A028 (to set the pin low) or 0xF005A02C (to set the pin high):

bit 24 = /CS
bit 25 = SCL
bit 26 = SDI

Register and data pairs can then be written as per the diagram in section 6.1 of the LCD datasheet. This would allow us to perform the power-on and power-off sequences given in section 9.

Establishing how RGB data is transferred is another matter entirely though...

[Malle]

So it seems it got a little quiet around here...

First of all, I got the recovery drivers, so if anybody already bricked their device tell me =)

Further more, after mkdf posted he got the firmware loaded on the D2 using tcctool with Gentoo linux I tried to get it working under ubuntu, but no luck, do I need to change the value in the source of tcctool, or what did you do to make it work?

And what can I do, if I got tcctool working?

Hello,
first of all thanks for the efforts already done by so many people. For me as a 'beginner' reading your posts is entering a different world behind the UI.
Neverless I have a bricked D2 (4GB) as well. After a failed F/W upgrade (-> 2.51) it doesn't start up anymore. It also not recognized by my Ubuntu system or windows. But I can find the bugger with lsusb -v, as it is mentioned earlier in this post.
As I mentioned I'm running Ubuntu and therefore I couldn't so far get tcctool working as well. Is there any update?
@Yeeze: can you provide me the recovery drivers as back up, in case there is no running tcctool in the near future? Thanks.
Perhaps this is not the right place to ask for this, but this post is the best I could find, which might help me out.

Thanks anyway for sharing the knowledge.

Malle

[linuxstb]

Please don't turn this thread into a general D2 troubleshooting discussion - it should be limited to discussion related to porting Rockbox.

Discussion of the use of tcctool to help recover broken D2s is happening here:

http://iaudiophile.net/forums/showthread.php?t=17680

[Malle]

ok, thanks for the notice

Malle

[dalmane98]

Tcctool works on a bricked D2.

I bricked my D2 on purpose and was able to recover it using Tcctool.

I used the Windows version.

Thanks Linuxstb for a great tool.