How do I install touch screen drivers?? please help

Discussion in 'General Discussion' started by leodesign, Jan 18, 2014.

  1. leodesign

    leodesign New Member

    Joined:
    Jan 18, 2014
    Messages:
    4
    Likes Received:
    0
    Hello to all.

    So I purchase a touchscreen monitor, it is a fusion touch display model number: F10A-0102 ,and I am trying to integrate it to work with the UDOO Quad. So I made a cable that plugs into the 24 pin connector that the Uddo board provides and connected all the appropriate wires to their perspective counterpart. When I boot up the Udoo I get a message could not apply the stored configuration for the monitors, and nothing happens not even a flicker on the touchscreen. Now, fusion touch supplies these nifty drivers for linux and I have no clue how to install them. So My question Is how do I install these drivers. I am new to linux as this is really the 1st time I've ever used it. And I have been scouring the internet for descriptions on how to install them . My hopes are that some one here can give me a heads up on how to install them. It would be greatly appreciate it. Below I am posting the installation instructions.
    Thank you for the help in advanced.
    Leo

    Installation instructions

    Document Title
    5
    TPK USA LLC Confidential
    2 INTEGRATE TOUCH DRIVER
    2.1
    DRIVER INSTALLATION
    The reference touch driver is contained in two sour
    ce files:
    fusion_0710A.c
    and
    fusion_0710A.h
    .
    To make the touch driver compiled built-in the kern
    el image. These files should be copied into
    the proper driver directory:
    driver/input/touchscreen
    .
    Then the
    Makefile
    and
    Kconfig
    files should be modified to have those files inclu
    ded in the
    compilation of the kernel.

    driver/input/touchscreen/Makefile
    needs to have the extra line:
    obj-$(CONFIG_TOUCHSCREEN_
    FUSION_F0710A
    ) += fusion_0710A.o

    driver/input/touchscreen/Kconfig
    needs to have the extra section:
    config TOUCHSCREEN_
    FUSION_F0710A
    tristate "
    Fusion_F0710A
    touchscreen"
    depends on I2C
    The kernel configuration should be altered to inclu
    de the touch driver. To do so, in the
    configuration, the following item should be selecte
    d when configuring the Linux kernel with
    the command ‘
    make menuconfig
    ’:
    Device Drivers --->
    Input device support --->
    [*] Touchscreens --->
    <*>
    Fusion_F0710A
    touchscreen

    It can also be built as a module:
    Device Drivers --->
    Input device support --->
    [*] Touchscreens --->
    <M>
    Fusion_F0710A
    touchscreen
    After compiling it will produce the file
    fusion_0710A.ko
    in the same folder as where the
    source code is. When the kernel image is running on
    the platform, the module can be loaded
    into the kernel or unloaded from it using the follo
    wing commands:
    Loading:
    / # insmod /sys/lib/modules/fusion_0710A.ko
    Unloading:
    / # rmmod fusion_0710A.ko
     
  2. leodesign

    leodesign New Member

    Joined:
    Jan 18, 2014
    Messages:
    4
    Likes Received:
    0
    I figured it out on my own. In case anyone else has this problem. You need to compile your own kernel. The steps for doing this are in the (Udoo Starting manual) Creating a bootable micro SD card the Hard Way. And it is hard the 1st time :(
     
  3. mkopack

    mkopack Member

    Joined:
    Jun 14, 2013
    Messages:
    451
    Likes Received:
    21
    Hopefully the Udoo team is working on making versions where you just DL the version for whichever LCD you need (or none).
     
  4. shaunak_s

    shaunak_s New Member

    Joined:
    Aug 29, 2014
    Messages:
    16
    Likes Received:
    0
    Hi,

    I have ported the touch drivers for a 10" LCD from fusion but there seems to be something a miss. From the data sheet I understood that the I2C device address is 0x10, however, the touch controller (ATMEGA328) also replies with a NACK during the ACK slot in an I2C communication. I first thought that the controller could have been damaged but it seems to be performing all other tasks on the touch FPC. I can see PWM signals being generated at various test points that have a direct connection with the controller. Not sure what exactly is wrong. Did you come across a similar situation?

    Thanks very much.

    Regards,
    Shaunak
     

Share This Page