Rockbox Development > New Ports
Cowon D2
shotofadds:
--- Quote from: GMelchett on October 16, 2009, 02:09:49 PM ---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.
--- End quote ---
You mean I put it in the wrong place - all fixed now though! ;)
--- Quote ---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.
--- End quote ---
This is the current working link.
--- Quote ---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.
--- End quote ---
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:
--- Quote ---This is the current working link.
--- End quote ---
Hmm.. It looks like the datasheet for TCC780, not TCC7801. Sure that you got it right?
--- Quote ---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?
--- End quote ---
No idea. An AC adapter wasn't included when I bought my D2+, so I can't test it.
shotofadds:
--- Quote from: GMelchett on October 17, 2009, 11:47:23 AM ---Hmm.. It looks like the datasheet for TCC780, not TCC7801. Sure that you got it right?
--- End quote ---
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.
--- Quote ---No idea. An AC adapter wasn't included when I bought my D2+, so I can't test it.
--- End quote ---
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:
--- Quote from: GMelchett on October 20, 2009, 01:38:21 PM ---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.
--- End quote ---
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().
--- Quote ---Can anyone explain why adc_tick() looks like it does? It looks strange.
--- End quote ---
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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version