Rockbox Development > New Ports
Cowon D2
Yeeze:
Right now I am compiling a new kernel with the depreciated options for usb checked as mentioned here before somewhere... I just need to wait... but in 1 - 3 hours I will know if tcctool will work under ubuntu for me as well...
But don't let this thread go off topic, maybe there should be opened up a new thread about tcctool in the compiling forum...
shotofadds:
--- Quote from: Yeeze on January 30, 2008, 07:44:45 PM ---One question about the input from the touchscreen, what has been done to these values exactly (are they alredy put together out of three measurment's as stated in this document?
--- End quote ---
The X/Y positions are calculated by the PCF50606 chip's ADC, which returns values in the range 0-1023 (0x3ff). The screen position can be calculated using X*LCD_WIDTH/1024 and Y*LCD_HEIGHT/1024.
--- Quote from: Yeeze on January 30, 2008, 07:44:45 PM ---In telechips.c it said the touchscreen driver cannot be put on a tick task... what is that? Should there be a thread?
Is there something like an API for the I2c code or somewhat to get more information about it?
--- End quote ---
To read values from the touchscreen we need to communicate with the PCF50606 chip via the I2C protocol (the PCF datasheet has a good description of this). The normal button drivers etc are run on a 'tick task' (ie as an interrupt, on a 100Hz timer) which means they can occur at any time - potentially while another thread is making use of the I2C bus. That comment in the code serves as a reminder to find a solution, of which there may be many.
The current I2C calls are really only there for testing purposes, and I envisage them being replaced by a single call to a D2 touchscreen driver, which calls a generic PCF50606 driver, which in turn calls the I2C driver.
--- Quote from: Yeeze on January 31, 2008, 05:43:24 AM ---But don't let this thread go off topic, maybe there should be opened up a new thread about tcctool in the compiling forum...
--- End quote ---
Go for it - after all tcctool is not a New Port, is it? ;)
Finally to change the subject entirely, I'm making good progress on the flash driver - I think I've figured out the required block translation, so (in theory at least) it shouldn't be too long before we can read files from the internal memory. I just need to find a few spare hours to sit down and code it...
Llorean:
tcctool is not used in the installation of any current ports. It is, for practical purposes, a component of a new port, and shouldn't be muddying up the discussion elsewhere when the expert(s) for it only exist in one place. Please keep "installation tools" for a new port in the same thread as that new port until the whole thing is "supported" (documented in the manual is what should be for something to leave the new ports area, once there are instructions in the manual for using tcctool, then people can reasonably find out the basics of using it).
shotofadds:
Fair enough, though I think Yeeze was referring to problems setting up an appropriate environment to build tcctool, rather than having trouble running it (so the compiling forum seemed to make sense).
If/when the port is "supported" there won't be any need to run tcctool - I wouldn't expect to see it in the manual as it's purely a development tool that allows us to run code without flashing the device. Final installation can be done by using the OF to flash a retail firmware that has been patched to contain a dual boot mechanism & the Rockbox bootloader.
Although having said that, tcctool is proving to be very useful over at iAudiophile, as it can be used to repair botched firmware upgrades. It probably could do with its own Wiki page, at least.
Yeeze:
After some problems I was able to boot my newly compiled kernel with deprecated usb devices checked...
I am still not able to use tcctool...
here is my setup:
§ uname -a
§ Linux yeeze-desktop 2.6.24 #1 SMP Sun Feb 3 13:35:24 CET 2008 i686 GNU/Linux
$ lsusb -t
$ Bus# 5`-Dev# 1 Vendor 0x0000 Product 0x0000
Bus# 4
`-Dev# 1 Vendor 0x0000 Product 0x0000
Bus# 3
`-Dev# 1 Vendor 0x0000 Product 0x0000
`-Dev# 2 Vendor 0x0db0 Product 0x6982
Bus# 2
`-Dev# 1 Vendor 0x0000 Product 0x0000
`-Dev# 2 Vendor 0x046d Product 0xc01d
Bus# 1
`-Dev# 1 Vendor 0x0000 Product 0x0000
|-Dev# 4 Vendor 0x154b Product 0x0005
`-Dev# 11 Vendor 0x140e Product 0xb011
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version