Hardware Reference
In-Depth Information
Without that change, the
uinput_mapper
upstart service will fail to find the
tvservice
binary and silently fail.
Your touchscreen should be ready. Reboot your Raspberry Pi to test it:
$ sudo shutdown -r now
When it comes back up, try touching the screen. The cursor should move to where
you touched. If you want to “touch” a click, touch and hold for a half-second and then
release. It will take some getting used to. This setup should work simultaneously with
any other attached input devices (such as a keyboard and mouse), so if you want to
have an “override” console, you can add that easily.
If you need to debug the
uinput_mapper
service, first stop the
xbmc
service:
$ sudo stop xbmc
If you do not do this, XBMC will hold the
uinput_mapper
device, and you won't be able
to access it with anything else for debugging. You can install the
evtest
utility from the
Raspbian repository and use it to debug the events that the touchscreen is registering:
$ sudo apt-get install evtest
$ evtest
No device specified, trying to scan all of /dev/input/event*
Not running as root, no devices may be available.
Available devices:
/dev/input/event0: eGalax Inc. Touch
/dev/input/event1: eGalax Inc. Touch
/dev/input/event2: Logitech USB Keyboard
/dev/input/event3: Logitech USB Keyboard
/dev/input/event4: Logitech USB Optical Mouse
/dev/input/event5: uimapper - touchscreen
Select the device event number [0-5]: 5
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x42 product 0xbebe version 0x1
Input device name: "uimapper - touchscreen"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 106 (KEY_RIGHT)
Event code 273 (BTN_RIGHT)
Event code 320 (BTN_TOOL_PEN)
Event code 330 (BTN_TOUCH)
Event type 3 (EV_ABS)
Event code 0 (ABS_X)
Value 0
Min 0
