Saturday, January 19, 2013

Adding 7inch display with touchscreen to Raspberry PI

Hi!

First thing I got in mind when seeing Raspberry PI was "car PC project".
The targeted display was 7 inch with touchscreen. I have found a lot of displays on Ebay.

I have got myself one for 85 dollars with free shipping(this; if it is not available any more you can search "reversing driver board hdmi" on ebay and you will find others). The display driver board has hdmi input and an on board resistive touchpanel with usb controller board.

It took less than a month to receive it(in Romania). After unpack, it worked out of the box with Ubuntu 12.10(display + touchpanel) and with Windows, but for Windows I had to install some drivers also received in the package.

I have installed latest Raspbian image on a SD_Card and tried it on my Raspberry PI model B, but the touchpanel didn't show any input. After searching a lot I have decided that I have to recompile the raspbian kernel and add support for touchpanel. This sounded very new to me but it seemed to be an easy task.

First thing, I have run lsusb to see the touch controller type(on RaspberryPI):
pi@raspberrypi ~ $ lsusb
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
Bus 001 Device 005: ID 0eef:0001 D-WAV Scientific Co., Ltd eGalax TouchScreen
Last device is the touch controller, from eGalax.

Edit: If you don't want to build the kernel by yourself, you can download mine from here. After his, you have to replace file /boot/kernel.img and /lib/firmware and /lib/modules/ on the SD card.

Building a new kernel(in UBUNTU 12.10).
Get kernel sources.
wget https://github.com/raspberrypi/linux/archive/rpi-3.6.y.tar.gz
tar -zxvf  rpi-3.6.y.tar.gz
Install some dependencies.
sudo apt-get install git libncurses5 libncurses5-dev qt4-dev-tools build-essential
Install toolchain.
The best way to do the kernel compilation is on a Desktop/Laptop machine, which will be much more fast than on the Raspberry PI. I have did this in Ubuntu 12.10:
sudo apt-get install gcc-arm-linux-gnueabi
After download of the kernel archive has finished unpack it and then navigate with terminal to the extracted folder.
Be sure thaat the sources objects are cleaned. Type:
make mrproper
Create a folder for the generated kernel:
mkdir ../kernel
Generate the .config file:
make O=../kernel/ ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- bcmrpi_cutdown_defconfig
Configure the kernel:
make O=../kernel/ ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- xconfig
In the opened window press the | button to collapse all items. Then, navigate to Device Drivers->Input Device Support->TouchScreens and select it. Here, be sure to check also your touch screen controller if it is other than eGalax, or if it is not selected. Now press save.

With the changes being made you can now compile the kernel:
make O=../kernel/ ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- -k -j3
Note: -j3 option from the end means to enable parallel build. The number should be number of cpu cores + 1(I have dual core cpu).

The build took about 20 minutes on my PC. After the build completes, you will have the new kernel in ../kernel folder, created above.

Create the kernel image:
cd ../
git clone git://github.com/raspberrypi/tools.git
Note: You need to have git installed.

Navigate to tools/mkimage and then run:
./imagetool-uncompressed.py ../../kernel/arch/arm/boot/Image
This command will generate the kernel image(kernel.img file).

Build modules:
Go back to the ../kernel/ folder.
mkdir ../modules/
make modules_install ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- INSTALL_MOD_PATH=../modules/

Replace the kernel:
Get latest firmware:
wget https://github.com/raspberrypi/firmware/archive/next.tar.gz
tar -zxvf next.tar.gz
In the small partition(/boot) do:
  • replace /boot/bootcode.bin with firmware-next/boot/bootcode.bin
  • replace /boot/kernel.img with the previously created kernel image
  • replace /boot/start.elf with firmware-next/boot/start.elf
In the big partition(/root) do:
  • replace /lib/firmware with <modules_builded_above_folder>/lib/firmware
  • replace /lib/modules with <modules_builded_above_folder>/lib/modules
  • replace /opt/vc with firmware-next/hardfp/opt/vc/
Now your card should contain the new image. Safely eject your SD card and then unplug it from the card reader and then put the card in Raspberry PI and start X(startx). Plug the touch controller in one usb and check if you can move the cursor(or you can start with he touch already plugged in).

After I have started X, my touch input was working but the axes were switched and also not calibrated.

Calibration for the touchscreen(in Raspberry PI). 
Note: The next steps are performed in the Raspberry PI's Debian Wheezy. This is a method for calibrating the touchscreen which will work just for Xserver and Xserver based applications.

Install xinput_calibrator.
Install some dependencies:
sudo apt-get install libx11-dev libxext-dev libxi-dev x11proto-input-dev
Download xinput_calibrator somewhere in the Raspberry PI's folder structure.
wget http://github.com/downloads/tias/xinput_calibrator/xinput_calibrator-0.7.5.tar.gz
Unpack it and then navigate to the unpacked folder and then install it using:
./configure
make
sudo make install
After this step you should run xinput_calibrator(from Xserver terminal console: first startx then open console and then run it).
xinput_calibrator
Follow the on screen instructions(touching some points on screen) and after calibration is complete you will receive a message like this:
Calibrating EVDEV driver for "eGalax Inc. USB TouchController" id=8
    current calibration values (from XInput): min_x=1938, max_x=114 and min_y=1745, max_y=341

Doing dynamic recalibration:
    Setting new calibration data: 121, 1917, 317, 1741


--> Making the calibration permanent <--
  copy the snippet below into '/etc/X11/xorg.conf.d/99-calibration.conf'
Section "InputClass"
    Identifier    "calibration"
    MatchProduct    "eGalax Inc. USB TouchController"
    Option    "Calibration"    "121 1917 317 1741"
    Option    "SwapAxes"    "1"
EndSection

For Raspbian you have to create a file:
sudo nano /usr/share/X11/xorg.conf.d/01-input.conf
Add in this file the content above(starting with Section "InputClass" line) and then save it(ctrl+O).

Note:
Please make sure that you don't have sections like
MatchProduct    "eGalax Inc. USB TouchController"
in other files from /usr/share/X11/xorg.conf.d/ folder(highest number files are processed last, thanks to Jasmin).

Now touchscreen should be calibrated and after reboot it will keep the settings.
Once, I had to run xinput_calibration again in order to have the pointer to the desired points. You can update the numbers given by the xinput_calibration utility in the
usr/share/X11/xorg.conf.d/01-input.conf file in order to have the best calibration at boot.

Soon I will add some pictures.

Andrei

