Cowon D2

[shotofadds]

There is a small flaw in last nights touchscreen patch. Since the "last_btn = btn" ended up inside if(tsc200x_is_pressed()) {} the latest button will be repeated on and on until you press somewhere else and that new button gets repeated on and on. IE the line must be outside the if.

You mean I put it in the wrong place - all fixed now though!

I would really appreciate if you could mail me the tcc7801 datasheet. The link on the forum is dead, or rather Telechips now require a password for the files, and the datasheet is nowhere else to be found.

This is the current working link.

I tried many times to see if any GPIO pin changed in the "Hardware info" screen, but none did when I inserted/removed the USB cable.

Ok, we'll need to monitor the PCF50635 interrupts (this should work in pretty much the same way as the existing code). Also does D23 change when you insert the AC adapter?

[GMelchett]

This is the current working link.

Hmm.. It looks like the datasheet for TCC780, not TCC7801. Sure that you got it right?

Ok, we'll need to monitor the PCF50635 interrupts (this should work in pretty much the same way as the existing code). Also does D23 change when you insert the AC adapter?

No idea. An AC adapter wasn't included when I bought my D2+, so I can't test it.

[shotofadds]

Hmm.. It looks like the datasheet for TCC780, not TCC7801. Sure that you got it right?

Yes, it's definitely the correct one. The '01' is the only variant of 780x that made it into mass production, as far as I can tell.

No idea. An AC adapter wasn't included when I bought my D2+, so I can't test it.

Ok, I'll assume it's the same for now - I can always check the OF disassembly to be sure...

[GMelchett]

Eventhough power management  isn't top priority at the moment, I feel for starting with it.
I'll start with trying to replace the TIMER0 interrupt that does current_tick++ 100 times a second
with the 32 bit timer/counter hw.

Can anyone explain why adc_tick() looks like it does? It looks strange.

 

[shotofadds]

I'll start with trying to replace the TIMER0 interrupt that does current_tick++ 100 times a second
with the 32 bit timer/counter hw.

I don't really see what you'd achieve by changing it. And it could be tricky since the 32bit counter is already being used for the high resolution timer USEC_TIMER - see system-target.h and clock_init().

Can anyone explain why adc_tick() looks like it does? It looks strange.

Ah OK, I forgot an IRQ in my list - the ADC conversions are clearly IRQ based.

It's quite straightforward: adc_tick() is called once each tick, and it just requests that the CPU starts the ADC conversion process. When that is finished, the ADC interrupt fires and the results are read. Calls to adc_read() just return the cached values.

If by "strange" you mean the #ifdef BOOTLOADER stuff, it's because at one time IRQs did not work in the bootloader - that's not a problem now, so I should remove those lines.

[GMelchett]

You don't achieve much by just replacing the TIMER0 interrupt. But in order to reach good playback hours, you have to aim to reduce the number of wake-ups during idle to just a handful per second.
 

[tomers]

Just to let you know, I am working on implementing rbutil support in http://www.rockbox.org/tracker/task/10728

It will hopefully committed in the near future.

[Gunbuster]

Is there any way to rotate the screen (the left of the screen being the top, and the right the bottom) ?
I want to display big covers in 240x240 pixels like i did with my gigabeat F, which is not possible with de default display.
Thank you.

[tomers]

Is there any way to rotate the screen (the left of the screen being the top, and the right the bottom) ?
I want to display big covers in 240x240 pixels like i did with my gigabeat F, which is not possible with de default display.

Take a look at the themes site: http://themes.rockbox.org/index.php?target=cowond2. Especially, notice the SpartanBlack theme:

[fish]

I just want to say thank your for making it work on the newer D2+ Devices.
Finally a usable firmware - the original firmware really suck I think.. I never had a piece of hardware with such a bad usability. But with Rockbox it just rocks

[tomers]

Finally a usable firmware - the original firmware really suck I think.. I never had a piece of hardware with such a bad usability. But with Rockbox it just rocks

Hi Fish,

I found that Cowon D2 has some usability issues related to keymaps.
If you would like to volunteer and contribute to Rockbox (no need for programming knowledge), I could use your contribution with compiling a list of desirable key-mappings for various screens and plugins on Rockbox, which would make it more usable. I'll try to fix whatever you find :-)

[shotofadds]

Tomers - regarding your recent keymap changes, I really don't agree with some of them.

In the FM Radio screen the +/- keys could previously be used to adjust volume (their natural usage, consistent with the WPS and also how they're used in the OF). Why did you change this to prev/next?

Also in the FM screen, the MENU key would previously open the menu (again the natural, expected function). Now it needs a long-press - why did you do this?

You also removed the second ACTION_TREE_WPS line that I only recently added. What was the reason for this?

Please can you revert these changes.

[lynix]

Hi, there!

I want to thank you guys for working on D2 support

I just managed to build the dev tools and install Rockbox on an SD in my D2. Unfortunately I can't hear any sound when playing MP3s while FM radio is working fine... will check this later.

I also have an AC adapter so if I can help by providing some information, just tell me
I also speak C and a bit MIPS, if that helps ^^

Thanks again for a firmware that rocks!


lynix

EDIT: removed typo ^^

[tomers]

Tomers - regarding your recent keymap changes, I really don't agree with some of them.

In the FM Radio screen the +/- keys could previously be used to adjust volume (their natural usage, consistent with the WPS and also how they're used in the OF). Why did you change this to prev/next?

Also in the FM screen, the MENU key would previously open the menu (again the natural, expected function). Now it needs a long-press - why did you do this?

You also removed the second ACTION_TREE_WPS line that I only recently added. What was the reason for this?

Please can you revert these changes.

Hi shotofadds, I am sorry to cause a regression with the keymaps. I agree with your comments and reverted the changes you've referred to in r23936. I did not mean to change anything that worked as expected previously, rather to add functionality in areas where things didn't work at all :-) I am sorry if I caused any inconvenience to you or to other D2 users. I am now working on making the D2 more usable, and for every two steps forward, one step might be taken backwards. I'll be more careful now.
Thank you for your feedback!

Tomer

[robbie]

current build is broken now (get an error when opening the file with winrar).