This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Touchscreen setup for android 2.3.4/2.1 on beagleboard-xm

Other Parts Discussed in Thread: ADS7846, TSC2004, TSC2007

I've installed the binary prebuild from android 2.3.4-DevKit-2.1, on a beagleboard-xm Rev C.  I've made no changes to the images as distributed by TI.  I just burned them directly to my flash card.

Some things work, including basic Android on a DVI display, with mouse control.

But, I see no signs of life for the touch input.  I tried the 'getevent' command, and the touchscreen event type was not reported, although 3 others were (Microsoft Microsoft Wheel Mouse Optical, gpio-keys, twl4030_pwrbutton).

So, touch input appears inoperable, and leads to few questions . . .

1) Regarding touch control support:  I assumed touch control would be enabled (although uncalibrated), since this is a prebuilt binary for the beagleboard-xm, where the touch controller resides.  On the other hand, I see no reference to touch in the user guide.  So, do I need to enable/install the touch controller support on my own, and if so, what is the procedure for doing so in the prebuilt binary.  I'm assuming the procedure outlined in the porting guide does not apply to prebuilt binaries, but maybe that's wrong.

2) Regarding touch control calibration:  Once I get past insuring the touch controller is alive, what is the correct/best approach for calibrating touch input?  There is a calibration discussion in the porting guide, but that defines the parameters in source code, which presumably requires a source build, or maybe just a runtime module installation.  I've also seen references elsewhere to defining the touch calibration in xorg.conf.  Which of these approaches (or others?) do I follow, keeping in mind I'm attempting to dodge a source build for now?

3) Regarding beagleboard-xm revisions:  The developer guide states that beagleboard-xm revisions through Rev C are supported.  So far I've seen no need to specify my revision anywhere, which suggests the differences don't matter to the software, or if they do, that they're handled automatically.  Am I correct that I don't need to specify the XM revision anywhere?

Ron

  • Hi Ron,

    We don't have touch controller on Beagle-XM board. getevent command will not show touchscreen event type as this not supported by Beagle-XM kernel configuration.

    Which touch controller are you using with Begleboard-XM?

    If you are using a specific touch controller then you have to add its support in kernel. Our AM37 EVM has support for ADS7846 touch controller you can refer to its driver for more details.

    Calibration procedure metioned in the porting guide does not apply to pre-built binaries (Run time calibration). It explains the procedure about the driver tuning for touch calibration. For touch calibration please follow procedure mentioned in porting guide and build kernel sources again and try.

    If board is booting properly with our pre-built images then you need not worry about board revision.

    Thanks and Regards,

    Pankaj Bharadiya

  • Hi Pankaj,

    Thank you for your prompt reply.  I think the point of confusion is that the porting guide states the following:

    The touch controller is ADS7846 with SPI interface (in OMAP35xEVM, AM37xEVM, BEAGLE, BEAGLE-XM)
    and TSC2004 with I2C interface (in AM3517EVM).

    That suggested to me that BEAGLE-XM contained touch controller ADS7846.  I'm uncertain what that porting guide statement means, if the touch controller is in fact not on BEAGLE-XM.

    Anyway, I confirmed with our hardware team that we are using TSC2007 on our own circuitry.  So, I will add kernel support for that device, and then calibrate per the porting guide.

    Thanks,

    Ron

  • Ron,

    It looks like beagleboard has been mistakenly mentioned in the Touchscreen porting guide.

    Thanks for pointing this out. This will be fixed immediately.