Cowon D2

[shotofadds]

I've committed a slightly modified version of FranzD2's LCD fixes, which seem to reliably fix the missing/repeated LCD lines (at least for me).

Let me know if there's still a problem for anyone else...

[FranzD2]

For some days it worked fine for me but today i turned on my d2 and the screen was messed up again, i think that the delay is still too short.
Anyone else noticed this? shoto?

[dragongod]

hi everybody, i'm a newbie of both D2 and rockbox, and i want to do sth. for this wonderful project. can anyone tell me where to start? i mean since there is no datasheet or SDK of telechips, should i just begin to read the source code or read sth. else before that?

[Llorean]

You could start by reading the forum posting guidelines.

[shotofadds]

For some days it worked fine for me but today i turned on my d2 and the screen was messed up again, i think that the delay is still too short.
Anyone else noticed this? shoto?

Hi Franz,

Could you try editing line 80 of lcd-cowond2.c, so that FREQ>>23 now reads FREQ>>22? This will double the current delay, so let me know if it works any better for you.

[FranzD2]

I just tried but i've got the top line repeated at the bottom, it seems that a value of 22 is worse than 23, is it possible?
By the way i'm investigating the problem in the touchscreen driver which takes wrong presses, i'm almost sure that the problem is the lack of a delay between the adc start command and the read:

Code: [Select]

 pcf50606_write(PCF5060X_ADCC2, (0xE<<1) | 1); /* ADC start X+Y */
 pcf50606_read_multiple(PCF5060X_ADCS1, buf, 3);

in button-cowond2.c.
Putting a delay here seem to solve this problem but it slows down when i keep the screen button pressed.

[shotofadds]

I just tried but i've got the top line repeated at the bottom, it seems that a value of 22 is worse than 23, is it possible?

Strange, both values seem to work here. Looks like I'll need to do some more work on this...

Putting a delay here seem to solve this problem but it slows down when i keep the screen button pressed.

Yes, the touchscreen handling is one area that could do with some serious re-work. Inserting delays should be a last resort as this code is run from IRQ context, and like you say, it will cause slow-downs. If I remember correctly, the PCF50606 datasheet states that a delay should not be required between the start and read commands.

I have some changes in my local tree that might improve things, but I was waiting to see how reliable they turned out to be!

Finally, I've committed some improvements to the NAND driver (in r19118), so please try out the new version and let me know how it goes. Cheers! 

EDIT: To get the full benefit of any improvements to the NAND driver you will also need to update and re-flash the bootloader.

[FranzD2]

  !!!NAND!!!  

However i've just checked on the pcf50606 user manual and it says that the coversion time is 25 us.

[vodi]

hi!
i just loaded r19130 (incl. new bootloader) into my D2!

The Bootup-logo works, but after this there is again the "2 lines from top on bottom" problem. everytime.

[shotofadds]

Wow, that was quick.. 

Could you try one thing quickly for me - a variation of the "fix" I suggested to FranzD2 earlier? Could you try editing line 80 of lcd-cowond2.c, so that FREQ>>23 now reads FREQ>>24?

I just booted up the D2 15 times in a row with this setting and didn't see the problem once...

[vodi]

oh ja

FREQ>>24 works for me also!

[shotofadds]

Ok, I've committed that change.

For everyone else:

From r19130 onwards the main rockbox binary has been renamed to "rockbox.d2", so you will need to update the bootloader and flash a new patched firmware in order to use the new builds (since the old bootloader would still be looking for rockbox.iaudio).

The reason for making this change is twofold: 1) the D2 has never been marketed as part of the "iAudio" range, so I removed those references from the code, and 2) it forces people to update their bootloaders to the new more reliable NAND driver. It seemed a convenient time to do it.

[shotofadds]

Almost one week (and over 1000 page views) later, there hasn't been any comment regarding reliability of the updated NAND driver. Did anyone try it?

Is the requirement to build a new bootloader from source holding people back from testing this? Would a pre-built bootloader.bin and mktccboot be helpful, so that you can patch your own firmware file without having to build Rockbox?

[Yeeze]

I'm sorry, I would love to test it, but I can't find my D2 since weeks :'(
But as soon as I fing it I'll let you know

[gevaerts]

It's a lot better than last time I tried. I installed the bootloader, unpacked the zip, and it actually booted! I'll play with it a bit and report back