From: Haritz <hza...@fa...> - 2008-10-28 13:26:02
|
Hi! I want to read the A/D register from the TSC2003 Touch Screen Controller. I have read these posts, http://www.nabble.com/I2C-Setup-for-Verdex-td18807158.html http://www.nabble.com/tsc2003-userspace-driver-td18834088.html and http://www.nabble.com/Help%3A-i2c-with-console-vx-td17563347.html#a17563347 but I don't know how to find the address of the register where the data is stored. I think it is 0x0A, but I don't know for sure and I don't know where to find it. The dmesg says that the tsc2003 i2c address is 0x48. See attached dmesg output. http://www.nabble.com/file/p20206503/consoledmesg.txt consoledmesg.txt Whenever I try to access the tsc2003 using the i2c program written by Dave Hylands, I get the following error... i2c 0x48 RecvByte2 ERROR: I2cSetSlaveAddress: Error trying to set slave address to 0x48 (16 Device or resource busy) 0x3b3b How can I solve this? Thank you -- View this message in context: http://www.nabble.com/A-D-reading-using-ConsoleVX-LCD-tp20206503p20206503.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Dave H. <dhy...@gm...> - 2008-10-28 14:42:05
|
Hi Haritz, On Tue, Oct 28, 2008 at 5:42 AM, Haritz <hza...@fa...> wrote: > > Hi! > I want to read the A/D register from the TSC2003 Touch Screen Controller. > > I have read these posts, > http://www.nabble.com/I2C-Setup-for-Verdex-td18807158.html > http://www.nabble.com/tsc2003-userspace-driver-td18834088.html > and > http://www.nabble.com/Help%3A-i2c-with-console-vx-td17563347.html#a17563347 > > but I don't know how to find the address of the register where the data is > stored. This page: <http://focus.ti.com/docs/prod/folders/print/tsc2003.html> hasa link to the datasheet for the TSC2003. Page 16 shows the "register map" (aka commands). > I think it is 0x0A, but I don't know for sure and I don't know where to > find it. That seems incorrect according to the datasheet. > The dmesg says that the tsc2003 i2c address is 0x48. See attached dmesg > output. http://www.nabble.com/file/p20206503/consoledmesg.txt > consoledmesg.txt > > Whenever I try to access the tsc2003 using the i2c program written by Dave > Hylands, I get the following error... > i2c 0x48 RecvByte2 > ERROR: I2cSetSlaveAddress: Error trying to set slave address to 0x48 (16 > Device or resource busy) > 0x3b3b > > How can I solve this? I think that once a proper driver is loaded and claiming a given address, then the i2c program can no longer be used to access that device. You need to use the driver for the device in question. I believe that you could unload the tsc2003 driver and then be able to use the i2c utility. -- Dave Hylands Shuswap, BC, Canada http://www.DaveHylands.com/ |
From: Oliver D. <o.d...@gm...> - 2008-10-29 03:06:48
Attachments:
tsc2003.c
|
Hi, this is a patch for the tsc2003 Touchscreen-Controler. It works only with running Touchscreen/X11 to update the Values. root@gumstix-custom-verdex:~$ cat /proc/tsc2003 vbat1=0 vbat2=0 in1=1920 in2=2400 temp1=896 temp2=1088 xpos1=4080 ypos2=720 pressure=0 By Olli BTW: my Gumstix-Project: http://rcos.multixmedia.org/index.php ;-) |
From: ojai m. <oja...@ya...> - 2008-10-29 21:51:47
|
What should the first boot look like one this LCD? |
From: Haritz <hza...@fa...> - 2008-11-05 12:15:33
|
The errors I mentioned disapeared when I removed the tsc2003 modules from the kernel. The bit to be send is the 0x20 and you get back 2 bytes (last 4 bits allways 0) # i2c 0x48 SendByte 0x20 # i2c 0x48 RecvByte2 0xd3b0 the first byte plus the first 4 bits of the second byte go from 0x000 (0V) to 0xFFF (2.5 V) No robostix needed for 2 analog inputs!!! great!! -- View this message in context: http://www.nabble.com/A-D-reading-using-ConsoleVX-LCD-tp20206503p20340439.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Dante S. <da...@ma...> - 2009-03-09 15:15:04
|
Hi guys, Haritz wrote: > > The errors I mentioned disapeared when I removed the tsc2003 modules from > the kernel. > > The bit to be send is the 0x20 and you get back 2 bytes (last 4 bits > allways 0) > > # i2c 0x48 SendByte 0x20 > # i2c 0x48 RecvByte2 > 0xd3b0 > > the first byte plus the first 4 bits of the second byte go from 0x000 (0V) > to 0xFFF (2.5 V) > I'm trying to do the exact same thing, but I am getting error messages- root@gumstix-custom-verdex:~$ modprobe -r tsc2003 root@gumstix-custom-verdex:~$ i2c 0x48 SendByte 0x20 i2c: error: exhausted retries i2c: msg_num: 0 msg_idx: -2000 msg_ptr: 0 i2c: ICR: 000007e0 ISR: 00000002 i2c: log: [00000442:000007e0] ERROR: I2cSendBytes: ioctl failed: Remote I/O error (121) ERROR: I2cSendBytes failed: -1 root@gumstix-custom-verdex:~$ I should mention I am using a console-vx. I had a consoleLCD-vx lying around so I took its tsc2003 chip and soldered it in place. Maybe I'm missing some other components? Thanks, Dante -- View this message in context: http://www.nabble.com/A-D-reading-using-ConsoleVX-LCD-tp20206503p22413449.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Dante S. <da...@ma...> - 2009-03-10 21:20:48
|
Hi, Haritz wrote: > > The bit to be send is the 0x20 and you get back 2 bytes (last 4 bits > allways 0) > > # i2c 0x48 SendByte 0x20 > # i2c 0x48 RecvByte2 > 0xd3b0 > > the first byte plus the first 4 bits of the second byte go from 0x000 (0V) > to 0xFFF (2.5 V) > No robostix needed for 2 analog inputs!!! great!! > I removed the tsc2003 module as well, but every time I poll the AD1 register I get a 0xff reading. I have a voltage divider that goes from 0 to 2.4V attached to it, and it's powered via the VCC pin on the NSSP part of the console-vx. Any ideas? Thanks, Dante -- View this message in context: http://www.nabble.com/A-D-reading-using-ConsoleVX-LCD-tp20206503p22443828.html Sent from the Gumstix mailing list archive at Nabble.com. |