Rockbox Development > New Ports
Cowon D2
shotofadds:
--- Quote from: GMelchett on October 11, 2009, 01:44:18 PM ---Weird. I wonder how any other device could work on the I2C bus if you can access "the touchscreen"-chip in that fashion.
--- End quote ---
I may have described it wrongly - a slave address is always sent, so other devices should just ignore the data that follows. It seems the Cowon firmware does something very strange:
- send slave address (0x90) followed by register address (0x80/0x90)
- send slave address (0x90) followed by two byte reads
whereas it could just:
- send slave address (0x90), followed by register address (0x80/0x90), followed by two byte reads.
But anyway, it doesn't seem to matter. :)
--- Quote ---I've added both the touchscreen patch and the eeprom dump on the tracker.
Adding a complete flash, including oob, dumping code would make the eeprom dumper more useful. Then someone might give us a nice 2 GB image.
--- End quote ---
Thanks, I saw those and started making some comments. I will do some work on the dumper plugin...
--- Quote ---By the way, does the name have to be unique? IE wonder about the cowond2 appendix.
--- End quote ---
No, it's not really necessary, but it's convention for those .c's in the target/ tree to have such a suffix.
--- Quote ---I will have a look at if I can fix the clock. The date is correct but the clock says 00:00:00.
--- End quote ---
It can't be correct unless the date is coming from a file timestamp or some thing - the RTC is currently trying to read from the PCF50606 (check SVN shortly for a fix) :P
helloworld1:
--- Quote from: shotofadds on October 08, 2009, 06:44:32 PM ---I need a volunteer... somebody who has a D2+ that currently does not work with Rockbox (ie. one with the updated power management chip - PCF50635).
Could you unzip this Rockbox build to the root of your D2 (or SD card), then upload this image using tcctool? Then tell me:
a) if Rockbox boots
b) if the backlight works
c) if you can adjust the brightness in the General > Display > LCD settings menu
d) if battery voltage monitoring works (in the System > Debug menu)
e) if sound works
@grantmasterflash, I didn't see your update until now - glad you got your problem sorted in the end (and for pointing out how these kind of issues can be diagnosed). I wonder what caused that corruption....?
--- End quote ---
a. rockbox boots.
b. backlight works.
c. backlgiht brightness works.
d. Battery voltage starts out as 3.925(not correct( but after a while itis 4.098 and is correct.
e. sound works.
f. FM radio works, but the touchscreen is notworking so I cannot select the channel.
GREAT WORK!
GMelchett:
--- Quote ---It can't be correct unless the date is coming from a file timestamp or some thing - the RTC is currently trying to read from the PCF50606 (check SVN shortly for a fix) :P
--- End quote ---
@shotofadds: Your rtc patch definitely changed things. On the good side, the seconds are moving and there is a system time that moves at a approximately correct speed. However it says 09:37 when it should be 20:01. The system date says April 23 2005. The date was correct before your rtc patch.
Btw, I'm considering changing the touchscreen calibration code to calibrate two more spots, the (0,0) and (LCD_WIDTH, LCD_HEIGHT) for getting the correct hw values, not just my hardcoded ones.
shotofadds:
You should find these things work in the main build now, so hopefully there's no need for you to download test images or use tcctool any more! The clock "might" work too, but no promises.
--- Quote from: helloworld1 on October 12, 2009, 10:00:44 AM ---f. FM radio works, but the touchscreen is notworking so I cannot select the channel.
--- End quote ---
If you can compile your own builds, there is a patch at FS#10671 that implements the touchscreen driver. It still needs a bit of work, but shouldn't be too long before it's in the main build.
ps. it's normal for the battery voltage to start at a set value - it's an average reading and has to start somewhere that isn't zero!
shotofadds:
--- Quote from: GMelchett on October 12, 2009, 02:25:22 PM ---@shotofadds: Your rtc patch definitely changed things. On the good side, the seconds are moving and there is a system time that moves at a approximately correct speed. However it says 09:37 when it should be 20:01. The system date says April 23 2005. The date was correct before your rtc patch.
--- End quote ---
The correct date can't have been read by the old driver, it was probably failing and using the build date as a fallback. The current build reads the correct fields from the PCF chip, but they appear to contain invalid data. What happens if you try to set the time in Rockbox? Does it persist (and does it affect what the Cowon firmware displays)? Maybe the stock firmware is using the TCC7801 RTC instead...
--- Quote ---Btw, I'm considering changing the touchscreen calibration code to calibrate two more spots, the (0,0) and (LCD_WIDTH, LCD_HEIGHT) for getting the correct hw values, not just my hardcoded ones.
--- End quote ---
In theory only the three spots are needed - does it work at all if you remove your hard-coded scaling?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version