From: Bill G. <bg...@bi...> - 2007-12-28 12:57:37
|
Steve Sakoman wrote: > Eric, > > I finally got some time to devote to seriously looking at the > touchscreen driver rather than a few snatched moments here and there. > > Five minutes with a logic analyzer on the i2c lines showed where all > those i2c timeout messages were coming from: the driver was > attempting to probe adressess 48, 49, 4a, and 4b. Of course the chip > only answers to the first address, so the driver tries for a while and > then gives up and prints the messages. A simple one line fix limits > the probe to just the proper address. > D'oh! :) The board I wrote that driver for had two tsc2003's on it, with provisions for at least one more. Over time, it became so natural to me to have the driver probe all possible ports that I didn't even "see" that code anymore. Sorry!! Props to you for sorting this out, despite my "help". :) > That plus a udev rule to map tsc2003 events to /dev/input/touchscreen > got us a working touchscreen on the x11 image. > > Still have those RGB18 nasties to deal with on fonts & icons . . . > I think there was some progress on this posted on l-a-k about six months ago. b.g. -- Bill Gatliff bg...@bi... |
From: Steve S. <sa...@gm...> - 2007-12-23 03:54:43
|
Erick, It isn't necessary to add pullups to the i2c lines on the tsc2003. If you try playing around with the tsc2003 using Dave Hyland's excellent i2c command line program you will find that you can talk to the chip just fine. I was able to poke around and read the various registers and got back reasonable values. If you read the driver output messages you will see that it does succeed in its first probe of the chip. Something goes awry after that point though. I've been too swamped with other tasks to look into this, but hopefully will get to it sometime over the holidays. Steve On Dec 22, 2007 7:00 PM, thaGod <th...@gm...> wrote: > > I have gone as far as you in this new fix for the touchscreen driver. You > might try adding pullup resistors as described in the previous touchscreen > thread. > > TI TSC2003 touchscreen controller (supplied with Gumstix Samsung display) > > I haven't re-probed the touchscreen controller with my o-scope since I've > added this jumper, but it can't solve the pullup problem so I can only > assume that they must still be added. Don't take this for gospel, but that > message would indicate exactly what you would expect from an i2c circuit > with no pullups. There must be pullups in order to free the line for > transmission. > > I added these pullups before by soldering jumper wire to the SDL and SCL > lines of the tsc2003 and then clipping resistors in line with VCC... not an > elegant solution, but it will do for testing. Good luck... maybe I'll get > back around to feeling this out the rest of the way too. > > Erick > > > > Magnus Ekhall wrote: > > > > Demetris Zavorotnichenko wrote: > >> Why, what is wrong with this one ? Are you having problems ? > >> > >> > >> Demetris Z. > >> > >> > > > > Yes, at the moment I get the following errors when I insmod the driver: > > " > > i2c_adapter i2c-1: i2c_pxa_set_slave: wait timedout > > tsc2003_i2c_detect: probing address 0x48 > > i2c_adapter i2c-1: i2c_pxa: timeout waiting for bus free > > " > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2005. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > -- > View this message in context: http://www.nabble.com/Touchscreen-driver-TSC2003-i2c-timeout-tp14445072p14475397.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Thomas K. B. <tkb...@ba...> - 2007-12-23 20:32:23
|
It looks like there have been a number of people who have tried to get a = GUI working for the Gumstix. Using the current buildroot, I have tried to get Qtopia compiled and = microwin. Focusing on microwin, for some reason I had to move all of the header = files into the various source directories to get it to compile. This = got me a long way, but I'm getting an error that puzzles me. In microwin/src/nanox/client.c I get an error that says = 'PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP' undeclared here (not in = function). >From what I can tell, the client.c has an include statement for = "lock.h", which declares the variable. I've tried taking some of the = "if" statements out of the lock.h file to make sure that it declares the = variable, and it still doesn't compile. I'm using the current buildroot and these just don't compile correctly. = Anyone offer any advice to get this to compile? Sincerely, Thomas K. Bailey K. Ronald Bailey & Associates Co. L.P.A. 220 West Market Street P.O. Box 830 Sandusky, Ohio 44871-0830 Phone: 419-625-6740 Fax: 419-625-2021 www.baileyandassoc.com |
From: thaGod <th...@gm...> - 2007-12-23 21:17:48
|
I see. That's good news.. although I just don't understand why I'm reading both lines low on my oscope with no pullups added. It would help to have access to the mobo schematics ;) kidding of course. Maybe some pertinent info.. maybe not, but the busy bus messages come whenever the 2nd module is loaded of the i2c-pxa/tsc2003 pair. Meaning if you load tsc2003 first.. no errors, but they come when you load i2c-pxa. You've probably already noticed. Erick Steve Sakoman wrote: > > Erick, > > It isn't necessary to add pullups to the i2c lines on the tsc2003. > > If you try playing around with the tsc2003 using Dave Hyland's > excellent i2c command line program you will find that you can talk to > the chip just fine. > > I was able to poke around and read the various registers and got back > reasonable values. > > If you read the driver output messages you will see that it does > succeed in its first probe of the chip. Something goes awry after > that point though. I've been too swamped with other tasks to look > into this, but hopefully will get to it sometime over the holidays. > > Steve > > On Dec 22, 2007 7:00 PM, thaGod <th...@gm...> wrote: >> >> I have gone as far as you in this new fix for the touchscreen driver. You >> might try adding pullup resistors as described in the previous >> touchscreen >> thread. >> >> TI TSC2003 touchscreen controller (supplied with Gumstix Samsung display) >> >> I haven't re-probed the touchscreen controller with my o-scope since I've >> added this jumper, but it can't solve the pullup problem so I can only >> assume that they must still be added. Don't take this for gospel, but >> that >> message would indicate exactly what you would expect from an i2c circuit >> with no pullups. There must be pullups in order to free the line for >> transmission. >> >> I added these pullups before by soldering jumper wire to the SDL and SCL >> lines of the tsc2003 and then clipping resistors in line with VCC... not >> an >> elegant solution, but it will do for testing. Good luck... maybe I'll get >> back around to feeling this out the rest of the way too. >> >> Erick >> >> >> >> Magnus Ekhall wrote: >> > >> > Demetris Zavorotnichenko wrote: >> >> Why, what is wrong with this one ? Are you having problems ? >> >> >> >> >> >> Demetris Z. >> >> >> >> >> > >> > Yes, at the moment I get the following errors when I insmod the driver: >> > " >> > i2c_adapter i2c-1: i2c_pxa_set_slave: wait timedout >> > tsc2003_i2c_detect: probing address 0x48 >> > i2c_adapter i2c-1: i2c_pxa: timeout waiting for bus free >> > " >> > >> > >> > >> ------------------------------------------------------------------------- >> > This SF.net email is sponsored by: Microsoft >> > Defy all challenges. Microsoft(R) Visual Studio 2005. >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> > _______________________________________________ >> > gumstix-users mailing list >> > gum...@li... >> > https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Touchscreen-driver-TSC2003-i2c-timeout-tp14445072p14475397.html >> Sent from the Gumstix mailing list archive at Nabble.com. >> >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2005. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://www.nabble.com/Touchscreen-driver-TSC2003-i2c-timeout-tp14445072p14481909.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Steve S. <sa...@gm...> - 2007-12-24 00:40:11
|
> I see. That's good news.. although I just don't understand why I'm reading > both lines low on my oscope with no pullups added. It would help to have > access to the mobo schematics ;) kidding of course. This afternoon I soldered wires to i2c clk, data, int, and ground so I can easily probe the signals. At boot clk, data, and int are pulled high. I can see clk and data wiggle when I use the i2c tool. Not sure why you see no signals! Steve > Maybe some pertinent info.. maybe not, but the busy bus messages come > whenever the 2nd module is loaded of the i2c-pxa/tsc2003 pair. Meaning if > you load tsc2003 first.. no errors, but they come when you load i2c-pxa. > You've probably already noticed. > > Erick > > > > Steve Sakoman wrote: > > > > Erick, > > > > It isn't necessary to add pullups to the i2c lines on the tsc2003. > > > > If you try playing around with the tsc2003 using Dave Hyland's > > excellent i2c command line program you will find that you can talk to > > the chip just fine. > > > > I was able to poke around and read the various registers and got back > > reasonable values. > > > > If you read the driver output messages you will see that it does > > succeed in its first probe of the chip. Something goes awry after > > that point though. I've been too swamped with other tasks to look > > into this, but hopefully will get to it sometime over the holidays. > > > > Steve > > > > On Dec 22, 2007 7:00 PM, thaGod <th...@gm...> wrote: > >> > >> I have gone as far as you in this new fix for the touchscreen driver. You > >> might try adding pullup resistors as described in the previous > >> touchscreen > >> thread. > >> > >> TI TSC2003 touchscreen controller (supplied with Gumstix Samsung display) > >> > >> I haven't re-probed the touchscreen controller with my o-scope since I've > >> added this jumper, but it can't solve the pullup problem so I can only > >> assume that they must still be added. Don't take this for gospel, but > >> that > >> message would indicate exactly what you would expect from an i2c circuit > >> with no pullups. There must be pullups in order to free the line for > >> transmission. > >> > >> I added these pullups before by soldering jumper wire to the SDL and SCL > >> lines of the tsc2003 and then clipping resistors in line with VCC... not > >> an > >> elegant solution, but it will do for testing. Good luck... maybe I'll get > >> back around to feeling this out the rest of the way too. > >> > >> Erick > >> > >> > >> > >> Magnus Ekhall wrote: > >> > > >> > Demetris Zavorotnichenko wrote: > >> >> Why, what is wrong with this one ? Are you having problems ? > >> >> > >> >> > >> >> Demetris Z. > >> >> > >> >> > >> > > >> > Yes, at the moment I get the following errors when I insmod the driver: > >> > " > >> > i2c_adapter i2c-1: i2c_pxa_set_slave: wait timedout > >> > tsc2003_i2c_detect: probing address 0x48 > >> > i2c_adapter i2c-1: i2c_pxa: timeout waiting for bus free > >> > " > >> > > >> > > >> > > >> ------------------------------------------------------------------------- > >> > This SF.net email is sponsored by: Microsoft > >> > Defy all challenges. Microsoft(R) Visual Studio 2005. > >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> > _______________________________________________ > >> > gumstix-users mailing list > >> > gum...@li... > >> > https://lists.sourceforge.net/lists/listinfo/gumstix-users > >> > > >> > > >> > >> -- > >> View this message in context: > >> http://www.nabble.com/Touchscreen-driver-TSC2003-i2c-timeout-tp14445072p14475397.html > >> Sent from the Gumstix mailing list archive at Nabble.com. > >> > >> > >> > >> ------------------------------------------------------------------------- > >> This SF.net email is sponsored by: Microsoft > >> Defy all challenges. Microsoft(R) Visual Studio 2005. > >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> _______________________________________________ > >> gumstix-users mailing list > >> gum...@li... > >> https://lists.sourceforge.net/lists/listinfo/gumstix-users > >> > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2005. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > -- > View this message in context: http://www.nabble.com/Touchscreen-driver-TSC2003-i2c-timeout-tp14445072p14481909.html > > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: thaGod <th...@gm...> - 2007-12-25 17:06:04
|
Well.. the only obvious answer is I must have done it wrong! I did do this a little different than you and I haven't tried it since I added the jumper wire. I was soldering jumper wire to the SCL and SDA wires on the tsc2003 on the consoleLCD-vx board for monitoring. It's entirely possible that I just don't understand the entire circuit. Erick Steve Sakoman wrote: > >> I see. That's good news.. although I just don't understand why I'm >> reading >> both lines low on my oscope with no pullups added. It would help to have >> access to the mobo schematics ;) kidding of course. > > This afternoon I soldered wires to i2c clk, data, int, and ground so I > can easily probe the signals. At boot clk, data, and int are pulled > high. I can see clk and data wiggle when I use the i2c tool. > > Not sure why you see no signals! > > Steve > >> Maybe some pertinent info.. maybe not, but the busy bus messages come >> whenever the 2nd module is loaded of the i2c-pxa/tsc2003 pair. Meaning if >> you load tsc2003 first.. no errors, but they come when you load i2c-pxa. >> You've probably already noticed. >> >> Erick >> >> >> >> Steve Sakoman wrote: >> > >> > Erick, >> > >> > It isn't necessary to add pullups to the i2c lines on the tsc2003. >> > >> > If you try playing around with the tsc2003 using Dave Hyland's >> > excellent i2c command line program you will find that you can talk to >> > the chip just fine. >> > >> > I was able to poke around and read the various registers and got back >> > reasonable values. >> > >> > If you read the driver output messages you will see that it does >> > succeed in its first probe of the chip. Something goes awry after >> > that point though. I've been too swamped with other tasks to look >> > into this, but hopefully will get to it sometime over the holidays. >> > >> > Steve >> > >> > On Dec 22, 2007 7:00 PM, thaGod <th...@gm...> wrote: >> >> >> >> I have gone as far as you in this new fix for the touchscreen driver. >> You >> >> might try adding pullup resistors as described in the previous >> >> touchscreen >> >> thread. >> >> >> >> TI TSC2003 touchscreen controller (supplied with Gumstix Samsung >> display) >> >> >> >> I haven't re-probed the touchscreen controller with my o-scope since >> I've >> >> added this jumper, but it can't solve the pullup problem so I can only >> >> assume that they must still be added. Don't take this for gospel, but >> >> that >> >> message would indicate exactly what you would expect from an i2c >> circuit >> >> with no pullups. There must be pullups in order to free the line for >> >> transmission. >> >> >> >> I added these pullups before by soldering jumper wire to the SDL and >> SCL >> >> lines of the tsc2003 and then clipping resistors in line with VCC... >> not >> >> an >> >> elegant solution, but it will do for testing. Good luck... maybe I'll >> get >> >> back around to feeling this out the rest of the way too. >> >> >> >> Erick >> >> >> >> >> >> >> >> Magnus Ekhall wrote: >> >> > >> >> > Demetris Zavorotnichenko wrote: >> >> >> Why, what is wrong with this one ? Are you having problems ? >> >> >> >> >> >> >> >> >> Demetris Z. >> >> >> >> >> >> >> >> > >> >> > Yes, at the moment I get the following errors when I insmod the >> driver: >> >> > " >> >> > i2c_adapter i2c-1: i2c_pxa_set_slave: wait timedout >> >> > tsc2003_i2c_detect: probing address 0x48 >> >> > i2c_adapter i2c-1: i2c_pxa: timeout waiting for bus free >> >> > " >> >> > >> >> > >> >> > >> >> >> ------------------------------------------------------------------------- >> >> > This SF.net email is sponsored by: Microsoft >> >> > Defy all challenges. Microsoft(R) Visual Studio 2005. >> >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> >> > _______________________________________________ >> >> > gumstix-users mailing list >> >> > gum...@li... >> >> > https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > >> >> > >> >> >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/Touchscreen-driver-TSC2003-i2c-timeout-tp14445072p14475397.html >> >> Sent from the Gumstix mailing list archive at Nabble.com. >> >> >> >> >> >> >> >> >> ------------------------------------------------------------------------- >> >> This SF.net email is sponsored by: Microsoft >> >> Defy all challenges. Microsoft(R) Visual Studio 2005. >> >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> >> _______________________________________________ >> >> gumstix-users mailing list >> >> gum...@li... >> >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> >> > >> > >> ------------------------------------------------------------------------- >> > This SF.net email is sponsored by: Microsoft >> > Defy all challenges. Microsoft(R) Visual Studio 2005. >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> > _______________________________________________ >> > gumstix-users mailing list >> > gum...@li... >> > https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Touchscreen-driver-TSC2003-i2c-timeout-tp14445072p14481909.html >> >> Sent from the Gumstix mailing list archive at Nabble.com. >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2005. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://www.nabble.com/Touchscreen-driver-TSC2003-i2c-timeout-tp14445072p14496247.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Steve S. <sa...@gm...> - 2007-12-25 23:54:23
|
Erick, There's easy access to the i2c data, clock, and interrupt lines -- they all come out to plated through holes. The only dicey soldering is to one leg of the pull up resistor for the interrupt. You don't need to touch the tsc2003 chip itself! And now that I've verified that there are pullups and live i2c signaling, the only jumper that is necessary is the one that I previously posted a diagram for. I have some theories on why it might not be working. I hope to get a chance to pursue this tomorrow when I'm back on the job :-) Steve On Dec 25, 2007 9:06 AM, thaGod <th...@gm...> wrote: > > Well.. the only obvious answer is I must have done it wrong! > > I did do this a little different than you and I haven't tried it since I > added the jumper wire. I was soldering jumper wire to the SCL and SDA wires > on the tsc2003 on the consoleLCD-vx board for monitoring. It's entirely > possible that I just don't understand the entire circuit. > > Erick > > > > Steve Sakoman wrote: > > > >> I see. That's good news.. although I just don't understand why I'm > >> reading > >> both lines low on my oscope with no pullups added. It would help to have > >> access to the mobo schematics ;) kidding of course. > > > > This afternoon I soldered wires to i2c clk, data, int, and ground so I > > can easily probe the signals. At boot clk, data, and int are pulled > > high. I can see clk and data wiggle when I use the i2c tool. > > > > Not sure why you see no signals! > > > > Steve > > > >> Maybe some pertinent info.. maybe not, but the busy bus messages come > >> whenever the 2nd module is loaded of the i2c-pxa/tsc2003 pair. Meaning if > >> you load tsc2003 first.. no errors, but they come when you load i2c-pxa. > >> You've probably already noticed. > >> > >> Erick > >> > >> > >> > >> Steve Sakoman wrote: > >> > > >> > Erick, > >> > > >> > It isn't necessary to add pullups to the i2c lines on the tsc2003. > >> > > >> > If you try playing around with the tsc2003 using Dave Hyland's > >> > excellent i2c command line program you will find that you can talk to > >> > the chip just fine. > >> > > >> > I was able to poke around and read the various registers and got back > >> > reasonable values. > >> > > >> > If you read the driver output messages you will see that it does > >> > succeed in its first probe of the chip. Something goes awry after > >> > that point though. I've been too swamped with other tasks to look > >> > into this, but hopefully will get to it sometime over the holidays. > >> > > >> > Steve > >> > > >> > On Dec 22, 2007 7:00 PM, thaGod <th...@gm...> wrote: > >> >> > >> >> I have gone as far as you in this new fix for the touchscreen driver. > >> You > >> >> might try adding pullup resistors as described in the previous > >> >> touchscreen > >> >> thread. > >> >> > >> >> TI TSC2003 touchscreen controller (supplied with Gumstix Samsung > >> display) > >> >> > >> >> I haven't re-probed the touchscreen controller with my o-scope since > >> I've > >> >> added this jumper, but it can't solve the pullup problem so I can only > >> >> assume that they must still be added. Don't take this for gospel, but > >> >> that > >> >> message would indicate exactly what you would expect from an i2c > >> circuit > >> >> with no pullups. There must be pullups in order to free the line for > >> >> transmission. > >> >> > >> >> I added these pullups before by soldering jumper wire to the SDL and > >> SCL > >> >> lines of the tsc2003 and then clipping resistors in line with VCC... > >> not > >> >> an > >> >> elegant solution, but it will do for testing. Good luck... maybe I'll > >> get > >> >> back around to feeling this out the rest of the way too. > >> >> > >> >> Erick > >> >> > >> >> > >> >> > >> >> Magnus Ekhall wrote: > >> >> > > >> >> > Demetris Zavorotnichenko wrote: > >> >> >> Why, what is wrong with this one ? Are you having problems ? > >> >> >> > >> >> >> > >> >> >> Demetris Z. > >> >> >> > >> >> >> > >> >> > > >> >> > Yes, at the moment I get the following errors when I insmod the > >> driver: > >> >> > " > >> >> > i2c_adapter i2c-1: i2c_pxa_set_slave: wait timedout > >> >> > tsc2003_i2c_detect: probing address 0x48 > >> >> > i2c_adapter i2c-1: i2c_pxa: timeout waiting for bus free > >> >> > " > >> >> > > >> >> > > >> >> > > >> >> > >> ------------------------------------------------------------------------- > >> >> > This SF.net email is sponsored by: Microsoft > >> >> > Defy all challenges. Microsoft(R) Visual Studio 2005. > >> >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> >> > _______________________________________________ > >> >> > gumstix-users mailing list > >> >> > gum...@li... > >> >> > https://lists.sourceforge.net/lists/listinfo/gumstix-users > >> >> > > >> >> > > >> >> > >> >> -- > >> >> View this message in context: > >> >> > >> http://www.nabble.com/Touchscreen-driver-TSC2003-i2c-timeout-tp14445072p14475397.html > >> >> Sent from the Gumstix mailing list archive at Nabble.com. > >> >> > >> >> > >> >> > >> >> > >> ------------------------------------------------------------------------- > >> >> This SF.net email is sponsored by: Microsoft > >> >> Defy all challenges. Microsoft(R) Visual Studio 2005. > >> >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> >> _______________________________________________ > >> >> gumstix-users mailing list > >> >> gum...@li... > >> >> https://lists.sourceforge.net/lists/listinfo/gumstix-users > >> >> > >> > > >> > > >> ------------------------------------------------------------------------- > >> > This SF.net email is sponsored by: Microsoft > >> > Defy all challenges. Microsoft(R) Visual Studio 2005. > >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> > _______________________________________________ > >> > gumstix-users mailing list > >> > gum...@li... > >> > https://lists.sourceforge.net/lists/listinfo/gumstix-users > >> > > >> > > >> > >> -- > >> View this message in context: > >> http://www.nabble.com/Touchscreen-driver-TSC2003-i2c-timeout-tp14445072p14481909.html > >> > >> Sent from the Gumstix mailing list archive at Nabble.com. > >> > >> > >> ------------------------------------------------------------------------- > >> This SF.net email is sponsored by: Microsoft > >> Defy all challenges. Microsoft(R) Visual Studio 2005. > >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> _______________________________________________ > >> gumstix-users mailing list > >> gum...@li... > >> https://lists.sourceforge.net/lists/listinfo/gumstix-users > >> > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2005. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > -- > View this message in context: http://www.nabble.com/Touchscreen-driver-TSC2003-i2c-timeout-tp14445072p14496247.html > > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: thaGod <th...@gm...> - 2007-12-26 00:15:54
|
I'll start with that to verify your findings... although I'm more than willing to take your word for it =) I'm excited to get back on the job as well. I've been itching for a few days now to get my eyes on the driver code again. The only reason I would even double check your findings is possible board revision differences? This isn't something I'm in a position to guess at... I'll go ahead and run the jumpers to my oscope because that's the simplest thing for me to verify right off the bat. For a few weeks now I've been tossing around the idea of just writing my own bit banging code for running this touchscreen controller. It really doesn't have to be this difficult. Granted, Bill's driver would be great to have working because the code exists and the work should be done. We'll see how it works out. I'll keep everyone posted. Merry Christmas! Erick Steve Sakoman wrote: > > Erick, > > There's easy access to the i2c data, clock, and interrupt lines -- > they all come out to plated through holes. The only dicey soldering > is to one leg of the pull up resistor for the interrupt. You don't > need to touch the tsc2003 chip itself! > > And now that I've verified that there are pullups and live i2c > signaling, the only jumper that is necessary is the one that I > previously posted a diagram for. > > I have some theories on why it might not be working. I hope to get a > chance to pursue this tomorrow when I'm back on the job :-) > > Steve > > > On Dec 25, 2007 9:06 AM, thaGod <th...@gm...> wrote: >> >> Well.. the only obvious answer is I must have done it wrong! >> >> I did do this a little different than you and I haven't tried it since I >> added the jumper wire. I was soldering jumper wire to the SCL and SDA >> wires >> on the tsc2003 on the consoleLCD-vx board for monitoring. It's entirely >> possible that I just don't understand the entire circuit. >> >> Erick >> >> >> >> Steve Sakoman wrote: >> > >> >> I see. That's good news.. although I just don't understand why I'm >> >> reading >> >> both lines low on my oscope with no pullups added. It would help to >> have >> >> access to the mobo schematics ;) kidding of course. >> > >> > This afternoon I soldered wires to i2c clk, data, int, and ground so I >> > can easily probe the signals. At boot clk, data, and int are pulled >> > high. I can see clk and data wiggle when I use the i2c tool. >> > >> > Not sure why you see no signals! >> > >> > Steve >> > >> >> Maybe some pertinent info.. maybe not, but the busy bus messages come >> >> whenever the 2nd module is loaded of the i2c-pxa/tsc2003 pair. Meaning >> if >> >> you load tsc2003 first.. no errors, but they come when you load >> i2c-pxa. >> >> You've probably already noticed. >> >> >> >> Erick >> >> >> >> >> >> >> >> Steve Sakoman wrote: >> >> > >> >> > Erick, >> >> > >> >> > It isn't necessary to add pullups to the i2c lines on the tsc2003. >> >> > >> >> > If you try playing around with the tsc2003 using Dave Hyland's >> >> > excellent i2c command line program you will find that you can talk >> to >> >> > the chip just fine. >> >> > >> >> > I was able to poke around and read the various registers and got >> back >> >> > reasonable values. >> >> > >> >> > If you read the driver output messages you will see that it does >> >> > succeed in its first probe of the chip. Something goes awry after >> >> > that point though. I've been too swamped with other tasks to look >> >> > into this, but hopefully will get to it sometime over the holidays. >> >> > >> >> > Steve >> >> > >> >> > On Dec 22, 2007 7:00 PM, thaGod <th...@gm...> wrote: >> >> >> >> >> >> I have gone as far as you in this new fix for the touchscreen >> driver. >> >> You >> >> >> might try adding pullup resistors as described in the previous >> >> >> touchscreen >> >> >> thread. >> >> >> >> >> >> TI TSC2003 touchscreen controller (supplied with Gumstix Samsung >> >> display) >> >> >> >> >> >> I haven't re-probed the touchscreen controller with my o-scope >> since >> >> I've >> >> >> added this jumper, but it can't solve the pullup problem so I can >> only >> >> >> assume that they must still be added. Don't take this for gospel, >> but >> >> >> that >> >> >> message would indicate exactly what you would expect from an i2c >> >> circuit >> >> >> with no pullups. There must be pullups in order to free the line >> for >> >> >> transmission. >> >> >> >> >> >> I added these pullups before by soldering jumper wire to the SDL >> and >> >> SCL >> >> >> lines of the tsc2003 and then clipping resistors in line with >> VCC... >> >> not >> >> >> an >> >> >> elegant solution, but it will do for testing. Good luck... maybe >> I'll >> >> get >> >> >> back around to feeling this out the rest of the way too. >> >> >> >> >> >> Erick >> >> >> >> >> >> >> >> >> >> >> >> Magnus Ekhall wrote: >> >> >> > >> >> >> > Demetris Zavorotnichenko wrote: >> >> >> >> Why, what is wrong with this one ? Are you having problems ? >> >> >> >> >> >> >> >> >> >> >> >> Demetris Z. >> >> >> >> >> >> >> >> >> >> >> > >> >> >> > Yes, at the moment I get the following errors when I insmod the >> >> driver: >> >> >> > " >> >> >> > i2c_adapter i2c-1: i2c_pxa_set_slave: wait timedout >> >> >> > tsc2003_i2c_detect: probing address 0x48 >> >> >> > i2c_adapter i2c-1: i2c_pxa: timeout waiting for bus free >> >> >> > " >> >> >> > >> >> >> > >> >> >> > >> >> >> >> >> >> ------------------------------------------------------------------------- >> >> >> > This SF.net email is sponsored by: Microsoft >> >> >> > Defy all challenges. Microsoft(R) Visual Studio 2005. >> >> >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> >> >> > _______________________________________________ >> >> >> > gumstix-users mailing list >> >> >> > gum...@li... >> >> >> > https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> >> > >> >> >> > >> >> >> >> >> >> -- >> >> >> View this message in context: >> >> >> >> >> >> http://www.nabble.com/Touchscreen-driver-TSC2003-i2c-timeout-tp14445072p14475397.html >> >> >> Sent from the Gumstix mailing list archive at Nabble.com. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> ------------------------------------------------------------------------- >> >> >> This SF.net email is sponsored by: Microsoft >> >> >> Defy all challenges. Microsoft(R) Visual Studio 2005. >> >> >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> >> >> _______________________________________________ >> >> >> gumstix-users mailing list >> >> >> gum...@li... >> >> >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> >> >> >> > >> >> > >> >> >> ------------------------------------------------------------------------- >> >> > This SF.net email is sponsored by: Microsoft >> >> > Defy all challenges. Microsoft(R) Visual Studio 2005. >> >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> >> > _______________________________________________ >> >> > gumstix-users mailing list >> >> > gum...@li... >> >> > https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > >> >> > >> >> >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/Touchscreen-driver-TSC2003-i2c-timeout-tp14445072p14481909.html >> >> >> >> Sent from the Gumstix mailing list archive at Nabble.com. >> >> >> >> >> >> >> ------------------------------------------------------------------------- >> >> This SF.net email is sponsored by: Microsoft >> >> Defy all challenges. Microsoft(R) Visual Studio 2005. >> >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> >> _______________________________________________ >> >> gumstix-users mailing list >> >> gum...@li... >> >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> >> > >> > >> ------------------------------------------------------------------------- >> > This SF.net email is sponsored by: Microsoft >> > Defy all challenges. Microsoft(R) Visual Studio 2005. >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> > _______________________________________________ >> > gumstix-users mailing list >> > gum...@li... >> > https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Touchscreen-driver-TSC2003-i2c-timeout-tp14445072p14496247.html >> >> Sent from the Gumstix mailing list archive at Nabble.com. >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2005. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://www.nabble.com/Touchscreen-driver-TSC2003-i2c-timeout-tp14445072p14498381.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Grahame J. <gb...@th...> - 2007-12-27 02:11:42
|
Hi, I have compiled and installed oe based on gumstix-x11-image.bb. When I run cat /dev/input/event0 it is spewing information, however it reacts to my finger on the screen. This is some of the spewing information: tsc2003_read: cmd=1] pd=3 m=1 tsc2003_read: val[1] = 7878 tsc2003_read: cmd=1] pd=2 m=1 tsc2003_read: val[1] = 7920 tsc2003_read: cmd=c] pd=3 m=1 tsc2003_read: val[c] = 78 tsc2003_read: cmd=d] pd=3 m=1 tsc2003_read: val[d] = f778 tsc2003_read: cmd=e] pd=3 m=1 tsc2003_read: val[e] = 78 tsc2003_read: cmd=1] pd=3 m=1 Running Xfbdev complains about no /dev/input/touchscreen0 ln -s /dev/input/event0 /dev/input/touchscreen0 Xfbdev starts but spews out information. Does react somewhat to finger on screen but nothing coherently? This looks like there is something stuck? Cheers Grahame Jordan |
From: Chris D. <chr...@gm...> - 2007-12-27 02:30:12
|
Hi Grahame, Xfbdev should work fine with /dev/input/event0. The gumstix-x11-image file was based off of a build I did for a connex + Alps lcd, so you may need to tweak the values in /etc/X11/Xserver to be more appropriate for your setup (although those changes might already be present?? I only build for my custom setup...). Also, I'm not sure that the touchscreen driver for the tsc2003 is working properly yet, which might cause you some problems starting X. Chris On Dec 26, 2007 7:11 PM, Grahame Jordan <gb...@th...> wrote: > Hi, > > I have compiled and installed oe based on gumstix-x11-image.bb. > When I run cat /dev/input/event0 it is spewing information, however it > reacts to my finger on the screen. > > This is some of the spewing information: > tsc2003_read: cmd=1] pd=3 m=1 > tsc2003_read: val[1] = 7878 > tsc2003_read: cmd=1] pd=2 m=1 > tsc2003_read: val[1] = 7920 > tsc2003_read: cmd=c] pd=3 m=1 > tsc2003_read: val[c] = 78 > tsc2003_read: cmd=d] pd=3 m=1 > tsc2003_read: val[d] = f778 > tsc2003_read: cmd=e] pd=3 m=1 > tsc2003_read: val[e] = 78 > tsc2003_read: cmd=1] pd=3 m=1 > > Running Xfbdev complains about no /dev/input/touchscreen0 > ln -s /dev/input/event0 /dev/input/touchscreen0 > Xfbdev starts but spews out information. Does react somewhat to finger > on screen but nothing coherently? > > This looks like there is something stuck? > > Cheers > > Grahame Jordan > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Steve S. <sa...@gm...> - 2007-12-27 03:16:03
|
Grahame, That image is *highly* experimental :-) Also, as Chris says, the touchscreen driver is still not functional. Stay tuned, I'll be working on it over the coming weeks. If you manage to make any progress, please submit patches! Steve On Dec 26, 2007 6:11 PM, Grahame Jordan <gb...@th...> wrote: > Hi, > > I have compiled and installed oe based on gumstix-x11-image.bb. > When I run cat /dev/input/event0 it is spewing information, however it > reacts to my finger on the screen. > > This is some of the spewing information: > tsc2003_read: cmd=1] pd=3 m=1 > tsc2003_read: val[1] = 7878 > tsc2003_read: cmd=1] pd=2 m=1 > tsc2003_read: val[1] = 7920 > tsc2003_read: cmd=c] pd=3 m=1 > tsc2003_read: val[c] = 78 > tsc2003_read: cmd=d] pd=3 m=1 > tsc2003_read: val[d] = f778 > tsc2003_read: cmd=e] pd=3 m=1 > tsc2003_read: val[e] = 78 > tsc2003_read: cmd=1] pd=3 m=1 > > Running Xfbdev complains about no /dev/input/touchscreen0 > ln -s /dev/input/event0 /dev/input/touchscreen0 > Xfbdev starts but spews out information. Does react somewhat to finger > on screen but nothing coherently? > > This looks like there is something stuck? > > Cheers > > Grahame Jordan > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Tom K. <tk...@so...> - 2008-01-12 03:04:11
|
This may be a bit late, but I guess if I am reading this thread correctly, the proper steps for installing and getting the Samsung to work is: 0.) Connect all hardware properly :) 1.) Solder in the jumper as shown in http://www.sakoman.net/oe/B10003.rew.png 2.) Get the latest gumstix-oe source as described at http://www.gumstix.net/Software/view/Getting-started/Setting-up-a-build-environment/32.html 3.) Using the other fine documentation there at gumstix.net, build the target with "bitbake gumstix-x11-image" Is that correct, or am I missing something? Thanks to all for their work on this. Tom Steve Sakoman wrote: > Grahame, > > I checked in changes to the tsc2003 driver that should speed up the > startup process. The old version of the driver was probing for the > tsc2003 on 4 different addresses -- that is what was taking so long > and printing out all of those messages & timeout warnings. Now it > just looks at the address where the tsc2003 happens to be on gumstix > hw :-) > > I also checked in some udev changes that should automatically create > /dev/input/touchscreen0 when the tsc2003 driver is loaded at boot > time. > > With those changes, the gumstix-x11-image should launch right into the > touchscreen calibration program right at boot. After the calibration > process, it proceeds to launch matchbox and you should get some icons > on the screen and be able to play with them with your stylus. Not a > lot to keep you entertained though! Colors are still screwed up, but > every day a little progress . . . > > You also can play with the ts_test program -- it lets you draw on the screen. > > Thanks for helping to test this! > > Steve > > On Dec 27, 2007 12:14 PM, Grahame Jordan <gb...@th...> wrote: > >> Latest oe. >> Yes It loads tsc2003 during boot. >> tsdev loads but is not required (Obsolite) >> >> I tried running /etc/X11/Xserver but it gets confused about the mouse >> device among other things. >> >> Somehow the device changed from /dev/input/touchscreen0 to >> /dev/input/ts0 after I updated kernel & modules but by changing the link >> to event0, that was fixed >> >> Grahame >> >> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > |
From: Steve S. <sa...@gm...> - 2008-01-12 04:15:43
|
Tom, You are correct. The x11 image doesn't support the 18bpp frame buffer all that well yet, but these steps will give you something interesting to play with. Steve On Jan 11, 2008 7:03 PM, Tom Kunz <tk...@so...> wrote: > This may be a bit late, but I guess if I am reading this thread > correctly, the proper steps for installing and getting the Samsung to > work is: > > 0.) Connect all hardware properly :) > 1.) Solder in the jumper as shown in > http://www.sakoman.net/oe/B10003.rew.png > 2.) Get the latest gumstix-oe source as described at > http://www.gumstix.net/Software/view/Getting-started/Setting-up-a-build-environment/32.html > 3.) Using the other fine documentation there at gumstix.net, build the > target with "bitbake gumstix-x11-image" > > Is that correct, or am I missing something? > > Thanks to all for their work on this. > > Tom > > > > Steve Sakoman wrote: > > Grahame, > > > > I checked in changes to the tsc2003 driver that should speed up the > > startup process. The old version of the driver was probing for the > > tsc2003 on 4 different addresses -- that is what was taking so long > > and printing out all of those messages & timeout warnings. Now it > > just looks at the address where the tsc2003 happens to be on gumstix > > hw :-) > > > > I also checked in some udev changes that should automatically create > > /dev/input/touchscreen0 when the tsc2003 driver is loaded at boot > > time. > > > > With those changes, the gumstix-x11-image should launch right into the > > touchscreen calibration program right at boot. After the calibration > > process, it proceeds to launch matchbox and you should get some icons > > on the screen and be able to play with them with your stylus. Not a > > lot to keep you entertained though! Colors are still screwed up, but > > every day a little progress . . . > > > > You also can play with the ts_test program -- it lets you draw on the screen. > > > > Thanks for helping to test this! > > > > Steve > > > > On Dec 27, 2007 12:14 PM, Grahame Jordan <gb...@th...> wrote: > > > >> Latest oe. > >> Yes It loads tsc2003 during boot. > >> tsdev loads but is not required (Obsolite) > >> > >> I tried running /etc/X11/Xserver but it gets confused about the mouse > >> device among other things. > >> > >> Somehow the device changed from /dev/input/touchscreen0 to > >> /dev/input/ts0 after I updated kernel & modules but by changing the link > >> to event0, that was fixed > >> > >> Grahame > >> > >> > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2005. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Bill G. <bg...@bi...> - 2007-12-28 13:52:10
|
Steve Sakoman wrote: > >> I think there was some progress on this posted on l-a-k about six months >> ago. >> > > Maybe I haven't had enough coffee this morning, but l-a-k isn't > ringing a bell for me! What do those three letters stand for? > Linux-ARM-Kernel. http://arm.linux.org.uk b.g. -- Bill Gatliff bg...@bi... |
From: Steve S. <sa...@gm...> - 2007-12-28 14:03:37
|
My turn to say doh! and grab another cup of coffee :-) Steve On Dec 28, 2007 5:52 AM, Bill Gatliff <bg...@bi...> wrote: > Steve Sakoman wrote: > > > >> I think there was some progress on this posted on l-a-k about six months > >> ago. > >> > > > > Maybe I haven't had enough coffee this morning, but l-a-k isn't > > ringing a bell for me! What do those three letters stand for? > > > > Linux-ARM-Kernel. http://arm.linux.org.uk > > > > b.g. > > -- > Bill Gatliff > bg...@bi... > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Steve S. <sa...@gm...> - 2007-12-24 15:48:52
|
Eric, I spent a little more time looking at the tsc2003. As far as I can tell the hardware seems to be working fine. With scope probes on i2c clock and data I can see the driver issue the initial command to probe the tsc2003. With a scope probe on the interrupt line I can see the line pulled low when I touch the screen and return high when I remove my finger. I put a print at the start of tsc2003_penirq and after the tsc2003 driver is modprobed I get a message printed to the console each time I touch the screen. So it appears that the driver sets up the interrupt properly. For some reason though, the driver does something that wedges the i2c driver or hardware after that initial probe. That is when you are seeing the error messages from the i2c driver. The i2c command line program also fails after that point when it attempts to do an ioctl( i2cDev, I2C_SLAVE, gI2cAddr ). It reports an error of: ERROR: I2cSetSlaveAddress: Error trying to set slave address to 0x48 (16 Device or resource busy) Looking at clock & data lines at this point show both to be high, so the problem is *not* something holding clock low or a lack of pullups. That's the status at this point. I was tired & went to sleep :-) It being Christmas Eve, I'm not sure that I will find to get back to this today or tomorrow, but I thought I would get this much info out there in case someone else wants to go further with the debugging. Suggestions for areas to look next are always welcome, especially from those who have experience writing i2c drivers. Steve On Dec 23, 2007 1:17 PM, thaGod <th...@gm...> wrote: > > I see. That's good news.. although I just don't understand why I'm reading > both lines low on my oscope with no pullups added. It would help to have > access to the mobo schematics ;) kidding of course. > > Maybe some pertinent info.. maybe not, but the busy bus messages come > whenever the 2nd module is loaded of the i2c-pxa/tsc2003 pair. Meaning if > you load tsc2003 first.. no errors, but they come when you load i2c-pxa. > You've probably already noticed. > > Erick > > > > Steve Sakoman wrote: > > > > Erick, > > > > It isn't necessary to add pullups to the i2c lines on the tsc2003. > > > > If you try playing around with the tsc2003 using Dave Hyland's > > excellent i2c command line program you will find that you can talk to > > the chip just fine. > > > > I was able to poke around and read the various registers and got back > > reasonable values. > > > > If you read the driver output messages you will see that it does > > succeed in its first probe of the chip. Something goes awry after > > that point though. I've been too swamped with other tasks to look > > into this, but hopefully will get to it sometime over the holidays. > > > > Steve > > > > On Dec 22, 2007 7:00 PM, thaGod <th...@gm...> wrote: > >> > >> I have gone as far as you in this new fix for the touchscreen driver. You > >> might try adding pullup resistors as described in the previous > >> touchscreen > >> thread. > >> > >> TI TSC2003 touchscreen controller (supplied with Gumstix Samsung display) > >> > >> I haven't re-probed the touchscreen controller with my o-scope since I've > >> added this jumper, but it can't solve the pullup problem so I can only > >> assume that they must still be added. Don't take this for gospel, but > >> that > >> message would indicate exactly what you would expect from an i2c circuit > >> with no pullups. There must be pullups in order to free the line for > >> transmission. > >> > >> I added these pullups before by soldering jumper wire to the SDL and SCL > >> lines of the tsc2003 and then clipping resistors in line with VCC... not > >> an > >> elegant solution, but it will do for testing. Good luck... maybe I'll get > >> back around to feeling this out the rest of the way too. > >> > >> Erick > >> > >> > >> > >> Magnus Ekhall wrote: > >> > > >> > Demetris Zavorotnichenko wrote: > >> >> Why, what is wrong with this one ? Are you having problems ? > >> >> > >> >> > >> >> Demetris Z. > >> >> > >> >> > >> > > >> > Yes, at the moment I get the following errors when I insmod the driver: > >> > " > >> > i2c_adapter i2c-1: i2c_pxa_set_slave: wait timedout > >> > tsc2003_i2c_detect: probing address 0x48 > >> > i2c_adapter i2c-1: i2c_pxa: timeout waiting for bus free > >> > " > >> > > >> > > >> > > >> ------------------------------------------------------------------------- > >> > This SF.net email is sponsored by: Microsoft > >> > Defy all challenges. Microsoft(R) Visual Studio 2005. > >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> > _______________________________________________ > >> > gumstix-users mailing list > >> > gum...@li... > >> > https://lists.sourceforge.net/lists/listinfo/gumstix-users > >> > > >> > > >> > >> -- > >> View this message in context: > >> http://www.nabble.com/Touchscreen-driver-TSC2003-i2c-timeout-tp14445072p14475397.html > >> Sent from the Gumstix mailing list archive at Nabble.com. > >> > >> > >> > >> ------------------------------------------------------------------------- > >> This SF.net email is sponsored by: Microsoft > >> Defy all challenges. Microsoft(R) Visual Studio 2005. > >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> _______________________________________________ > >> gumstix-users mailing list > >> gum...@li... > >> https://lists.sourceforge.net/lists/listinfo/gumstix-users > >> > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2005. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > -- > View this message in context: http://www.nabble.com/Touchscreen-driver-TSC2003-i2c-timeout-tp14445072p14481909.html > > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Dave H. <dhy...@gm...> - 2007-12-24 17:15:56
|
Hi Steve, > For some reason though, the driver does something that wedges the i2c > driver or hardware after that initial probe. That is when you are > seeing the error messages from the i2c driver. The i2c command line > program also fails after that point when it attempts to do an ioctl( > i2cDev, I2C_SLAVE, gI2cAddr ). It reports an error of: > > ERROR: I2cSetSlaveAddress: Error trying to set slave address to 0x48 > (16 Device or resource busy) I think this happens when the touch screen registers a proper i2c driver. There are two modes of using the i2c stuff. The first, which is used by the i2c program, is to use the i2cdev interface. This is really a bus level interface. The second method, is that a particular driver registers itself as an i2c device. In this case it normally creates a /dev entry that then takes care of doing all of the i2c transactions, in effect, claiming that particular device as its own. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Steve S. <sa...@gm...> - 2007-12-24 17:38:34
|
Dave, Thanks for clarifying that! I had a suspicion that might be the case. Explains why the i2c command line tool doesn't work after the tsc2003 driver loads. Doesn't yet explain the bizarre i2c driver error messages :-) Steve On Dec 24, 2007 9:15 AM, Dave Hylands <dhy...@gm...> wrote: > Hi Steve, > > > For some reason though, the driver does something that wedges the i2c > > driver or hardware after that initial probe. That is when you are > > seeing the error messages from the i2c driver. The i2c command line > > program also fails after that point when it attempts to do an ioctl( > > i2cDev, I2C_SLAVE, gI2cAddr ). It reports an error of: > > > > ERROR: I2cSetSlaveAddress: Error trying to set slave address to 0x48 > > (16 Device or resource busy) > > I think this happens when the touch screen registers a proper i2c > driver. There are two modes of using the i2c stuff. > > The first, which is used by the i2c program, is to use the i2cdev > interface. This is really a bus level interface. > > The second method, is that a particular driver registers itself as an > i2c device. In this case it normally creates a /dev entry that then > takes care of doing all of the i2c transactions, in effect, claiming > that particular device as its own. > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Steve S. <sa...@gm...> - 2007-12-27 03:39:25
|
> may need to tweak the values in /etc/X11/Xserver to be more > appropriate for your setup (although those changes might already be > present?? Yes, I tweaked /etc/X11/Xserver to incorporate a couple of changes needed to work with gumstix. I found that if you kill the touchscreen calibration tool that launches at boot you will get a desktop with a few icons. In the most recent build you can connect a usb mouse, move the cursor around the screen , and even launch a couple of the applets. For some reason the mouse only works after you press the escape key on the keyboard. As I said, this is all still highly experimental :-) I'm surprised anyone noticed it was there! It's also a bit hefty in size. Surprisingly the glibc version is smaller than the uclibc version. Steve On Dec 26, 2007 6:30 PM, Chris Dollar <chr...@gm...> wrote: > Hi Grahame, > > Xfbdev should work fine with /dev/input/event0. The gumstix-x11-image > file was based off of a build I did for a connex + Alps lcd, so you > may need to tweak the values in /etc/X11/Xserver to be more > appropriate for your setup (although those changes might already be > present?? I only build for my custom setup...). Also, I'm not sure > that the touchscreen driver for the tsc2003 is working properly yet, > which might cause you some problems starting X. > > Chris > > > On Dec 26, 2007 7:11 PM, Grahame Jordan <gb...@th...> wrote: > > Hi, > > > > I have compiled and installed oe based on gumstix-x11-image.bb. > > When I run cat /dev/input/event0 it is spewing information, however it > > reacts to my finger on the screen. > > > > This is some of the spewing information: > > tsc2003_read: cmd=1] pd=3 m=1 > > tsc2003_read: val[1] = 7878 > > tsc2003_read: cmd=1] pd=2 m=1 > > tsc2003_read: val[1] = 7920 > > tsc2003_read: cmd=c] pd=3 m=1 > > tsc2003_read: val[c] = 78 > > tsc2003_read: cmd=d] pd=3 m=1 > > tsc2003_read: val[d] = f778 > > tsc2003_read: cmd=e] pd=3 m=1 > > tsc2003_read: val[e] = 78 > > tsc2003_read: cmd=1] pd=3 m=1 > > > > Running Xfbdev complains about no /dev/input/touchscreen0 > > ln -s /dev/input/event0 /dev/input/touchscreen0 > > Xfbdev starts but spews out information. Does react somewhat to finger > > on screen but nothing coherently? > > > > This looks like there is something stuck? > > > > Cheers > > > > Grahame Jordan > > > > > > > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2005. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Grahame J. <gb...@th...> - 2007-12-27 11:02:48
|
Good News First of all: Add wiring mod bitbake gumstix-x11-image Install image and boot modprobe tsc2003 After a while it will talk on i2c. This may be a speed issue? export DISPLAY=:0 ln -s /dev/input/event0 /dev/input/touchscreeen0 Xfbdev & xtscal Calibrate screen "Thanks to my son on this one :)" x-window-manager & Touch screen is working! Needs tweaking but a good start Cheers Grahame Jordan Steve Sakoman wrote: >> may need to tweak the values in /etc/X11/Xserver to be more >> appropriate for your setup (although those changes might already be >> present?? >> > > Yes, I tweaked /etc/X11/Xserver to incorporate a couple of changes > needed to work with gumstix. > > I found that if you kill the touchscreen calibration tool that > launches at boot you will get a desktop with a few icons. In the most > recent build you can connect a usb mouse, move the cursor around the > screen , and even launch a couple of the applets. For some reason the > mouse only works after you press the escape key on the keyboard. > > As I said, this is all still highly experimental :-) I'm surprised > anyone noticed it was there! It's also a bit hefty in size. > Surprisingly the glibc version is smaller than the uclibc version. > > Steve > > > On Dec 26, 2007 6:30 PM, Chris Dollar <chr...@gm...> wrote: > >> Hi Grahame, >> >> Xfbdev should work fine with /dev/input/event0. The gumstix-x11-image >> file was based off of a build I did for a connex + Alps lcd, so you >> may need to tweak the values in /etc/X11/Xserver to be more >> appropriate for your setup (although those changes might already be >> present?? I only build for my custom setup...). Also, I'm not sure >> that the touchscreen driver for the tsc2003 is working properly yet, >> which might cause you some problems starting X. >> >> Chris >> >> >> On Dec 26, 2007 7:11 PM, Grahame Jordan <gb...@th...> wrote: >> >>> Hi, >>> >>> I have compiled and installed oe based on gumstix-x11-image.bb. >>> When I run cat /dev/input/event0 it is spewing information, however it >>> reacts to my finger on the screen. >>> >>> This is some of the spewing information: >>> tsc2003_read: cmd=1] pd=3 m=1 >>> tsc2003_read: val[1] = 7878 >>> tsc2003_read: cmd=1] pd=2 m=1 >>> tsc2003_read: val[1] = 7920 >>> tsc2003_read: cmd=c] pd=3 m=1 >>> tsc2003_read: val[c] = 78 >>> tsc2003_read: cmd=d] pd=3 m=1 >>> tsc2003_read: val[d] = f778 >>> tsc2003_read: cmd=e] pd=3 m=1 >>> tsc2003_read: val[e] = 78 >>> tsc2003_read: cmd=1] pd=3 m=1 >>> >>> Running Xfbdev complains about no /dev/input/touchscreen0 >>> ln -s /dev/input/event0 /dev/input/touchscreen0 >>> Xfbdev starts but spews out information. Does react somewhat to finger >>> on screen but nothing coherently? >>> >>> This looks like there is something stuck? >>> >>> Cheers >>> >>> Grahame Jordan >>> >>> >>> >>> >>> >>> ------------------------------------------------------------------------- >>> This SF.net email is sponsored by: Microsoft >>> Defy all challenges. Microsoft(R) Visual Studio 2005. >>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >>> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2005. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > |
From: Steve S. <sa...@gm...> - 2007-12-27 17:58:30
|
Grahame, Which svn revision are you working with? The latests revs shouldn't need the modprobe tsc2003. Steve On Dec 27, 2007 3:02 AM, Grahame Jordan <gb...@th...> wrote: > Good News > > First of all: > Add wiring mod > > bitbake gumstix-x11-image > Install image and boot > > modprobe tsc2003 > After a while it will talk on i2c. This may be a speed issue? > > export DISPLAY=:0 > ln -s /dev/input/event0 /dev/input/touchscreeen0 > > Xfbdev & xtscal > Calibrate screen "Thanks to my son on this one :)" > x-window-manager & > > Touch screen is working! > > Needs tweaking but a good start > > > Cheers > > Grahame Jordan > > > > > Steve Sakoman wrote: > >> may need to tweak the values in /etc/X11/Xserver to be more > >> appropriate for your setup (although those changes might already be > >> present?? > >> > > > > Yes, I tweaked /etc/X11/Xserver to incorporate a couple of changes > > needed to work with gumstix. > > > > I found that if you kill the touchscreen calibration tool that > > launches at boot you will get a desktop with a few icons. In the most > > recent build you can connect a usb mouse, move the cursor around the > > screen , and even launch a couple of the applets. For some reason the > > mouse only works after you press the escape key on the keyboard. > > > > As I said, this is all still highly experimental :-) I'm surprised > > anyone noticed it was there! It's also a bit hefty in size. > > Surprisingly the glibc version is smaller than the uclibc version. > > > > Steve > > > > > > On Dec 26, 2007 6:30 PM, Chris Dollar <chr...@gm...> wrote: > > > >> Hi Grahame, > >> > >> Xfbdev should work fine with /dev/input/event0. The gumstix-x11-image > >> file was based off of a build I did for a connex + Alps lcd, so you > >> may need to tweak the values in /etc/X11/Xserver to be more > >> appropriate for your setup (although those changes might already be > >> present?? I only build for my custom setup...). Also, I'm not sure > >> that the touchscreen driver for the tsc2003 is working properly yet, > >> which might cause you some problems starting X. > >> > >> Chris > >> > >> > >> On Dec 26, 2007 7:11 PM, Grahame Jordan <gb...@th...> wrote: > >> > >>> Hi, > >>> > >>> I have compiled and installed oe based on gumstix-x11-image.bb. > >>> When I run cat /dev/input/event0 it is spewing information, however it > >>> reacts to my finger on the screen. > >>> > >>> This is some of the spewing information: > >>> tsc2003_read: cmd=1] pd=3 m=1 > >>> tsc2003_read: val[1] = 7878 > >>> tsc2003_read: cmd=1] pd=2 m=1 > >>> tsc2003_read: val[1] = 7920 > >>> tsc2003_read: cmd=c] pd=3 m=1 > >>> tsc2003_read: val[c] = 78 > >>> tsc2003_read: cmd=d] pd=3 m=1 > >>> tsc2003_read: val[d] = f778 > >>> tsc2003_read: cmd=e] pd=3 m=1 > >>> tsc2003_read: val[e] = 78 > >>> tsc2003_read: cmd=1] pd=3 m=1 > >>> > >>> Running Xfbdev complains about no /dev/input/touchscreen0 > >>> ln -s /dev/input/event0 /dev/input/touchscreen0 > >>> Xfbdev starts but spews out information. Does react somewhat to finger > >>> on screen but nothing coherently? > >>> > >>> This looks like there is something stuck? > >>> > >>> Cheers > >>> > >>> Grahame Jordan > >>> > >>> > >>> > >>> > >>> > >>> ------------------------------------------------------------------------- > >>> This SF.net email is sponsored by: Microsoft > >>> Defy all challenges. Microsoft(R) Visual Studio 2005. > >>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >>> _______________________________________________ > >>> gumstix-users mailing list > >>> gum...@li... > >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users > >>> > >>> > >> ------------------------------------------------------------------------- > >> This SF.net email is sponsored by: Microsoft > >> Defy all challenges. Microsoft(R) Visual Studio 2005. > >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> _______________________________________________ > >> gumstix-users mailing list > >> gum...@li... > >> https://lists.sourceforge.net/lists/listinfo/gumstix-users > >> > >> > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2005. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Grahame J. <gb...@th...> - 2007-12-27 20:14:47
|
Latest oe. Yes It loads tsc2003 during boot. tsdev loads but is not required (Obsolite) I tried running /etc/X11/Xserver but it gets confused about the mouse device among other things. Somehow the device changed from /dev/input/touchscreen0 to /dev/input/ts0 after I updated kernel & modules but by changing the link to event0, that was fixed Grahame Steve Sakoman wrote: > Grahame, > > Which svn revision are you working with? The latests revs shouldn't > need the modprobe tsc2003. > > Steve > > On Dec 27, 2007 3:02 AM, Grahame Jordan <gb...@th...> wrote: > >> Good News >> >> First of all: >> Add wiring mod >> >> bitbake gumstix-x11-image >> Install image and boot >> >> modprobe tsc2003 >> After a while it will talk on i2c. This may be a speed issue? >> >> export DISPLAY=:0 >> ln -s /dev/input/event0 /dev/input/touchscreeen0 >> >> Xfbdev & xtscal >> Calibrate screen "Thanks to my son on this one :)" >> x-window-manager & >> >> Touch screen is working! >> >> Needs tweaking but a good start >> >> >> Cheers >> >> Grahame Jordan >> >> >> >> >> Steve Sakoman wrote: >> >>>> may need to tweak the values in /etc/X11/Xserver to be more >>>> appropriate for your setup (although those changes might already be >>>> present?? >>>> >>>> >>> Yes, I tweaked /etc/X11/Xserver to incorporate a couple of changes >>> needed to work with gumstix. >>> >>> I found that if you kill the touchscreen calibration tool that >>> launches at boot you will get a desktop with a few icons. In the most >>> recent build you can connect a usb mouse, move the cursor around the >>> screen , and even launch a couple of the applets. For some reason the >>> mouse only works after you press the escape key on the keyboard. >>> >>> As I said, this is all still highly experimental :-) I'm surprised >>> anyone noticed it was there! It's also a bit hefty in size. >>> Surprisingly the glibc version is smaller than the uclibc version. >>> >>> Steve >>> >>> >>> On Dec 26, 2007 6:30 PM, Chris Dollar <chr...@gm...> wrote: >>> >>> >>>> Hi Grahame, >>>> >>>> Xfbdev should work fine with /dev/input/event0. The gumstix-x11-image >>>> file was based off of a build I did for a connex + Alps lcd, so you >>>> may need to tweak the values in /etc/X11/Xserver to be more >>>> appropriate for your setup (although those changes might already be >>>> present?? I only build for my custom setup...). Also, I'm not sure >>>> that the touchscreen driver for the tsc2003 is working properly yet, >>>> which might cause you some problems starting X. >>>> >>>> Chris >>>> >>>> >>>> On Dec 26, 2007 7:11 PM, Grahame Jordan <gb...@th...> wrote: >>>> >>>> >>>>> Hi, >>>>> >>>>> I have compiled and installed oe based on gumstix-x11-image.bb. >>>>> When I run cat /dev/input/event0 it is spewing information, however it >>>>> reacts to my finger on the screen. >>>>> >>>>> This is some of the spewing information: >>>>> tsc2003_read: cmd=1] pd=3 m=1 >>>>> tsc2003_read: val[1] = 7878 >>>>> tsc2003_read: cmd=1] pd=2 m=1 >>>>> tsc2003_read: val[1] = 7920 >>>>> tsc2003_read: cmd=c] pd=3 m=1 >>>>> tsc2003_read: val[c] = 78 >>>>> tsc2003_read: cmd=d] pd=3 m=1 >>>>> tsc2003_read: val[d] = f778 >>>>> tsc2003_read: cmd=e] pd=3 m=1 >>>>> tsc2003_read: val[e] = 78 >>>>> tsc2003_read: cmd=1] pd=3 m=1 >>>>> >>>>> Running Xfbdev complains about no /dev/input/touchscreen0 >>>>> ln -s /dev/input/event0 /dev/input/touchscreen0 >>>>> Xfbdev starts but spews out information. Does react somewhat to finger >>>>> on screen but nothing coherently? >>>>> >>>>> This looks like there is something stuck? >>>>> >>>>> Cheers >>>>> >>>>> Grahame Jordan >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------- >>>>> This SF.net email is sponsored by: Microsoft >>>>> Defy all challenges. Microsoft(R) Visual Studio 2005. >>>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>>>> _______________________________________________ >>>>> gumstix-users mailing list >>>>> gum...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>> >>>>> >>>>> >>>> ------------------------------------------------------------------------- >>>> This SF.net email is sponsored by: Microsoft >>>> Defy all challenges. Microsoft(R) Visual Studio 2005. >>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>>> _______________________________________________ >>>> gumstix-users mailing list >>>> gum...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>> >>>> >>>> >>> ------------------------------------------------------------------------- >>> This SF.net email is sponsored by: Microsoft >>> Defy all challenges. Microsoft(R) Visual Studio 2005. >>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >>> >>> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2005. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > |
From: Thomas K. B. <tkb...@ba...> - 2008-01-16 13:32:05
|
Sorry if this email has posted a couple times. I've sent it a couple times, and it isn't showing up in my email. Anyway, now that everything seems to be shifting to the OE environment, a question that is on my mind, and will probably be creeping up soon is how to add packages. Someone had previously mentioned something about ipkg, which apparently you need to have a net connection on your gumstix, which I don't have. I've been looking over the OE folders and files to try to piece this all together so that I can select an application in the org.openembedded.snapshot packages directory. So I've been looking at the gumstix-x11-image.bb file, which I used to generate the jffs2 image, etc. I've noticed there are lines in the gumstix-x11-image.bb file such as "matchbox-common \" There is also a folder in the org.openembedded.snapshot\packages called matchbox-common. However, in this folder there are several .bb files, such as "matchbox_0.8.1.bb" and "matchbox_0.9.1.bb" So what is going on here? How do I know what is being compiled, and what isn't? If I want to add a package like qt, do I just add "qt \" to my gumstix-x11-image.bb, and then bitbake magically knows where to go from there? Obviously not because I've tried this and it hasn't worked. Anyone care to break this down for the rest of us please? Thanks for your time. I'm sure this knowledge will go a long way to help us struggling noobs. Sincerely, Thomas K. Bailey Paralegal =20 K. Ronald Bailey & Associates Co. L.P.A. 220 West Market Street P.O. Box 830 Sandusky, Ohio 44871-0830 Phone: 419-625-6740 Fax: 419-625-2021 www.baileyandassoc.com |
From: Philip B. <ph...@ba...> - 2008-01-16 14:50:56
Attachments:
smime.p7s
|
Thomas K. Bailey wrote: > Anyway, now that everything seems to be shifting to the OE environment, > a question that is on my mind, and will probably be creeping up soon is > how to add packages. Someone had previously mentioned something about > ipkg, which apparently you need to have a net connection on your > gumstix, which I don't have. I've been looking over the OE folders and > files to try to piece this all together so that I can select an > application in the org.openembedded.snapshot packages directory. You can also copy the ipkgs to the gumstix and install with ipkg filename. > So I've been looking at the gumstix-x11-image.bb file, which I used to > generate the jffs2 image, etc. > > I've noticed there are lines in the gumstix-x11-image.bb file such as > "matchbox-common \" There is also a folder in the > org.openembedded.snapshot\packages called matchbox-common. However, in > this folder there are several .bb files, such as "matchbox_0.8.1.bb" and > "matchbox_0.9.1.bb" > > So what is going on here? How do I know what is being compiled, and > what isn't? If I want to add a package like qt, do I just add "qt \" to > my gumstix-x11-image.bb, and then bitbake magically knows where to go > from there? Obviously not because I've tried this and it hasn't worked. > Anyone care to break this down for the rest of us please? Basically, OE will build the latest revision. This behavior may be modified by setting DEFAULT_PREFERENCE in the bb file (usually done to stop the latest version from being built) or by setting the version in sane-source-versions in the distro/include directory (the file name may vary depending on the distro) Hopefully this helps a little. Philip |
From: Thomas K. B. <tkb...@ba...> - 2008-01-16 14:56:09
|
It helps a little :) Are we not able to simply go to the package folder and compile the package directly by executing "bitbake matchbox_0.8.1.bb" ? I guess if I can install the ipkg without a net card, I'm okay with that as well. Actually, this would be better because I wouldn't have to put a whole filesystem on my gumstix every time I want to try out a different piece of software...it takes about 2 hours for me to load the jffs2 file and other crap. Sincerely, Thomas K. Bailey Paralegal =20 K. Ronald Bailey & Associates Co. L.P.A. 220 West Market Street P.O. Box 830 Sandusky, Ohio 44871-0830 Phone: 419-625-6740 Fax: 419-625-2021 www.baileyandassoc.com -----Original Message----- From: gum...@li... [mailto:gum...@li...] On Behalf Of Philip Balister Sent: Wednesday, January 16, 2008 9:51 AM To: General mailing list for gumstix users. Subject: Re: [Gumstix-users] Touchscreen working? Thomas K. Bailey wrote: > Anyway, now that everything seems to be shifting to the OE=20 > environment, a question that is on my mind, and will probably be=20 > creeping up soon is how to add packages. Someone had previously=20 > mentioned something about ipkg, which apparently you need to have a=20 > net connection on your gumstix, which I don't have. I've been looking > over the OE folders and files to try to piece this all together so=20 > that I can select an application in the org.openembedded.snapshot packages directory. You can also copy the ipkgs to the gumstix and install with ipkg filename. > So I've been looking at the gumstix-x11-image.bb file, which I used to > generate the jffs2 image, etc. >=20 > I've noticed there are lines in the gumstix-x11-image.bb file such as=20 > "matchbox-common \" There is also a folder in the=20 > org.openembedded.snapshot\packages called matchbox-common. However,=20 > in this folder there are several .bb files, such as=20 > "matchbox_0.8.1.bb" and "matchbox_0.9.1.bb" > > So what is going on here? How do I know what is being compiled, and=20 > what isn't? If I want to add a package like qt, do I just add "qt \"=20 > to my gumstix-x11-image.bb, and then bitbake magically knows where to=20 > go from there? Obviously not because I've tried this and it hasn't worked. > Anyone care to break this down for the rest of us please? Basically, OE will build the latest revision. This behavior may be modified by setting DEFAULT_PREFERENCE in the bb file (usually done to stop the latest version from being built) or by setting the version in sane-source-versions in the distro/include directory (the file name may vary depending on the distro) Hopefully this helps a little. Philip |