I've tried booting both verdexes repeatedly and find that /dev/input/event0 is created some of the time for both of them.  Now I'm wondering whether there could be a problem with the touch screen or console board that I'm using. 

It looks like there *is* a pattern with the kernel messages:
* The snippet that I showed earlier will always be the output that I see if the device node is not created. 
* If the device node is created, the first 'probing address 0x48' will succeed and be followed by "tsc2003_driver_register: irq 48" and "input: tsc2003 as /class/input/input0".  The second attempt to probe the device may or may not show the "i2c_pxa: timeout waiting for bus free" messages.

I'm going to solder on a jumper to another console board and see if I get the same results with another touch screen and console board. 

In the meantime, any insights are much appreciated.



On Jan 30, 2008 2:25 PM, Mike M <mike0599@gmail.com> wrote:
Very strange...the verdex that did not have the device node created sometimes has it. 

Yes, I verified that the module was loaded using lsmod.  Both verdexes are booted using the same console, netwifi-microsd and touch screen components.  The console board does have the jumper added.

The motherboard that has the device node created is running an image that requires ar-gumstix-minimal and basically adds python to it.  The motherboard that doesn't work is running ar-gumstix-minimal. 

The software revisions should be the same because I never did an svn update after doing the initial checkout of gumstix-oe.  Here is the output of svn info:

URL: https://gumstix.svn.sourceforge.net/svnroot/gumstix/trunk/com.gumstix.collection
Repository Root: https://gumstix.svn.sourceforge.net/svnroot/gumstix
Repository UUID: b85c6266-aee1-4070-9685-74336958316a
Revision: 151
Node Kind: directory
Schedule: normal
Last Changed Author: sakoman
Last Changed Rev: 151
Last Changed Date: 2008-01-18 09:29:29 -0800 (Fri, 18 Jan 2008)

One other piece of information: I sometimes see this in the kernel message output on the verdex that works sporadically:

i2c: error: timeout
i2c: msg_num: 1 msg_idx: 0 msg_ptr: 0
i2c: ICR: 000007e9 ISR: 00000004
i2c: log:
tsc2003_i2c_detect: probing address 0x48
i2c_adapter i2c-0: i2c_pxa: timeout waiting for bus free
i2c_adapter i2c-0: i2c_pxa: timeout waiting for bus free
i2c_adapter i2c-0: i2c_pxa: timeout waiting for bus free
i2c_adapter i2c-0: i2c_pxa: timeout waiting for bus free
i2c_adapter i2c-0: i2c_pxa: timeout waiting for bus free
i2c_adapter i2c-0: i2c_pxa: timeout waiting for bus free
i2c: error: exhausted retries
i2c: msg_num: 1 msg_idx: 0 msg_ptr: 0
i2c: ICR: 000007e9 ISR: 00000004
i2c: log:
I2C: i2c-0: PXA I2C adapter
tsc2003 i2c touch screen controller
Bill Gatliff <bgat at billgatliff.com
Nicholas Chen <nchen at cs.umd.edu>
tsc2003_i2c_detect: probing address 0x48
i2c: error: timeout
i2c: msg_num: 1 msg_idx: 0 msg_ptr: 1
i2c: ICR: 000017ee ISR: 00000005
i2c: log: [00000045:000017e8] [00000085:000017ee]
I2C: i2c-1: PXA I2C adapter
i2c /dev entries driver

The "i2c_pxa: timeout waiting for bus free" and subsequent "error: exhausted retries" messages don't always show up at boot and there seems to be no correlation between the presence of those messages and whether the device node will be created.  I'm going to try rebooting the verdex that works a few more times to see if anything looks different.



On Jan 30, 2008 1:37 PM, Steve Sakoman <sakoman@gmail.com> wrote:
Hmm . . . you should see the device.  You shouldn't need any
additional packages for the device to appear in /dev

I have a few questions:

Do you have the same sw revision on both verdex motherboards (& which
rev is it)?
Have you done the jumper wire mod on both of the consoleLCD's?
When you say you verified that the tsc2003 driver is loaded, was that
by doing a lsmod?

Steve

On Jan 30, 2008 1:08 PM, Mike M <mike0599@gmail.com> wrote:
> I don't see a device node (/dev/input/event0 or /dev/input/touchscreen0)
> when I installed gumstix-minimal-image onto my vederx.  I  have another
> verdex that does have these device nodes, but dont' know what the difference
> is between the two.  I verified that tsc2003 is loaded and the udev rules
> look the same for the verdex that has a device node and the one that
> doesn't.  Does anybody have any hints about where to look?  Do I need to
> install a few more packages?
>
> Thanks in advance!
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>
>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
gumstix-users mailing list
gumstix-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gumstix-users