135 comments:

  1. It worked fine ! Thanks !
    Just a suggestion to help others out there who might get stuck...

    In Build modules:

    Instead of
    {Go back to the linux-rpi-3.6.y folder.}

    I have used
    {Go to the built kernel folder}

    and then

    mkdir ../modules/
    make modules_install ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- INSTALL_MOD_PATH=../modules/

    Also the system complains that some packages are missing when trying to build xinput_calibratror
    (x11 for example).

    All the best,
    Helio.

    ReplyDelete
  2. To install the dependencies of xinput_calibrator you can use

    apt-get update
    sudo apt-get install libx11-dev libxext-dev libxi-dev x11proto-input-dev


    Regards,
    Helio.

    ReplyDelete
  3. My calibration went fine, the axes were not swapped. The first calibration solved just fine. As base system I've used the last raspbian, 2013-02-09-wheezy-raspbian .
    Now I'm going to install XBMC: http://www.raspbian.org/RaspbianXBMC

    Regards,
    Helio.

    ReplyDelete
    Replies
    1. Hi!
      I have just finished building XBMC(xbmc-rbp git) on 2012 whezy image with custom kernel but video doesn't work :(.
      Note: I had to comment in file /usr/include/interface/vmcs_host/vcgencmd.h line:
      #include "vchost_config.h"
      It build in about 11 hours and not working. Very frustrating.
      I only got the video to work in a build with original kernel.
      One more note: after installing run it using /usr/lib/xbmc/xbmc.bin
      I will try tomorrow again with latest image and latest firmware.

      Regards,
      Andrei

      Delete
    2. How did it go? Did it work?
      I've managed to compile kernel for raspbmc distribution but the problem is you cannot run console under GUI, and there is no terminal emulation program what so ever.
      If only that would work in raspbmc it would be the smallest and cheapest media center with touch support.

      Delete
    3. Hi Jasmin!

      I have managed to build xbmc from latest git(which now is version 13 alpha 1).
      Good news: videos are working(streamed from my sd card) and also touchscreen is working(with the new module).
      Bad news: no addon is working, so I couldn't test youtube or other addons, maybe because there are some bugs in the alpha release.
      Now I am compiling latest stable XBMC v12 which should work fine, but I have to wait a couple of hours.
      When this will be done I will set up a tutorial and also I will try to provide a package.

      Regards,
      Andrei

      Delete
    4. Hi Andrei:

      I'm trying to compile XBMC but I'm running out of memory... Due to the fact that I've built a custom kernel there are no split files in the /boot directory... how did you do to compile xbmc ? How did you increase the available memory ? Thanks, Helio.

      Delete
    5. Hi Helio!

      To increase memory for building XBMC on Raspberry PI please have a look at step 3 in this post:
      http://www.engineering-diy.blogspot.ro/2013/02/build-xbmc-frodo-from-source-in.html

      Delete
  4. Hi Andrei: I'll try do compile during the weekend...Glad to know that it's working !
    Thanks ! Best Regards, Helio.

    ReplyDelete
  5. Heya¡­my very first comment on your site. ,I have been reading your blog for a while and thought I would completely pop in and drop a friendly note. . It is great stuff indeed. I also wanted to ask..is there a way to subscribe to your site via email?


    calibration company

    ReplyDelete
    Replies
    1. Hi!

      I have added couple of ways to subscribe.
      Thank you for the friendly note! :)

      Stay tuned! Raspbian+XBMC12+eGalax(calibrated+working single click)+Navit coming soon!

      Andrei

      Delete
  6. I bought the same 7" display with touchscreen that you linked, but as a power supply is not included, I need to find one. From what I understand, I need something that outputs 12V and has the appropriate sized connect to fit into the power port. Beyond that, I am ignorant. Do I need to pay attention to the amps on the power supply? Do I have to get a bulky power brick that takes up valuable real estate on my power strip or can I get something that is like a laptop power cord where the bulky part is in the middle of the cord?

    Can you recommend a good place to get a power supply for this - I usually shop at Amazon, eBay, Monoprice, and Newegg.

    Lastly, if I want to power both my Raspberry Pi and the screen you discuss in this post, can I do so with a single portable battery - like this one on Amazon? http://www.amazon.com/Anker%C2%AE-Astro3-10000mAh-Multi-voltage-output/dp/B005NGKR54/

    ReplyDelete
    Replies
    1. After reading the datasheet(http://www.vslcd.com/Specification/AT070TN92%20V.5.pdf), I have found out that you need 300mA minimum for the touchscreen and display driver. I have my touchscreen powered by a 12V 500mA power supply(AC-DC adaptor which was found around the house, for example the wifi router has a good power supply).
      You can find these adaptors on ebay:
      http://www.ebay.com/sch/i.html?_sacat=0&_from=R40&_nkw=ac-dc+adaptor+12v&_sop=15
      Regarding powering both from the same power supply I think you have to make some tests. For example, I saw that if I let the display unconnected and then start RPI and then start the display, the display never gets image on hdmi.
      Also if I connect the power supply of the display and power supply of the RPI at the same time the screen gets image and it is working fine.
      That power supply from Amazon looks pretty good and it certainly can handle both the screen and the RPI(2A for RPI it is more than enough to let you plug some usb devices)

      Please let me know how it goes(I am also reading your post on RPI forums:http://www.raspberrypi.org/phpBB3/viewtopic.php?f=64&t=33451&sid=6f0eecab55d588f94d4469e70cd75d53&p=293863)

      Regards,
      Andrei

      Delete
    2. Hi Will,

      Regarding the tests I have mentioned before, I don't think it is necessary anymore. I have tested with the latest debian wheezy image(which has a new firmware) and you don't have to plug first the display. If I am disconnecting the power chord of the display while PI is runing and then connect it back after a while it is working:)

      Regards,
      Andrei

      Delete
  7. I have a problem with permanent config. I did everything as told in tutorial but my touch alway needs to be recalibrated at reboot.
    Any advices...

    ReplyDelete
    Replies
    1. Hi Jasmin!

      You just have to follow these steps:
      sudo nano /usr/share/X11/xorg.conf.d/01-input.conf
      Add here the text given by xinput_calibrator, but not the whole text, just this part:
      Section "InputClass"
      Identifier "calibration"
      MatchProduct "eGalax Inc. USB TouchController"
      Option "Calibration" "121 1917 317 1741"
      EndSection

      Andrei

      Delete
    2. Thank you very much for your reply.
      I did it just like you written, but still after every reboot calibration is lost and it needs to be done again. Is it possible to store it somwhere in fstab so it can point to that file.
      Keep up the good work. Can't wait for you build of xbmc.

      Delete
    3. Hi Jasmin!

      Sorry but I don't know how to help you with the calibration. On all my images it was working as I wrote in the post. I don't know why it is not loaded automatically.
      With Raspberry PI model B and latest debian wheezy it is working.
      My build of XBMC 12 is ready, with touchscreen working well on Raspbian.
      Check it out at:
      http://www.engineering-diy.blogspot.ro/2013/02/raspberry-pi-raspbian-xbmc-and-egalax-7.html

      Andrei

      Delete
    4. Well I tried again with newest raspbian wheezy. Still no luck, after I write config to a file 01-input.conf and reebot, it behave like I didn't write that file at all.
      I'm very thankful for your effort and hard work anyway and hope someone will help me.

      Delete
    5. IS there a service that needs to be restarted after writing configuration?

      Delete
    6. One more question,
      is it possible that problem I am having is because I used win32 disk imager on windows.
      I didn'use linux for writing on sd card?

      Delete
    7. Hello Andrei,

      at first I want to thank you a lot for this really great working tutorial!! :)

      But I got the same issue like Jasmin - the calibrated settings in the created file are copied like you wrote, but After a reboot I have to calibrate again :-/

      Any other ideas?

      THX!!

      Chris

      Delete
  8. Do anybody knows how the kernel for Fedore remix can be rebuild like this one here?

    Thanks :)

    ReplyDelete
    Replies
    1. It's best to do it on ubuntu.
      I was working on debian 6.0 and I didn't made it work, then I booted virtual machine with ubuntu it all went well.
      My advice - use ubuntu

      Delete
  9. Hi there,

    I followed the steps on Ubuntu 12.01and was able to compile the kernel. When I reach
    make modules_install ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- INSTALL_MOD_PATH=../modules/

    I get:
    Configuration file ".config" not found!
    make[2]: *** [silentoldconfig] error 1
    make[1]: *** [silentoldconfig] error 2

    Do you have any ideas?

    tia

    Sebastian

    ReplyDelete
    Replies
    1. Hi Sebastian!

      Please navigate to the folder kernel(cd ../kernel from the linux_x_x folder).
      Then, run again
      make modules_install ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- INSTALL_MOD_PATH=../modules/

      I have to update the post.

      Andrei

      Delete
    2. Hi Andrei,

      looks great, works fine...

      tia

      Sebastian

      Delete
  10. Replies
    1. I have added an archive with my kernel. Please see the yellow note from the post.

      Andrei

      Delete
  11. Just wanted to let you know that I've made it work. If anyone will have ther same problem with permanent calibration. Key file is 10-evdev.conf so if you have at the end of file egalax part, you need to change the values. Watch for file number in front of the file, highest number is processed last so if you have bad configuration in 99-input.conf, regardless of your 01-input.conf it will load the highest with his configuration. Anyway I had to add invert axis = 1 and Invert x axis and invert y and it was working.
    Anyway thank you Andrei you helped very much with your work. Now hitting the xbmc :-)

    ReplyDelete
    Replies
    1. Hi Jasmin!

      Congratulations!
      Glad that you have found the issue. I will update the post.

      Thank you!

      Delete
    2. Hi,

      I had the same problem and solved it like Jasmin said:
      The basis was a Debian weezy on a atom board. The Touch was accepted, but with swaped axis.

      I run xcalibrate and had following result:

      Calibrating EVDEV driver for "eGalax Inc. USB TouchController" id=7
      current calibration values (from XInput): min_x=1964, max_x=75 and min_y=149, max_y=1890

      Doing dynamic recalibration:
      Setting new calibration data: 1949, 66, 140, 1896


      --> Making the calibration permanent <--
      copy the snippet below into '/etc/X11/xorg.conf.d/99-calibration.conf'
      Section "InputClass"
      Identifier "calibration"
      MatchProduct "eGalax Inc. USB TouchController"
      Option "Calibration" "1949 66 140 1896"
      EndSection

      I performed the follwing command:
      sudo nano /usr/share/X11/xorg.conf.d/01-input.conf

      and added the Section from above:

      Section "InputClass"
      Identifier "calibration"
      MatchProduct "eGalax Inc. USB TouchController"
      Option "Calibration" "1949 66 140 1896"
      EndSection

      addidtionally I added >Option "SwapAxes" "1"<, so that now the content of the file was

      Section "InputClass"
      Identifier "calibration"
      MatchProduct "eGalax Inc. USB TouchController"
      Option "Calibration" "1949 66 140 1896"
      Option "SwapAxis" "1"
      EndSection

      The additional Swap made the Touch work as desired after startup.
      Thank you very much for your detailed description, so that I could get there.

      Delete
  12. Thank you for the great tutorial!!! I followed instruction but took you compiled kernel. Everything works fine but for what ever reason Keyboard and Mouse are not working anymore. dmesg output:

    [ 39.658584] usb 1-1.2: new low-speed USB device number 4 using dwc_otg
    [ 39.765606] usb 1-1.2: New USB device found, idVendor=046d, idProduct=c050
    [ 39.765638] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [ 39.765653] usb 1-1.2: Product: USB-PS/2 Optical Mouse
    [ 39.765667] usb 1-1.2: Manufacturer: Logitech
    [ 39.777685] input: Logitech USB-PS/2 Optical Mouse as /devices/platform/bcm2708_usb/usb1/1-1/1-1.2/1-1.2:1.0/input/input0
    [ 39.780003] hid-generic 0003:046D:C050.0001: input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-bcm2708_usb-1.2/input0
    [ 39.873193] evdev: disagrees about version of symbol module_layout

    Xorg log:

    [ 25.937] (EE) FBDEV(0): FBIOBLANK: Operation not permitted
    [ 39.756] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/mouse0)
    [ 39.757] (II) No input driver specified, ignoring this device.
    [ 39.757] (II) This device may have been added with another device file.


    Is there anything I can do?

    ReplyDelete
    Replies
    1. Hi!

      If you had removed /lib/modules and /lib/firmware and put the new ones and also kernel.img file, on the latest firmware(or Raspbian Wheezy image this should have worked).
      I suggest you to build the kernel by yourself if the above steps were correctly done.

      Delete
    2. I missed the delete before add :-( its working. Calibration within X is fine but within XBMC it looks like the configuration will be ignored. I added the touchscreen_axes_calib but nothing changed. Will have a look at the logs.

      Delete
    3. Hi,

      i don´t get the xbmc calibration to function properly. I can put whatever values in touchscreen_axes_calib without any change. Is there anything I can do? Is there some kind of event_log I could use for debugging?

      Delete
    4. Hi!

      If you have built XBMC with my patches, please send me your xbmc.log file, with debug level set to 2(see here http://wiki.xbmc.org/index.php?title=Log_file/Advanced).

      Delete
    5. http://www.youbeto.de/www/xbmc.log

      Thank you in advance!

      Delete
  13. You Sir, are a true gentleman and a scholar.

    Thank you for posting this!

    ReplyDelete
  14. This comment has been removed by the author.

    ReplyDelete
  15. hi andrei,

    thank you for ur build!

    i got all running, and the calibration is fine, expect the y-axe is inverted.

    pi@raspberrypi ~ $ cat /etc/X11/xorg.conf.d/99-calibration.conf
    Section "InputClass"
    Identifier "calibration"
    MatchProduct "eGalax Inc. Touch"
    Option "Calibration" "1981 16 97 1958"
    EndSection

    and

    pi@raspberrypi ~ $ cat /usr/share/eGalaxCalibration/touchscreen_axes_calib calib_x_d=-16;calib_x_fact=0.651399;calib_y_d=-119;calib_y_fact=-0.393013100;swap_axes=0;

    with that the y-axe doesnt move anymore! only the x-axe is working. if i remove the "-" its still inverted....

    what can i do?

    ReplyDelete
    Replies
    1. in xbmc of course ;)

      in lxde it is working fine!

      Delete
    2. Hi!

      We have this formula for y axis:
      pointer.y = screen_height - value_read.y * calib_y_fact - calib_y_d;
      So, if you put both calib_y_d and calib_y_fact negative, the resulting formula will be:
      pointer.y = screen_height - value_read.y * (-0.393013100) - (-119);
      which is:
      pointer.y = screen_height + value_read.y * 0.393013100 + 119;
      which is wrong.
      In order to switch y orientation, you have to do something like this:
      the original formula:
      pointer.y = screen_height - value_read.y * calib_y_fact - calib_y_d;
      calib_y_d = screen_height (get this from your screen resolution)
      calib_y_fact=-0.393013100
      If you have to move the pointer up or down, put calib_y_d like this:
      calib_y_d = screen_height - value
      where value should be an offset, like 119, for example

      Hope it is clearer now.
      Good luck!

      Delete
  16. Hi,

    I'm so glad I've found this blog!

    With the help of this blog, I was able to get to the point of the calibration. But there something is strange.

    When the system starts, the calibration is wrong. When I tap on the top of the screen, the mouse pointer shows up on the right. When I tap on the right, it shows on the bottom etc...

    So I run the calibration utility. It then says: swapping X & Y etc... and gives me values.
    At that time, the calibration is STILL wrong, but now top and bottom are swapped, and so are left and right. So I re-run the calibration utility, and now it's correct!

    The strange part is that the utility now doesn't say "reversing axis" anymore, and it also doesn't propose the Option "SwapAxis" "1" line for the 01-input.conf file either.

    So then I enter the values I get into the usr/share/X11/xorg.conf.d/01-input.conf file. I quit X and restart. Then the mouse pointer is off again, just like the first time.

    Now, for the thing I have in mind for this screen, it would have to be on all the time in X, so on one hand it's not such a big task to do the calibration twice and then just leave it on. But it bugs the hell out of me. I just want it to work!

    I also read this:[i] --> Making the calibration permanent <--
    copy the snippet below into '/etc/X11/xorg.conf.d/99-calibration.conf'[/i]

    Is this correct? Do I need to create this file as well as create the usr/share/X11/xorg.conf.d/01-input.conf file?

    Do you have any idea what is going wrong here?

    Thank you!
    Bart

    ReplyDelete
    Replies
    1. Oh, and also this:

      I've found there's a slight error in your blog. In the final part is says:
      Option "SwapAxes" "1"

      And it's true: even the configuration utility says "SwapAxes". It's just that is needs to be "SwapAxis" (with, an 'i', not an 'e'), or otherwise X will give you an error and the GUI won't load.

      Delete
    2. Would you believe that TWO minutes after posting this above comment, I got it to work! It seems is line IS "SwapAxes" "1" and NOT "SwapAxis" "1"!!! I have no idea why X gave an error the first time, but now it works. So please, DISREGARD all my above comments. :)

      But you have to admit that it's confusing, because after all, it's the Axis the gets swapped, not the Axe... Oh well...

      Now the only thing I would like to know: is there any way of RIGHTclicking onto a certain icon? The windows software of this touchscreen, which I've used for years, could do that, and that was very handy! But I'm wondering if there's also a way in X...

      Thanks!

      Delete
  17. Oh yeah, and one other question (last one, I promise! :) )

    If I update the kernel in the future (with RPI-update, see here: https://github.com/Hexxeh/rpi-update ), will this erase the touchscreen additions to the kernel? (I did not re-create the kernel from scratch as I don't use Ubuntu, I'm a *cough cough* Windows user - I used your pre-built kernel and replaced the kernel and /lib and /modules maps)

    Can I still sudo update && sudo upgrade safely?

    I'd hate for this to break again...

    Thanks!
    Bart

    ReplyDelete
    Replies
    1. Hi Bart!

      I am glad that my blog helped you.
      Option "SwapAxes" is for both x and y axes so that's why it is with 'e' and not 'i'.
      You can use rpi-update but disable kernel updates by setting SKIP_KERNEL = 1 in the rpi-update file. If you want to have also latest kernel I think, but not 100% sure, that you have to compile it by yourself again from source, with eGalax module.

      Regards,
      Andrei

      Delete
  18. I have had an 7inch touchscreen in my drawer for 4 years and never got it to work with my favorite distro Debian. today I received my Raspberry Pi board, found this article and now the touchscreen is finally working thanks to you're work on this article. Thanks !
    Up and running within 30 minutes.

    ReplyDelete
  19. Appreciation for nice Updates, I found something new and folks can get useful info about BEST TRAINING online

    ReplyDelete
  20. Appreciation for this guide. I want to ask how to replace files in the small partition(/boot) and the big partition(/root)? Doing this in the PC or in raspi? Thx

    ReplyDelete
    Replies
    1. Hi!

      You can do this from your Raspberry PI or with a card reader from your PC but remember that you have to have super user rights.

      Delete
    2. Hello~
      Thanks for your helps. I did as your guides and succeeded, but the compiled kernel had problem about the FTDI ft232. I then rpi-updated to fix the problem and the thouchscreen couldn't work again. Can this way get the latest kernel? Theoretically, your way should get the newest kernel, but I don't know why the rpi-update still update and overwrite my compiled version overall.

      Delete
  21. @Andrei... First off, many thanks for an amazing great blog post. I got the itch to build a raspberry pi based touchscreen computer for my 3d printer, and I was way over my head until I saw this post. I took the shortcut and loaded your image with XBMC and proceeded to calibrate my screen and load the 3d printing software as well as tightvnc and e17 window manager(it has a great theme for touchscreen displays). Somewhere along the line, I ran into the same problem as qftp. All the updates overwrote something, and now my touchscreen no longer works. My current thought is to reload your image to another sd card and copy over the kernel image and other files/directories. Is there another (easier) way?

    Thanks again for your posts!

    ReplyDelete
    Replies
    1. Hi Daniel!

      I don't think it will work unless you are compiling the new kernel with the egalax module loaded.
      I will do this some time, but I don't know when.

      Regards

      Delete
  22. can i able to install windows8 mobile module

    ReplyDelete
  23. I am really shocked by the info of this website and i am glad i experienced a seem over the weblog. thank you so a lot for sharing this sort of wonderful data.
    Prom Limo Service
    limo service nj

    ReplyDelete
  24. I have one problem.
    I cant find lib on my sd card.
    Where do you can find /lib?
    I have only /boot and /revovery?

    ReplyDelete
    Replies
    1. Hi Stijn!

      /lib should be in the root of the sd card. If you have started from Raspbian OS it should be there. I don't know about other distributions.
      You can have a look here for the linux folder structure:
      http://www.comptechdoc.org/os/linux/commands/linux_crfilest.html

      Delete
  25. Hi Andrei congrats on job well done!!!
    You should save the data on this blog like permanent website.
    It will help people around the world.
    I'm still working on it to make the calibration in xbmc but I cant get it right. Keep this blog up and running with this great info.
    Thank you Andrei.

    ReplyDelete
    Replies
    1. Hi Jasmin!

      Thanks a lot for the appreciation!
      I will start creating a website but at this moment I don't have much time for this.
      If I can help you with the calibration please let me know.

      Delete
  26. Hi
    I have donwloaded your raspbian image, can you tell me what the user name and password is for the default account please? I'm stuck at the 'raspberrypi login:' prompt after boot.
    Thanks

    ReplyDelete
    Replies
    1. Hi Darren!

      Username is 'pi' and password 'a'.
      Please use the latest image from http://engineering-diy.blogspot.com/2013/08/car-pc-projectaugust-2013-update.html

      Delete
  27. Hey dude,

    i took your image. it works pretty fine, the touchscreen calibration in desktop mode also. but my xbmc calibration doesnt work. do you have any idea or can help me?

    with best regards
    astradslme

    ReplyDelete
    Replies
    1. Hi :-D,

      Please use my latest image(from the latest post).
      In order to calibrate xbmc touch you have to edit the file /usr/share/eGalax/touchscreen_axes_calib and put in there the best values for your display.
      You can read about getting these values at http://www.engineering-diy.blogspot.ro/2013/02/raspberry-pi-raspbian-xbmc-and-egalax-7.html, in chapter 4.

      Delete
  28. I'm not sure where you are getting your info, but good topic.
    I needs to spend some time learning more or understanding more.

    Thanks for fantastic information I was looking for this information for my
    mission.

    Look at my web-site :: Orangenhaut

    ReplyDelete
  29. Good Evening, after farting about with my RPi for a couple of months I found this thread. First of all thank you very much, this is one of things of I had been wanting to do. Second of all, after trying, unsuccessfully, for a couple of hours this morning when my screen arrived I decided to download your CarPC image. With it downloaded and the image written to my SD card I finally had a working touch screen, only problem is the touch in inverted across the X-axis i.e. when I touch the left hand side of the screen the pointer appears on the right hand side, the same distance from the centre of the screen as where my finger. Any help would be much appreciated

    Euan

    ReplyDelete
    Replies
    1. Hi Euan,

      You just need to change some values in /usr/share/eGalaxCalibration/touchscreen_axes_calib.
      You will have something like this:
      calib_x_d=-21;calib_x_fact=0.66013409;calib_y_d=-50;calib_y_fact=0.410724472;swap_axes=0;click_confines=8
      You have to set calib_x_fact=-0.66013409(a negative value)
      Also you have to set calib_x_d=1301(which means 1280 + 21, assuming your screen width in pixels is 1280).
      For more information about how to set this properly, please have a look at
      http://www.engineering-diy.blogspot.ro/2013/02/raspberry-pi-raspbian-xbmc-and-egalax-7.html on sections 4 and 5.

      Delete
    2. So if I run xinput_calibrate from the terminal I should get the above in the window and all I do is put a minus infront the calib-x-fact=number and that should rectify the problem? Thanks for the assisstance

      Delete
    3. In order to get the values for touchscreen_axes_calib, first you have to run xinput_calibrator and then you have to compute your values as it's being said in http://www.engineering-diy.blogspot.ro/2013/02/raspberry-pi-raspbian-xbmc-and-egalax-7.html in chapter 4. Tochange the direction of one axis you have to multiply calib_x_fact by -1 and also change the calib_x_d to be equal to your screen width.
      Please have a look at the formula implemented.

      Good luck!

      Delete
  30. I found that you have to run the xinput_calibrator program about three times to get the correct values.
    Once you have run it three times put the text into the 01-input.conf file.

    If the first time you run it, it suggest you need the "SwapAxes" = "1" addition, then add it, even if it does not report you need on the second and third run of xinput_calibrator. Took me all afternoon to figure this out so hopefully it might save someone some time!

    ReplyDelete
  31. Hi Andrei
    I have downloaded your image with XBMC 12 and it is working well for 7 inch touch screen. But for 8 inch touch screen the calibration is lost after reboot. I am using 8 inch HDMI monitor with USB touch (make - FEEL WORLD). please help me to fix this issue. Is the xinput calibrator supports only 7 inch touch screen?

    Seenivas

    ReplyDelete
    Replies
    1. Hi Seenivas!

      xinput_calibrator should work with different screen sizes and resolutions. Is the calibration ok before rebooting?
      If so, please have a look at the following statement:
      Please make sure that you don't have sections like
      MatchProduct "eGalax Inc. USB TouchController"
      in other files from /usr/share/X11/xorg.conf.d/ folder(highest number files are processed last).

      Regards

      Delete
    2. Hi Andrei
      Thanks for reply
      I am using the same make touch screen(both 7 inch and 8 inch from FEEL WORLD). Touch calibration for 7 inch working well without any problem.
      The calibration output for 7 inch
      Section "InputClass"
      Identifier "calibration"
      MatchProduct "eGalax Inc. Touch"
      Option "Calibration" "2004 42 97 1954"
      EndSection

      I have copied the above in /usr/share/X11/xorg.conf.d/01-input.conf , it's working well after reboot.

      Then I have calibrated 8 inch touch screen , the output is

      Section "InputClass"
      Identifier "calibration"
      MatchProduct "eGalax Inc. Touch"
      Option "Calibration" "88 1995 1899 102"
      EndSection

      I have copied the above in /usr/share/X11/xorg.conf.d/01-input.conf

      I have checked before reboot touch working well. But after reboot touch not working ....If I touch bottom right corner the cursor shows on top left corner. Please help me.

      Regards
      Seenivas. seenivenkat@gmail.com (if possible please mail me)





      Delete
    3. Turn the connector between the touchpanel and the USB module. You can plug it two different modes.

      Delete
  32. and I have ensured sure suggestion
    "
    Please make sure that you don't have sections like
    MatchProduct "eGalax Inc. USB TouchController"
    in other files from /usr/share/X11/xorg.conf.d/ folder(highest number files are processed last). "

    Regards
    Seenivas

    ReplyDelete
    Replies
    1. Hi!

      I am sorry but I don't know how to help you more. I haven't encountered this kind of issue.

      Delete
  33. Hi Andrei!

    Thanks for perfect guide. It's really good. Have you had a situation when /usr/share/eGalaxCalibration/touchscreen_axes_calib is not read. Well I mean that I've set all the params there, but xbmc writes to the output default params only. Do I need to set some specific permissions or any additional settings to check?
    Thanks in advance.

    Best Regards
    Dzmitry

    ReplyDelete
    Replies
    1. Found out - silly copy\paste error from calc. Had "," instead of "." in values :)

      Delete
  34. With blogs like this around I don't even need website anymore.
    I can just visit here and see all the latest happenings in the world.

    ReplyDelete
  35. Hi Everybody!

    I have a new error message if I would like to calibrate my touchpanle:

    $ xinput_calibrator
    Error: No calibratable device found.

    It's interesting, because the panel is connected to my Raspberry Pi over USB cable, and I've used this a few days.

    I tried the touchpanel with other device, and it's working fine (--> no hw problem).

    The Raspberry Pi is found the panel:

    $ lsusb
    ...
    Bus 001 Device 010: ID 0eef:0001 D-WAV Scientific Co., Ltd eGalax TouchScreen

    But I can't use it,

    I updated the firmware, reboot, etc... no changes.

    What dou you think what is the problem? Why couldn't access the RPi my touchpanel more?

    ReplyDelete
  36. Hi andrei, I have a question.
    I've followed your 'tuto' for recompile the kernel; but I've tried the option about copying your files. Ok; but I've tested that after those changes my raspberry pi, reboots when I send a poweroff, halt, etc. Do you know what can are happening?
    thanks in advance

    ReplyDelete
    Replies
    1. Hi!

      I don't know what could change for your PI. In my Raspberry PI model B rev2 and model A rev2 sudo halt turns off the PI. I have never seen a reboot instead.

      Delete
    2. thanks for your response; I'll think on hardward cause; but I always could turn off my Pi and after change of kernel I can't do it more.

      Delete
  37. Hi Andrei,
    I've downloaded your kernel and replace file /boot/kernel.img and /lib/firmware and /lib/modules/ on the SD card. I plug the SD card on my laptop and replaced them.But after reboot the touchscreen still not working. My raspberry image is 2013-02-09-wheezy-raspbian.img and using 7 inch AT070TN94 touch LCD panel. What's wrong with my step?

    ReplyDelete
    Replies
    1. If you have upgraded your OS, the kernel should be newer than 3.6.11.
      The kernel image here is for 3.6.11.

      Delete
    2. oops I was working with the other side of panel - idiot proof :) now the touch panel is working

      Delete
  38. With this command "sudo make modules_install ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- INSTALL_MOD_PATH=../modules/"

    My result is :

    scripts/kconfig/conf --silentoldconfig Kconfig
    ***
    *** Configuration file ".config" not found!
    ***
    *** Please run some configurator (e.g. "make oldconfig" or
    *** "make menuconfig" or "make xconfig").
    ***
    make[2]: *** [silentoldconfig] Erreur 1
    make[1]: *** [silentoldconfig] Erreur 2

    The present kernel configuration has modules disabled.
    Type 'make config' and enable loadable module support.
    Then build a kernel with module support enabled.

    make: *** [modules_install] Erreur 1

    however, when i configured the kernel with "make O=../kernel/ ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- xconfig", Enable loadable module support were ticked.

    Where I was wrong ?

    ReplyDelete
    Replies
    1. hi, i also encounter the same problem but then i follow the instruction from helio at his first comment above - thanks helio

      Delete
    2. Hi!

      Sorry, it is my mistake, you should execute that command from the ../kernel/ folder.

      Andrei

      Delete
  39. Hi Andrei,

    How to perform single click to launch default action since i have to use double click. Also how to simulate right click action?

    ReplyDelete
    Replies
    1. Hi!

      If you are using my build, with no other modification you should be able to use single. Regarding right click, I haven't got time for this.

      Regards,
      Andrei

      Delete
  40. This comment has been removed by the author.

    ReplyDelete
  41. Thanks to my father who told me about thjis
    weblog, this website is genuinely amazing.

    My web page :: Real Estate

    ReplyDelete
  42. Hello, thanks for the great info...
    Just thought I would share my experience, I had a NOOBS card come with my Model B Pi so used that to run up Raspbian, used your files rather than build my own, they seemed to work fine as the display came up fine after some work and the touch screen worked but really needed calibrating, this is where the big issues started.
    I could not compile the calibration software, mucked about for ages and gave up.
    Installed a vanilla Rasbian on another card, and compiled the calibration software on that, copied the folder to the other card and installed it, it ran fine and I now have a working touch screen.

    Thanks for supplying this info, its been a great help..

    Cheers,

    David... BD

    ReplyDelete
  43. WIll this work on this touch panel?

    http://www.ebay.com/itm/HDMI-input-LCD-controller-board-7inch-800x480-AT070TN92-lcd-with-touch-panel/360811533124?_trksid=p2047675.c100011.m1850&_trkparms=aid%3D222006%26algo%3DSIC.FITP%26ao%3D1%26asc%3D19852%26meid%3D4741517119939926677%26pid%3D100011%26prg%3D8938%26rk%3D1%26rkt%3D10%26sd%3D170937641798

    ReplyDelete
    Replies
    1. All the CarPC tutorials from this blog will work with your touch panel(eGalax)

      Delete
    2. I assume your simply saying yes, I hope it is.

      Delete
  44. Andrei, I want to thank you for you posts. I am a complete NOOB with programming, but am slowly learning by reading your posts. I have a RPi and the eGalax touchscreen 7" monitor. Using your image file that included the xbmc program I was able to get the touchscreen to work. To calibrate it, I used the calibrate tool in X. I noticed that after doing it the first time it didn't get any better. Doing it a second time however resulted in values: 1965 49 198 1903 and no axis flip. This worked great! Very accurate when used in X. It always requires doing twice. When I launched XBMC however, no touch feature. I'm ok with that for now since I wasn't planning on using it.

    Where I'm getting stuck as a beginner is how to get the calibration settings to stick. Every time I leave X and come back, they are gone. I created /etc/x11/xorg.conf.d/99-Calibration.conf and put in the lines of information with my calibration, but nothing.......

    Now, I'm trying a simple Rasbian build and will copy your kernel image and the lib/modules and lib/firmware files. I tried this once before and messed something up and couldn't boot. After I do this, is the calibration file already in place and I simply edit the values? Or must I do this:
    sudo apt-get install libx11-dev libxext-dev libxi-dev x11proto-input-dev when I tried doing this before it said no such file.....

    Sorry for the questions. To be honest I am only learning this so that I can install my RPi into my car. I have a 1981 Delorean (Back to the Future car) and wish to use the touchscreen as a way of controlling windows, door locks and some auxiliary lighting. I've already found how to control my relays using a python program. The real challenge for me (and if someone wants to help I'd love it) will be to develop a GUI that uses an image of the car with a few button/switches to activate those relays. Wiring it to the car is the easy part for me! It's the programming which is too structured for my old brain. I've seen some neat stuff with Java on the Pi. I would love that......

    Anyway, I'm still plugging away, but any hints or suggestions are appreciated. Keep up the good work!
    Owen.

    ReplyDelete
  45. OK, I'm doing something wrong... how does one "replace" the image files and the lib/mod, lib/fimware? Simply replace the files while using the file manager? Or do I have to run the disk imager? Time for a break and a beer....

    ReplyDelete
    Replies
    1. Hi Owen!

      Great project you are working on :)

      The xinput-calibrator output is confusing. It says that you have to create the file
      /etc/X11/xorg.conf.d/99-calibration.conf
      In fact(at least in Raspbian), you have to create the file:
      /usr/share/X11/xorg.conf.d/01-input.conf

      In my builds I have the touch screen calibrated and x11 stuff and xinput-calibrator installed and also the file 01-input.conf in /usr/share/X11/xorg.conf.d/. You just have to replace it with yours.

      Now, for replacing the files i am using a linux pc and a card reader. First, I delete the folders /lib/firmware and /lib/modules and after this I copy the new ones. You have to wait until the disk is successfully unmounted, to be sure that the whole data was copied(even if the copy dialog window is done).

      Regarding the GUI, I have chosen XBMC because it has a very good looking interface and it is very easy to use. Also, you find a lot of documentation on the internet. Just get the simplest addon(rpcalendar for example) and modify it as you wish.

      Andrei

      Delete
  46. Thanks Andrei, nice to "meet" you. I will dig into this again. I've also been trying your most recent car PC releases, but to be honest I won't need all that entertainment stuff you're doing. I may work my way up to it though! I don't have a linux px, only windows. I tried replacing those file while I was running on my Pi. That's probably the problem. I may have to learn some more and put a linux partition on my PC... or maybe it would be simpler to use Pi and just make the edits to another SD card rather than the live one. Readers are cheap......
    Thanks, I'll keep plugging away. If you or any of your followers should know of a good simple, editable GUI that I could grab, that would be great! I just want something like the Tesla has; a photo of the car with a few soft switches that I can hook to GPIOs. Thanks
    Owen.

    ReplyDelete
    Replies
    1. Nice to meet you too!
      Maybe you can use python with some photos for buttons.
      QT is another option but is a little bit more sophisticated.
      Good luck and please let me know how it goes :-)

      Delete
  47. Andrei,
    Excellent work! I, too, had an axis problem (mine was only one axis was inverted). I found a simple and easy/elegant solution to a one axis inverted problem: OPTION "InvertY" "1" (or x, or both)
    So your code would look like this:
    --> Making the calibration permanent <--
    copy the snippet below into '/etc/X11/xorg.conf.d/99-calibration.conf'
    Section "InputClass"
    Identifier "calibration"
    MatchProduct "eGalax Inc. USB TouchController"
    Option "Calibration" "121 1917 317 1741"
    Option "InvertY" "1" <------- Use InvertY or InvertX, simple and easy
    EndSection

    Thanks again for all your hard work,
    Scott

    ReplyDelete
  48. Nice instructions - it works! Nice touch to included your recompiled kernel, thanks. Latest one is newer but it still seems to work.

    ReplyDelete
  49. Thank you for the tutorial. My touchscreen works great now. But I have another issue.
    My pi will no longer turn off. All turn off icons are gone and the root terminal will not open. Also, any commands containing "sudo" generates an error message which says "sudo: effective uid is not 0, is sudo installed setuid root?"

    Any ideas?

    I have tried changing the permission for sudo.

    ReplyDelete
    Replies
    1. Hmm, this looks strange.
      I will soon post a new image, with latest firmware, kernel and xbmc. Please keep an eye on this blog.

      Delete
    2. I'm pretty sure it's my fault. I changed the ownership of the files in order to get access to the data on the pi's sd card.

      Delete
  50. I am very amazed by the information of this blog and i am glad i had a look over the blog. thank you so much for sharing Copy machine touch screen such great information.

    ReplyDelete
  51. Hi There,

    I would really like to know how to calibrate the touchscreen for XBMC, I have a Raspbian setup with a Newly compiled XBMC that I have installed, the touch screen works great with your settings above, but now when I run xbmc one axes are swapped, and it's not calibrated right, I have tried every google search I've found but nothing works, I have changed the values to see if it makes any difference but not even a bit. any Ideas please. Sorry that I ask the question on this thread.

    ReplyDelete
  52. I have used this tutorial and it gets the screen to work but it seems that there is some problem. The cursor stays in one spot and when screen is touched or mouse is moved the cursor move a little bit and then jumps back to its original spot as if someone was holding their finger there. any suggestions?

    ReplyDelete
  53. Hi. Fantastic job. I did not anticipate this. This is a great story. If you find same related blog or Konica transfer belt assembly just visit today. and get more good quality printing.

    ReplyDelete
  54. My struggles continue (lack of programming knowledge...) I have downloaded your new Kernel 3.10.30 but the modules don't seem to be downloadable from the Google drive. I have the older ones that came with 3.6.11 kernel. Can they be used?

    I only have a pi running linux. Not on my windows machine. Is there a procedure to replace these modules on a running pi? Sorry for the very elementary questions, but I can't really even learn more about my pi and experiment until I get the monitor/touchscreen up and running! Is there a step by step tutorial somewhere? I'm also surprised that a complete image cannot be made that includes everything (kernel, libraries, etc...) that can simply be extracted and burned onto a SD. Maybe there is and I just don't know it? Thanks.

    ReplyDelete
  55. Nice article and thanks for sharing your knowledge. I really appropriate your views. If you find same related blog or Konica transfer belt assembly just visit today.

    ReplyDelete
  56. Hi Andrei,

    Thanks heaps for this great tutorial, I've never used Linux before and this was easy to follow and get working...almost. I've followed your steps all the way until the last step where I had to create the new file and add the output from the xinput_calibrator into it. My output didn't have:

    MatchProduct "eGalax Inc. USB TouchController"

    But rather:

    MatchProduct "Logitech USB Keyboard"

    Which is probably a result of me using a USB hub with my mouse, keyboard and the touchscreen connected. So now when I startup the Pi, it hangs on a terminal screen with just a blinking cursor and I can't input anything into the device. Would you suggest I just reimage my SD card and start over again, this time plugging my touchscreen directly into the Pi before running xinput_calibrator?

    Thanks for any assistance.

    Alex

    ReplyDelete
    Replies
    1. Hi Alex,

      If you want to use xbmc, then this calibration is not needed, you can calibrate only in XBMC and it should work.
      If you don't want to use xbmc then you should do this calibration also. I will sugest you to try the calibration with the touch directly connected to the PI. I don't know why it could not work via hub.

      Delete
  57. Hello, thanks fort the tuto but my driver board is not seen by any of my computer when I type lsusb the board is not listed. What thats mean, you think the board is broken ? Thanks

    ReplyDelete
    Replies
    1. Hi, what is the output of dmesg? Please send me an email.

      Delete
  58. Hi !
    Nice turorial !
    I've downloaded the latest raspian, but i'm thinking that is not the same kernel version than your modules.
    So my touch panel doesn't work on the raspberry, and when I copy the files to the sd card the mouse doesn't work .
    My question is : is it possible to use the modules with the latest raspbian version and if yes how to do it?
    Many thanks
    Alexis

    ReplyDelete
    Replies
    1. Hi,
      You need to copy /lib/firmware and /lib/modules and also kernel.img if you want to use another kernel.
      Please download my latest image and test again.

      Delete
  59. Hi Andrei,
    The image posted by you is more than 1 year old. It would be great if you can post an image compiled on latest kernel. Thanks

    ReplyDelete
    Replies
    1. Hi,
      Please have a look at my downloads page, on the top right of my blog and you will get the latest image with latest kernel and also xbmc 13.1.

      Delete
  60. Hi Andrei,
    Nice work! - Finally reached Germany! =)

    I'm trying to conect two 10" LCD displays (HDMI & VGA) and matching touchcontroller (usb) in portrait mode!
    It should end up like an dual screen tablet pc.
    First at all... Is it possible? Because it seems like every step i make is messing up the step befor and the Banana PI is not understanding yet, that there are 2 touchcontroller!
    You're quite expierenced - could you list up the order and commands i need to finish my project!

    Thank you in advance

    Regards
    Tyrone

    ReplyDelete
  61. I have an appreciation for those smarter than me in all of this RPi stuff. I have a simple request that I hope you Andrei (or someone else) can help me with.
    I have the eGalax touch screen monitor. I am not interested in the whole xbmc setup and all the other nice stuff you have done. I have another project in mind for my RPi, but I need the touchscreen working. I am NOT at all experienced in Linux.

    Would it be possible to post a full SD image that I can burn onto my SD and have nothing but a standard Raspian operating system with the new touch screen drivers already compiled into it? To be honest, I am not smart enough or knowledgeable enough about the file system to be swapping directories or making changes. I DO know how to load full images however!

    Your work on this is very impressive and searching the internet I know there are lots of eGalax customers having the same problem as me. Your media center work is way ahead of what I need right now, but I would certainly appreciate just the eGalax piece so that I can get this touch screen working.

    I really appreciate it!
    Owen.

    ReplyDelete
  62. Hey everyone. I am building my own kernel however I'm running into a block.

    When I am at the kernel configuration I navigate to device drivers->input device support and I do not have any touch screen options. All I see is hardware I/O ports. Any advice?

    Thanks

    ReplyDelete
    Replies
    1. Select 'Input device support/generic input layer/USB Touchscreen Drivers' and you will find the one and only eGalax-Driver (eGalax, eTurboTouch CT-410/510/700 device support), but I'm not sure that this driver is correct.

      Delete
  63. sorry if this is a double post
    I installed the kernel and it worked fine but my digital gpio thermometers no longer work.
    the sudo modprobe w1-gpio and sudo modprobe w1-therm don't work. HELP!

    ReplyDelete
    Replies
    1. This sounds like these modules are not enabled. Please use the kernel build tutorial to build yours.

      Delete
  64. Hey, thanks for the tutorial.

    I have chosen the easy way - I downloaded the latest image onto my Model B. Unfortunately the whole thing starts and I can SSH into it but I get no video output via HDMI or RCA.

    Any ideas for me?

    Thanks!

    Andrew

    ReplyDelete
    Replies
    1. Hi Andrew,
      You need to change your monitor settings. Just play with /boot/config.txt options(http://elinux.org/RPiconfig).
      Please use my latest post(http://engineering-diy.blogspot.ro/2014/04/raspberry-pi-carpc-april-2014-updates.html) and look at the "Change the resolution" part.

      Delete
  65. Hi

    I love your project. I have downloaded your latest image and I am having trouble with the XBMC touch. I tried calibrating it but I can’t see the bottom two circles to press. I guess your settings are for 1200 and my screen is 800 by 600. After completing the calibration on XBMC the cursor and XBMC just freezes until I reboot. Can you please help?

    ReplyDelete
  66. Hi again,

    I managed to change the XBMC resolution but the problem I face now is that my settings on the desktop for the touch keep on changing as in they are not permanent. Infact they never stay permanent for the desktop, X11 and XBMC. Can you help please? Also when I do manage to calibrate and get the temporary settings even though I save in the sudo nano /usr/share/X11/xorg.conf.d/01-input.conf file I notice that I can’t touch the very right or left bottom of my screen like if i want to press the little arrow or “Start” button on the bottom left, the cursor does not go there. Can you please help.

    ReplyDelete
  67. Andrei

    I am having difficulties with XBMC it freezes please help

    ReplyDelete