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.

mouse pointer not working in ti matrix application running on OMAPL138

Other Parts Discussed in Thread: TSC2007

When i probed the touch screen, the mouse pointer stopped functioning ... but in the minicom, the serial interface, i could see the hardware response, when i connected the mouse to the evm.. but the pointer never functions.... i interfaced tsc2007 touch controller IC....

looking for a solution.........

the problem is with the matrix application file system.... have to correct it some where....

  • A mouse can be used instead of touchscreen input with the Matrix GUI by following these steps. It is also possible to use touchscreen and mouse input simultaneously.

    On your Target File system, edit the file:


    /etc/init.d/matrix-gui-e


    This script file will set Mouse support by default, but if it detects a touchscreen, then it will setup touchscreen support. If you comment out the touchscreen support then the default will remain mouse support. Use the '#' to comment out the line below:

    the file is as shown below


    #! /bin/sh

    matrixgui="/usr/bin/matrix_guiE"
    GUI_OPTS="-qws -display transformed:Rot0 /usr/share/matrix/html/menu_main_1.html"
    PIDFILE="/var/run/matrix-gui-e.pid"

    test -x "$matrixgui" || exit 0

    export TSLIB_TSDEVICE=/dev/input/touchscreen0
    export QWS_MOUSE_PROTO=Tslib:/dev/input/touchscreen0

    case "$1" in
      start)
        chvt 4
        if [ ! -f /etc/pointercal ] ; then
            echo -n "Calibrating touchscreen (first time only)"
            ts_calibrate
            echo "."
        fi

        if [ -e $PIDFILE ]; then
          PIDDIR=/proc/$(cat $PIDFILE)
          if [ -d ${PIDDIR} -a  "$(readlink -f ${PIDDIR}/exe)" = "${matrixgui}" ]; then
            echo "$DESC already started; not starting."
          else
            echo "Removing stale PID file $PIDFILE."
            rm -f $PIDFILE
          fi
        fi

        echo -n "Starting Matrix GUI application"
        start-stop-daemon --start --quiet --background --exec $matrixgui -- $GUI_OPTS
        pidof ${matrixgui} > $PIDFILE
        echo "."
        ;;

      stop)
        echo -n "Stopping Matrix GUI application"
        start-stop-daemon --stop --quiet --pidfile /var/run/matrix-gui-e.pid
        echo "."
        ;;
      *)
        echo "Usage: /etc/init.d/matrix-gui-e {start|stop}"
        exit 1
    esac

    exit 0


    here lies the selection for the control for touch screen and mouse

    export TSLIB_TSDEVICE=/dev/input/touchscreen0
    export QWS_MOUSE_PROTO=Tslib:/dev/input/touchscreen0

    For Mouse support, Replace:

    export TSLIB_TSDEVICE=/dev/input/touchscreen0
    export QWS_MOUSE_PROTO=Tslib:/dev/input/touchscreen0

    with

    export TSLIB_TSDEVICE=/dev/input/touchscreen0
    #export QWS_MOUSE_PROTO=Tslib:/dev/input/touchscreen0

    thus we made it inactive...

    to make work both the touch screen and mouse pointer simultaneosly, replace the two lines with

    export TSLIB_TSDEVICE=/dev/input/touchscreen0
    export QWS_MOUSE_PROTO="Tslib:/dev/input/touchscreen0 Auto"

    which selects the both devices...






  • The Kernel has been configured to enable mouse support in your SDK, so this step is not necessary if you are using the SDK.

    If you have built your own kernel: The kernel must be configured to include the PS/2 mouse support. To verify this, run the menuconfig utility.But before running this you should have allthe cross compilers in your pc.

    From you Linux root directory:
    make  menuconfig
    

    or


    From you Linux root directory: make ARCH=arm CROSS_COMPILE=arm-arago-linux-gnueabi- menuconfig

    Look under:

    Device Drivers ---> Input device support ---> <*> Mouse interface

    Device Drivers ---> Input device support ---> <*> Mice --->

    If mouse support is not already included in the kernel, enable the above two configuration by typing 'y' and rebuild the kernel.