Cowon D2

[Yeeze]

Yes the time stamp updated and the file also changed in size...

I am compiling under ubuntu (7.04) and uploading the file with WinXP emulated with VirtualBox...
I know its complicated, but it works, at least somehow...

I will try to upload the file under a real windows xp...

[Yeeze]

Ok the virtual machine seems to be the problem, in the real windows it worked like a charm... But testing stuff will take really long when you need to reboot every time...

well I will find another way getting tcctool to work under linux...

Under windows I failed, tried cygwin and coLinux...

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?

http://www.atmel.com/dyn/resources/prod_documents/doc8091.pdf.

What calculations are still needed? I just like to play a little with the touchscreen,
and maybe eventually write a useful driver to get easy to use values (absolute X/Y coordinates)
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?

[luck3r]

Yeeze: tcctool works perfectly on openSUSE and Gentoo with default configuration. I know that Debian based distributions tend to be quite "outdated" or having a strange configuration, so I would recommend you trying another distro. (Yes, I dont like *buntu)
If you want an easy configuration and the system should just work out of the box, try openSUSE.
If you want maximum flexibility and configurability, try Gentoo.
I don't want you to use these, it's just a suggestion.

[Bagder]

I know that Debian based distributions tend to be quite "outdated" or having a strange configuration.

Please. That's your opinion and you will find that a large portion of us Rockbox hackers use Debian or Debian-based distros without sharing your views on them. Debian (unstable) is not more outdated than any other distro really, they all tend to be forward and not so forward on various different aspects over time.

Blaming any of this problem on Debian is barking up the entirely wrong tree.

Now, back to cowon D2 and tcctool. What were you saying again?

[luck3r]

Sorry, I forgot to mention that this is my opinion (I've made some very bad experiences with Debian and *buntu). I didn't want to start a discussion about distros.
So, I was saying that tcctool works perfectly on Gentoo and openSUSE.
By the way, detection of my 4GB D2 works.

[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]

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?

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.

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?

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.

But don't let this thread go off topic, maybe there should be opened up a new thread about tcctool in the compiling forum...

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 <-- The D2 in recovery mode

Is there anything I missed, or is just not possible to run tcctool under ubuntu?

At the moment I am only able to compile the bootloader under Linux and then upload it under WinXp... And rebooting every time just takes forever....

[andiator]

@Yeeze
I'm using cygwin successfully on Vista and XP. I did exactly what the tutorial said (http://www.rockbox.org/twiki/bin/view/Main/CygwinDevelopment).
Even get it portable   : installed it on an external usb-drive and using it on XP and Vista pc's.
Well, it takes awhile to compile, but it works.

[Yeeze]

Thanks andiator, but the thing is, I tried cygwin and coLinux on my win xp, but somehow there is nothing working...
For example:
bash-3.2$ mkdir
bash: mkdir: command not found
bash-3.2$

I followed the guide on how to setup cygwin exactly...
With coLinux I can't get a connection to the Internet and so on....
I got really frustrated with windows and since I switched from WinXP to Linux a while ago and I am now on windows only once or twice a week, I thought it might be easier to get tcctool to work under ubuntu.... Also does everything compile under linux without any hassle and it compiles much faster
I will keep trying to get it working under windows....
But if it is possible to have tcctool working under ubuntu, I would prefer it this way...

[andiator]

@Yeeze
So your main OS is linux, sorry can't help with that.
But did you tried the debian-vmware image? (http://www.rockbox.org/twiki/bin/view/Main/VMwareDevelopmentPlatform)
Using vmware player 6 on vista I was able to download and compile the source code. And with the net-share (samba) you can acces your home directory. (enter \\debian in windows explorer).
You need about 3 or 4 GB on your harddrive. The virtual debian is configured to have 256 MB RAM, so you don't need a new and powerfull pc.

[luck3r]

Yeeze: Did you try tcctool with sudo? I don't know anything about your system configuration, but for me it doesn't work as a normal user.

[kugel.]

Thanks andiator, but the thing is, I tried cygwin and coLinux on my win xp, but somehow there is nothing working...
For example:
bash-3.2$ mkdir
bash: mkdir: command not found
bash-3.2$

Looks like your PATH variable is screwed up. mkdir shouldn't be "not found".