debian 5 lcd touch screen drivers factory

After execution, the driver will be installed. The system will automatically restart, and the display screen will rotate 90 degrees to display and touch normally.

debian 5 lcd touch screen drivers factory

Raspberry Pi leads out 40 GPIO pins, while the screen leads out 26 pins. When connecting, pay attention to the corresponding pins and Raspberry Pi pins.

5) Insert the TF card into the Raspberry Pi, power on the Raspberry Pi, and wait for more than 10 seconds to display normally. But the touch is abnormal at that time, and the touch needs to be calibrated as the following steps.

3. After reboot, the touch will work normally under normal circumstances. But for different resistance screens, the accuracy of using the default calibration parameters may not be very suitable.

You can perform touch calibration by clicking the Raspberry Pi icon on the taskbar, selecting Preferences -> Calibrate Touchscreen, and following the displayed prompts.

4. After calibration, the following data will be displayed. If you want to save these touch values, you can replace the data in the red circle with the data in the corresponding position in 99-calibration.conf.

The installation of xserver-xorg-input-evdev and xinput-calibrator in Ubuntu system reports an error, so the touch cannot be used normally. How to solve it?

The installation of xserver-xorg-input-evdev and xinput-calibrator in Kali system reports an error, so the touch cannot be used normally. How to solve it?

debian 5 lcd touch screen drivers factory

5) After the programming is completed, open the config.txt file in the root directory of the TF card, add the following code at the end of config.txt, save and eject the TF card safely.

6) Power on the Raspberry Pi and wait for a few seconds until the LCD displays normally. And the touch function can also work after the system starts.

At the end of the config.txt file, add the following commands corresponding to disabling touch (the config file is located in the root directory of the TF card, and can also be accessed through the command: sudo nano /boot/config.txt):

debian 5 lcd touch screen drivers factory

Thanks for bringing this to my attention. It appears that the upgrade package overwrites the FBTFT drivers, in particular, the Raspberry Pi bootloader. This seems to solve the problem:

dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p6 rootfstype=ext4 elevator=deadline rootwait fbtft_device.custom fbtft_device.name=waveshare32b fbtft_device.gpios=dc:22,reset:27 fbtft_device.bgr=1 fbtft_device.speed=48000000 fbcon=map:10 fbcon=font:ProFont6x11 logo.nologo dma.dmachans=0x7f35 console=tty1 consoleblank=0 fbtft_device.fps=50 fbtft_device.rotate=0

Hello..I tired to interface this lcd “https://www.crazypi.com/raspberry-pi-products/Raspberry-Pi-Accessories/32-TOUCH-DISPLAY-RASPBERRY-PI” to my Raspberry pi model B+.I got a DVD containing image for LCD in the package.I burned it to the SD card and plugged in the display.But my lcd is completly blank.But green inidcation led (ACT LED) in board is blinking.Why my LCD is Blank ?

If you have tried using the manufacturers image and the screen doesn’t work, it could be that the screen has a hardware malfunction. If the process above doesn’t work either, I would contact the manufacturer

Is your RED (POWER) LED on? I had the same problem. Green Led was blinking and screen was white. Then I noticed RED Led is off, indicating there’s something wrong with the power. I plugged into different port and it started

Yes, it may be that the screen isn’t supported. Newer screens might not have drivers yet. I do know it is possible to make your own driver but that’s above my level of knowledge :)

My Touchscreen is now working fine.The problem was for the ribbon cable on the back side of LCD.It was not connected properly.I just tighted the cable and it worked fine.Hope it will be useful tip.

Thank you for this great tutorial. I looked everywhere for this information. I have an eleduino 3.5 version A. I was able to get it working on my Pi 2 by following your tutorial and using flexfb as the screen type. I got the other settings from the image that came with the product. I did find that the ts_calibrate didn’t recognize the screen so I installed xinput-calibrator and it worked fine.

What other settings are you speaking of? Where are they on the image? I’m also using the Eleduino 3.5, but I’m not sure which letter version it is. It says version 141226 on the back, and it’s a black PCB.

Just got my Pi2 running Wheezy, working with the Eleduino 3.5 LCD without running the OEMs image… kinda. I didn’t want to rebuild the application environment again, so was avoiding flashing the SD.

I tried the steps in this tutorial. It’s very clear and easy to follow, thank you. But it didn’t work for me, I tried setting my device to flexfb. Only got white screen.

[ 0.000000] Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2709.boardrev=0xa21041 bcm2709.serial=0x631a4eae smsc95xx.macaddr=B8:27:EB:1A:4E:AE bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=250000000 vc_mem.mem_base=0x3dc00000 vc_mem.mem_size=0x3f000000 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait fbtft_device.custom fbtft_device.name=flexfb fbtft_device.gpios=dc:22,reset:27 fbtft_device.bgr=1 fbtft_device.speed=48000000 fbcon=map:10 fbcon=font:ProFont6x11 logo.nologo dma.dmachans=0x7f35 console=tty1 consoleblank=0 fbtft_device.fps=50 fbtft_device.rotate=0

thank you for your great tutorial, it got me on the right way. unfortunataly i only see some boot messages on the lcd and then it turns black. maybe you could give me a hint on how to get it working entirely.

Did you check to see if your device is supported yet? The device name should be specific for your screen, as listed in the fbtft file linked to in the beginning of the post

I too have a raspberry pi 2, and a waveshare spotpear 3.2 RPi lcd (v3) and I just can’t get it to work! I suspect I have a faulty LCD, but thought I’ll try this forum for help before I sent it back.

Soon as the pi is powered, the LCD lights up all white, with a few vertical pixels coloured at one of the edges, and nothing else. I don’t think that should happen – not at least before the BOIS has started up.

Any ideas what going wrong? I am using the latest “2015-02-16-raspbian-wheezy_zip”. Enabled SPI. done all the steps. Even changed mmcblk0p2 to mmcblk0p6 as suggested by Dabomber60 (but that freezes for me)

[ 0.000000] Linux version 3.18.5-v7+ (pi@raspi2) (gcc version 4.8.3 20140106 (prerelease) (crosstool-NG linaro-1.13.1-4.8-2014.01 – Linaro GCC 2013.11) ) #1 SMP PREEMPT Fri Feb 6 23:06:57 CET 2015

It seems all appears to be working – just the LCD is still all white with a single line of coloured pixels on edge) and nothing else. Is there a way to output, like jeff G script, of touch points?

I had the same one, I finally found a driver for it here: http://www.waveshare.net/wiki/3.2inch_RPi_LCD_(B) you will need to translate the page, but unpack the driver then run sudo ./LCD-show/LCD32-show. It should reboot and all will be good with the screen :)

Can anyone let me know if the default OS image sent with the screen works with pi2 or just Pi B/B+ as i think my screen maybe broken but can’t confirm it yet as i have not had it working at all

My system: Raspberry Pi 2 Model B with Raspian Wheezy from Febuary 2015. LCD display of Sainsmart 3.2 http://www.conrad.de/ce/de/product/1283498/Raspberry-Pi-Display-Modul-Touch-Display-81-cm-32/?ref=home&rt=home&rb=1

dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 cgroup_enable=memory elevator=deadline rootwait fbtft_device.custom fbtft_device.name=sainsmart32_spi fbtft_device.gpios=dc:24,reset:25 fbtft_device.bgr=1 fbtft_device.speed=48000000 fbcon=map:10 fbcon=font:ProFont6x11 logo.nologo dma.dmachans=0x7f35 console=tty1 consoleblank=0 fbtft_device.fps=50 fbtft_device.rotate=90

sainsmart32_spi width=320 height=240 buswidth=8 init=-1,0xCB,0x39,0x2C,0x00,0x34,0x02,-1,0xCF,0x00,0XC1,0X30,-1,0xE8,0x85,0x00,0x78,-1,0xEA,0x00,0x00,-1,0xED,0x64,0x03,0X12,0X81,-1,0xF7,0x20,-1,0xC0,0x23,-1,0xC1,0x10,-1,0xC5,0x3e,0x28,-1,0xC7,0x86,-1,0×36,0x28,-1,0x3A,0x55,-1,0xB1,0x00,0x18,-1,0xB6,0x08,0x82,0x27,-1,0xF2,0x00,-1,0×26,0x01,-1,0xE0,0x0F,0x31,0x2B,0x0C,0x0E,0x08,0x4E,0xF1,0x37,0x07,0x10,0x03,0x0E,0x09,0x00,-1,0XE1,0x00,0x0E,0x14,0x03,0x11,0x07,0x31,0xC1,0x48,0x08,0x0F,0x0C,0x31,0x36,0x0F,-1,0×11,-2,120,-1,0×29,-1,0x2c,-3

ads7846_device model=7846 cs=1 gpio_pendown=23 speed=2000000 keep_vref_on=1 swap_xy=1 pressure_max=255 x_plate_ohms=60 x_min=300 x_max=3800 y_min=700 y_max=3400

The LCD display shows the raspberry correctly. However, the touch screen input does not work. The mouse pointer can I move correctly with your finger, but I can not select things (function of the left mouse button).

Thank you so much for this great tutorial. I have my WaveShare SpotPear 3.2″ V4 working fine on my Raspberry Pi 2. If you are having problems with this specific hardware, skip step 5.

Can someone upload SD card image that works with RBP2 ? My idea is to use Eleduino TFT as additional screen and play movies via HDMI.. is it possible?

Do not follow this article when you don’t know what kind of LCD module. In my case, I follow all of this and my raspberry pi cannot boot anymore. I will try to recover, but I think I should format my SD card and reinstall OS.

Expecting this would builtin driver module within kernel and help with avoiding mistakenly overwriting anything. But with this is cause LCD screen to go blank white and no boot activity. Also noticed on HDMI it get stuck on Initial rainbow screen and stuck on that.

Does anyone tried splash boot screen with waveshare v4 LCD and Rpi2? I tried to follow some example from https://github.com/notro/fbtft/wiki/Bootsplash but no success.

Great tutorial thanks; got an X session working great 1st time. Has anybody managed to get Kodi/XMBC working on the LCD either Kodi standalone, Raspbmc or Xbian?

fbtft_device name=waveshare32b gpios=dc:22,reset:27 speed=48000000 width=320 height=240 buswidth=8 init=-1,0xCB,0x39,0x2C,0x00,0x34,0x02,-1,0xCF,0x00,0XC1,0X30,-1,0xE8,0x85,0x00,0x78,-1,0xEA,0x00,0x00,-1,0xED,0x64,0x03,0X12,0X81,-1,0xF7,0x20,-1,0xC0,0x23,-1,0xC1,0x10,-1,0xC5,0x3e,0x28,-1,0xC7,0x86,-1,0×36,0x28,-1,0x3A,0x55,-1,0xB1,0x00,0x18,-1,0xB6,0x08,0x82,0x27,-1,0xF2,0x00,-1,0×26,0x01,-1,0xE0,0x0F,0x31,0x2B,0x0C,0x0E,0x08,0x4E,0xF1,0x37,0x07,0x10,0x03,0x0E,0x09,0x00,-1,0XE1,0x00,0x0E,0x14,0x03,0x11,0x07,0x31,0xC1,0x48,0x08,0x0F,0x0C,0x31,0x36,0x0F,-1,0×11,-2,120,-1,0×29,-1,0x2c,-3

ads7846_device model=7846 cs=1 gpio_pendown=17 speed=1000000 keep_vref_on=1 swap_xy=0 pressure_max=255 x_plate_ohms=60 x_min=200 x_max=3900 y_min=200 y_max=3900

After following this tut to the letter on a brand new image of Raspian, I find that the touch driver does not function. Anyone experience the same? Basically all I did was image a current copy of rasping, did a apt-get upgrade, and then did this tutorial. Then the touch driver does not work, meaning the pointer does not respond.

The reason I did this was because on a production version of my system I added the 3.2 screen and it worked great except for the x-axis. So I wanted to see if there was something in my system that was interfering or if this is another error. Now with a raw rasping the driver does not work at all. I wonder if the touch pin has changed since the kernel is using BCM pins instead of GPIO pin numbers?

I have exactly the same problem. I also installed a new version of Raspbian, and the LCD part works fine (except all the windows are way too large), but the touch part doesn’t work at all… I’m using Waveshare Spotpear 3.2″ V4.

I remember that I plugged in the screen wrongly one time, before configuring any of the GPIO pins. Can this have damaged the screen? Still it’s weird that the display part works well and the touch part not at all.

Touch actually goes through one of the SPI pins I think. Either the driver is toast with the required kernel update or the driver is using the wrong pin. It is very likely the this works well with previous raspian versions, but not with the new B+ and with the new kernel.

I am trying to use the sainsmart 2.8″ lcd sold through microcenter, using the sainsmart32_spi … seems to have the same pinouts, should I be able to get this to work? I am stuck at the white out screen on the lcd, doesn’t seem to recognize the module either.

Unfortunately I’ve tried that ( a few times actually) but the file still doesn’t exist. Thanks very much for the assistance anyway. I must be doing something wrong. My Raspian came from a Noobs installation, I’m wondering if I should try installing the OS from somewhere else. My LCD screen didn’t come with a CD or any docs so I’m completely in the dark here.

I have just found a way to get this file on my system! Apparently its part of the fbturbo installation. I found it here http://www.raspberrypi.org/forums/viewtopic.php?f=63&t=45746&start=75 (under experimental enhanced x driver (rpifb).. Sorry if this is obvious to everyone but I am SUCH a noob at this!!

I have the waveshare 3.5 and what to use it only as a secondary screen by putting measurement data with a c program on the screen. Is there any solution?

Ok, what am I doing wrong. I am using a fresh install of the newest raspbian, on a Pi 2. After doing the first two steps and rebooting I get the rainbow screen, then the boot up process, and then my screen just goes black with a flashing cursor in the top left. I am not able to enter any commands or anything…like the pi is halting just after boot up. Any thoughts/suggestions would be greatly appreciated. Thanks.

Well figured out that step 1 was causing my problems. I’m guessing it is shutting off my hdmi feed and trying to switch it over to the SPI, am I guessing right? If so, not sure how I’m suppose to complete the rest of the steps if my hdmi output gets turned off before the LCD is actually set up to work…that sounds kind of smartass-like, which is not my intention, just looking for some clarification on what is going on in that first step as I am fairly new to this stuff. Thanks.

Anyway, I was able to do the rest of the steps with no problem. LCD didn’t work, but I am using a Waveshare 3.5, which doesn’t look to be supported yet. Mostly I am trying to play around and see if I can get it working somehow. Anyone found a way to do this yet?

Here is a link to an updated image from waveshare. Upon install it got the display up and running, but I still do not have touch functionality. I’ve been playing around with it, but it has been to no avail…hopefully someone better at this stuff from me can get the touch working.

I am having an issue with getting the GUI back. Every time I use startx my pi just sits there for about two minutes saying “No protocol specified”, and then it just gives up. I went through this tutorial about four times now and am not certain why it is doing this. I have the exact same LCD as is in the tutotial (WaveShare 3.2b). any help would be great.

Hi I am making a project for school,using the raspberry pi b+ and waveshare spotpare 3.2b. Everything works except the touch input doesn’t work. Any help would be appreciated very much.

Thanks for the tutorial. It works, but I get the boot/command line stuff on the HDMI monitor and the LCD only comes on when I do startx. Is there a way to get everything to appear on the LCD screen?

I am trying to get this same screen to work with the image of RetroPie 2.6 and it won’t work. I have followed all the steps and nothing, please help I an kinda a noob.

I have a Tontec 7 inch touchscreen with a Raspberry Pi 2 B. After following the instructions the touch screen is functioning but not properly… The only are that works is the upper left (and only a small area of that). I tried changing the width and height in the modules but it didnt change anything. Also the xy seems to be reversed, I changed the swap_xy to 1 but again no change on the screen.

Now the OS freezes at the emulation station loading screen, and if I connect my lcd it gives me a lot of error messages which I can only see on the 3.2 inch screen.

hi i have the same screen with a raspberry pi 2 im trying to run retro pie but it wont show ..however it shows all the commands …but i cant get it to show the gui …if u guys can make an image or something please i have been in this pain for two weeks already thank you

well ,,i follow all instructions and still kernel panic ,,,,may i request from mr. Circuitbasics@Gmail.Com that have a contact with manufacture and just ask for 2-3 links for image files for different versions of pi till all this f discussions are finished,,i cant understand 10 guys said we run it and 40 guys said kernel panic ,,as an expert i did 50 times imaging and follow all changes fro this forum and other forums and still cant run it ,,,so sth is wrong …..just asking the manufacture for simple f image ,,that`s it ,,,,simpleeeeeeeeeeeeeeeee

well i did it at last on pi 2,,after reading 100 pages and reimaging 50 times ,,i finally find the solution ,,,,there is a simple line forgotten to be attached in setup instruction,,,well i give u clue for prodigies ,,there is a step left between step 3 and 4,,,,and a simple change in step 5 according to your pi version ,,,that`s it ,,nothing else,,,,

Damn.. I thought I was kickin ass haha. I am using the SainSmart 3.2″.. the backlight is lit up and the pi was booting and everything just fine but on the final reboot it gets hung and says “nonblocking pool is initialized” ?? No idea what that means. But it’s def just frozen at this point.. on my main screen, and just the backlight is on the SainSmart.

This was an excellent tutorial. I have gotten an output to the screen, but no touchscreen usage . I have the Waveshare SpotPear 3.2 Inch LCD V4 screen, but using Raspberry PI 2 with wheezy. Any ideas?

Thanks a lot for this article. Very clear and easy . I am new in pi’s world and my 3.2″ screen is working fine. I rotate 90 º and works. I can use mouse and so on.Not problems.

I filed the steps to calibrate the screen but it did not work.I think because it did not find the TFT pin, because I think the touch problem is the assigned pin to control it changed.

I actually used the driver from here http://www.waveshare.com/wiki/3.2inch_RPi_LCD_(B) , from a new wheezy build, did nothing except enable SPI in config, install driver, and change mmcblk0p2 to mmcblk0p6 in cmdline.txt and it all worked, no drama.

Hi I managed to set up my touch screen ok but I now have the issue that everything desktop fits fine but the windows I open are all huge and I can’t remember how to change the size and cannot see the option in desktop preferences any idea what I have to do and is it at all possible to install kodi to run through the raspbian is as this would be a lot my useful than having to keep swapping os on every boot up many thanks in advanced hope you can help me

Hi, sorry I’m a REAL noob… I can’t manage changing 99-fbturbo.conf at the first step (fb0 to fb1), because the file is in read only mode (Raspbian july 2015). I can’t manage getting rights to change… Any idea? Thanks.

Advice to all who have the drivers from the (touch)screen manufacturer and cannot obtain those otherwise: you can skip everything and go to the update steps skipping the kernel and kernel modules update (as mentioned by the author) so that you don’t override the preinstalled drivers. I have a Waveshare 3.5″ RPi v3 (not the 3.2″ supported by notro’s drivers) and actually managed without any problems to get notro’s drivers make it work. However I am still reading about the xinput and xinput-calibrator to figure out how to include it as a kernel module so that I can compile my own kernel and add it there.

i have raspberry pi 2 with 3.2 inch rpi lcd v4 waveshare spotpear.i have done as per your instructions.the display is working but touch screen not working.error shows waveshare32b module not found as well as touch screen module not found messages.

Unfortunately I have lost the Touch facility on my Waveshare 3.5″ LCD Touchscreen? Can you offer any reasons as to why? I copied the Raspbian image to my Raspberry Pi from the Waveshare website first of all. The Touchscreen displays but is not reactive with any touch

Hi great article thanks. I am trying to get a waveshare 7 inch LCD with capacitive touch running it works with the suppled image but if you upgrade it breaks the capacitive touch. I have a sense-hat and GPS which require the latest kernel and RASPIAN image and the install program for the screen replaces the /lib/modules directory and the kernel with older ones. I need to be able to install the touch drivers into a new clean OS can anyone give me some pointers? Thanks

I should add that the screen is plugged into the HDMI port and always works. The capacitive touch is driven from the USB port which also supplies power.

For anyone who have those unbranded cheap TFT touch modules and cannot get it to work with this guide, I had success on my 3.5″ with the following steps: http://pastebin.com/89qmFbPB

I have the WaveShare 3.5 (A) and cannot get it to work with the Kali Linux with TFT for Raspberry Pi. Have anybody gotten the A to work? (Not the B, theres instructions for the B already and dont work with A)

So I have the original image that came with my screen and it works fine with the LCD but my problem is that I want to use my LCD screen with other distros (at this time I am trying to use it with Kali Linux with TFT support by default https://www.offensive-security.com/kali-linux-vmware-arm-image-download/) What do I have to do to transfer the needed files from the original image that WORKS with the screen and use them with another image?

I originally bought this bundle http://www.amazon.com/gp/product/B013E0IJUK?psc=1&redirect=true&ref_=oh_aui_detailpage_o02_s00 with an RPi LCD V3 and no extra documentation on the specifics on the chipset. I tried with the bftft drivers but since I have no idea what to call this screen I just suppose it isn’t supported.

After 4 lost days I just decided to get another screen, a Waveshare 3.2 (just like the one on this tutorial), I’ll follow these steps and see if it work for me.

I’ve followed your instructions and am only getting a white screen stil. I am using the Osoyoo 3.5 inch touchscreen from Amazon. http://www.amazon.com/gp/product/B013E0IJVE?psc=1&redirect=true&ref_=oh_aui_detailpage_o01_s00

I’m not sure if the Jessie kernel is compatible – can anyone please confirm or not ?? Adafruit states that their setup for TFT screens are Wheezy only ; is this a different setup ??

I am using the same LCD and followed your tutorial. Have your tested the guide lately? Are you certain that it works? I see the boot messages on console but I get white screen as GUI starts.

Oct 16 17:38:48 spare kernel: [ 12.544859] graphics fb1: fb_ili9340 frame buffer, 320×240, 150 KiB video memory, 4 KiB DMA buffer memory, fps=50, spi0.0 at 48 MHz

After I rebooted in step 3, my raspberry pi won’t boot up again. It goes thru the process of booting and the text scrolls down and every thing says “ok”. Then instead of going to GUI it just guys to a black screen on my monitor with a blinking underscore in the top left corner. Anyway to get around this? or should I start over with a fresh disk image??

That is what happens to mine also.. So long story short —> THIS SITE NEEDS TO BE UPDATED OR SHUT DOWN <— There are a hundred people on here that have all lost everything on the pi drive, and spent all day (or more) working thru this tutorial 4 or 5 (dozen) times and nothing. Just have to reinstall the os over again and again.

I have tried to set up waveshare 32b on my Pi B using the latest Raspian download. I learned a lot in the process using Windows Putty, Nano etc. I have repeated the setup process several times from scratch and included the corrections for possible overwriting. My Waveshare SpotPear 3.2 inch RPi LCD V4 just shows a white screen. Any suggestions?

I’d suggest that you use the included installation disk to make a clean install on another SD card to see if the screen itself works fine or not, then try to repeat the process of installation after upgrading

There was no disk included. I asked for drivers and was given a download link to the image file. After down loading this I tried it and still got just a white screen. The HDMI monitor locks partway though the boot. I can still log in to pi using putty from my PC.

This process worked for me except for two things. The screen only shows 25* of any page so the most important buttons are inaccessible, and now the Wifi does not work and cannot be activated where it worked fine before the reboot. Any suggestions?

Hi, I am using raspberry pi 2 with raspbian jessie installed. I the waveshare spotpear 3.2 v4. The above instructions are not working. and after completing the steps there was no display from hdmi or lcd. One things to notify is.: the etc/modules files only had i2c-dev and not snd-bcm2835.

I am trying to get this to work with Retro Pie 3.3.1 and the Waveshare3.2″ v4 but I only get the terminal on the lcd and emulation station starts on hdmi. to get it working with retro pie i just replaced startx with emulationstation. how do i get this to work?

Sir, Your post has very useful to me. i am using Tinylcd. but i cant get display. i am performing all the steps in your post. i cant get touch controller information from the product website and also i am using RASPberryPi B+ model. could u please give me best solution to my work. Than you.

Hi, what if you dont know the make of your screen, i purchased via Ebay, and it is unbranded, the contact speaks barely any English and keeps linking me to a custom kernal download.

i installed android OS in raspberry pi 2. can i use same LCD touch screen set up for android installed raspberry pi 2 which you are used for raspbian.

Is it normal the white back light during the whole process of initializing (I suspect that during the transportation trere is a deffect)? The problem is that I missed the step #1 and I performed it at the end. Unfortunately I don’t have any monitor available right now – neither “normal”, neither LCD :))))). Is it possible turning back the system or the only option is reinstallation of the Raspbian?

I have KeDei 3.5 inch TFT version 4.0 by Osoyoo. (released after January 1 2016) how do i get it working with vanilla Raspbian Jessie (do not want to install the image sent by the seller)

I’m trying to use an original Raspberry Pi model B with a cheap 3.5 inch 320×480 LCD which allegedly was manufactured to work with the Pi and has the correct fittings to fit over the GPIO pins. The operating system is the latest, downloaded yesterday and installed with NOOBS. I can’t get past step 2 of this guidance. When I reboot after using raspi-config I can see text generated as the Pi boots, then the HDMI fed screen goes blank apart from a flashing cursor in the top left hand corner. The LCD just remains white with nothing else on it. I have missed out step 1 and rebooted after step 2 and the screen functions as I would expect. Does anyone have any ideas please?

Thanks for the great tutorial. I do have a question. Once you install the drivers for the lcd are you effectively disabiling the hdmi port or is it still available to use and will the pi function with both displays. I have a pi 3

once you install the drivers it replaces the kernel by disabling hdmi output and enables it for LCD. i don’t think we have a solution to get em both working at the same time. ( you are encouraged to search for it )

Thanks for the guide, have been doing this with my son but once we leave raspi config and reboot all we get is a black screen with a flashing white horizontal line (dash). Can you help? I have looked in the comments at the end of the article but no one else appears to have this issue.

I have a raspberry pi 2 with waveshare screenn 3.5 inches. Isn’t it the same instructions. But it isnt working, all i get is a white screen, and the red led on the pi is on. The green LED isnot working.

My Rpi3 gets “ERROR: could not insert ‘spi_bcm2708’: No such device” after I enable SPI in the raspi-config.My Rpi3 is freezing on the rainbow screen after I reboot at the end of step 3. I’ve tried adding boot_delay=1 to config.txt.

if any interested, now i have a raspian image working on raspberry 3 with Waveshare 3.5, also with sdr support for dongles and FreqShow working perfectly on touch

I tried following your tutorial but I got stuck right at the first step… I enter sudo nano /usr/share/X11/xorg.conf.d/99-fbturbo.conf the whole screen is blank except for the command list at the bottom…

waveshare32b width=320 height=240 buswidth=8 init=-1,0xCB,0x39,0x2C,0x00,0x34,0x02,-1,0xCF,0x00,0XC1,0X30,-1,0xE8,0x85,0x00,0x78,-1,0xEA,0x00,0x00,-1,0xED,0x64,0x03,0X12,0X81,-1,0xF7,0x20,-1,0xC0,0x23,-1,0xC1,0x10,-1,0xC5,0x3e,0x28,-1,0xC7,0x86,-1,0×36,0x28,-1,0x3A,0x55,-1,0xB1,0x00,0x18,-1,0xB6,0x08,0x82,0x27,-1,0xF2,0x00,-1,0×26,0x01,-1,0xE0,0x0F,0x31,0x2B,0x0C,0x0E,0x08,0x4E,0xF1,0x37,0x07,0x10,0x03,0x0E,0x09,0x00,-1,0XE1,0x00,0x0E,0x14,0x03,0x11,0x07,0x31,0xC1,0x48,0x08,0x0F,0x0C,0x31,0x36,0x0F,-1,0×11,-2,120,-1,0×29,-1,0x2c,-3

ads7846_device model=7846 cs=1 gpio_pendown=17 speed=1000000 keep_vref_on=1 swap_xy=0 pressure_max=255 x_plate_ohms=60 x_min=200 x_max=3900 y_min=200 y_max=3900

I’d like to find the driver software for my 7″ LCD with touch (official Pi unit) so that I can use it in buildroot. I wanted to make sure this kernel is the one before I started digging further.

Every time I reboot after step 3 I get the rainbow screen of death (lost the kernel) and have to reimage my card and start over. Anybody had this happen and have a solution?

I started through your tutorial and completed step 3 and rebooted. After the Raspberry screen and some of the boot text on my HDMI monitor, I now have a black HDMI monitor and a white screen on my LCD. Does this mean that the bootloader was overwritten or something else is wrong? How am I supposed to enter in the proposed fixes to the bootloader, when I can’t get the RPi to boot? Do I have to interrupt the boot process at some point to reinstall the bootloader or what?

Its a script. Download and instead of running sudo ./LCD4-show run cat ./LCD4-show to simply display what it does without actually running it. The commands are fairly simple modifying a few files. I actually saved the LCD-show.tar.gz on my own server for faster future download but also for backup as it saved me tons of hours (if that’s a measuring unit for time :) )

I used this link though (smaller file ~ 50 KB, fast download) http://www.waveshare.com/w/upload/4/4b/LCD-show-161112.tar.gz and replaced LCD4-show with LCD32-show in the last line.

I’m using RasPi Zero with latest (as of last week) Jessie Raspbian. Did you run the script? If it didn’t work and you have modified other files in the process of making it work, I would recommend installing a fresh installed image on a new card and running the script. Can you suspect the screen being faulty or got “burned” in the process?

i bought a 3.5 inch tft lcd screen from banggood. and i have installed raspian jessie, the latest version, in my sd card. but when i power on my Pi, only a white backlit screen comes. there are no images or graphics whatsoever.

Of course. Raspbian Jessie does not come with the drivers needed to talk to the screen. See my previous comment (September 22, 2016 at 11:54 am) and follow it.

I have done every thing right but the only major problem is that the screen is still white and my raspberrypi freezes after a line of code when booting up and I cant get in with SSH

Will your system work with my SainSmart 2.8″ 2.8 inch TFT LCD 240×320 Arduino DUE MEGA2560 R3 Raspberry Pi ? I would like to know before not be able to back out. Thanks, Lee

I know I will end up regretting this, but how do I change fb0 to fb1? I’m on the screen that has all the info, but no way to change it. Am I looking for a file? I have had my screen for MONTHS and I can’t do anything with my pi or the screen. I am >< close to smashing both. COMPLETE WASTE OF MONEY so far!!

hello. I really appreciate your blog post. I have a raspberry pi 3 B. I have been unable to get my waveshare 3.2 screen to work.I am at a complete loss for what to do. I do step 2 I change fb0 to fb1 and then follow your directions I don’t get the prompt to reboot; however, I do it manually with sudo reboot. that works fine then I complete step three and that works just fine; however once I reboot from getting those drivers and when I attempt to reboot it is unsuccessful and then my whole raspberry pi will not restart. then when I power it back on it will just shut back off. I then have to redo noobs onto a new SD card I would GREATLY appreciate anyones help

I ‘m actually using a LCD Waveshare3.2” , I followed your steps to setup the lcd touchscreen for my rpi and it work but I have a problem with the resolution because if I open a repertory I do not see the whole contents on the screen .

hi! thank you for this post…. I was wondering if all the raspberry pi’s gpio are being held by this screen or do we have any of those availables for use??

it worked. but the resolution is for bigger screens. i got the menubar small, but the rest appears too big , and out of screen. the wastebasket icon is 1/6 of my 3.2″ screen. wich HAS the resolution capability too display the whole desktop. But i’m a PI newby and dunno how to adjust the screen resolution on this display. anybody?

hey Thanks for this good post …I have capacitive touchscreen which i brought from the link below..can you guide how i can configure the kernel modules…It will be very helpful for me…Thanks

hey Thanks for this good post …I have capacitive touchscreen which i brought from the link below..can you guide how i can configure the kernel modules…It will be very helpful for me…Thanks

I did a 5inch LCD for my raspberry pi. I dont use the touchscreen so i didnt have to install any drivers. It works out of the box but doesnt cover the whole screen unless you open the terminal and do:

HI I have my RPI running Pi Presents on a view sonic TD2230 Touchscreen. It all works fine, touching the click areas can navigate you thru my presentation, The problem arises when you use multitouch gestures like you would on a iPhone. Pinch or expand etc… and then all touch ability goes away. I can still control the presentation via a mouse, but I don’t get touch control back until I either relaunch Pi Presents, or if I unplug and plug the usb cable going to the touchscreen.

Could you provide me with a os image of open elec that you already built for the waveshare spotpear v4 3.2 inch touchscreen,because I cannot make sense of your website’s instructions?

In the case of the WaveShare driver, their setup script from their “LCD_show” repository will copy a device-tree overlay to /boot/overlays/ that provides most of the module config etc via boot-time device-tree patch.

After I did the step that “INSTALL THE FBTFT DRIVERS” and then reboot, my raspberry pi couldn’t boot successfully and the green light is always on, could you help me solve this problem? Thank you.

debian 5 lcd touch screen drivers factory

Now that we have access to the I²C GPIO expander, we yet have to find out which GPIO on the expander is wired to which pin of the screen. We will have to provide this information into the device tree, as it is explained in the hit,hd44780.txt file in the kernel documentation.

I will copy it here, as it is short enough, and also because unused drivers and their documentation have the tendency to disappear in the kernel — and I fear that this driver may one day be removed because so many users prefer to use some userspace Python code or stuff to talk to this kind of device.

So, we need to add this auxdisplay node in our device tree, and configure it with the pins of the PCF8574A (remember, we declared it as a gpio-controller just before).

For this, one could go with a multimeter to probe between the expander and the screen"s pins to understand how it was designed. But this screen setup is so cheap and familiar in the maker community that the LiquidCrystalI2C Arduino library will be a great candidate for retro engineering out the pinout.

By digging into the code — which is not easy to the eyes after passing so much time reading the Linux driver code — we can identify the few defines that identify the screen"s pins by numbers that are the number of the GPIO pin of the expander.

We can see that the bits used for the data are the 4..7 bits, because the values highnib and lownib are bitwise-and masked with 0xf0 — which represent the top most 4 bits of a byte. This way, we can establish the following layout of the GPIO expander to the screen from our retro engineering of the library:Pin number (GPIO expander)76543210

We can then add the screen to the root of the SBC"s device tree — because there is no reason to put it under the GPIO expander — and then configure the screen entry to use the expander"s pins [1].

After a try when the screen was displaying some stuff but the backlight was always off (so almost illegible on the white/blue screen variant), I had to change the backlight-gpios node to use GPIO_ACTIVE_LOW in order for the backlight to illuminate the screen at boot.

Sending a "backlight on" command to the screen turned the backlight off, so this step was an error. Indeed, the driver wants to activate the backlight only when necessary, but for me I like when it is always on, so I let this as-is even if it is not correct. The correct solution would be to enable the backlight on at the startup and keep it always on (or think to blink it when you put a message, the driver supports that too).

debian 5 lcd touch screen drivers factory

The touch screen i2c syntax would work for most other SBC’s. The Video section is tied to the am335x video, other SBC’s would have something similar, but slightly different.

debian 5 lcd touch screen drivers factory

The displays in the current mass production have some induced EMI from the LCD to the touchscreen, and I have found that the hardware pen down/up detection in the AFE is very sensible to spikes coming into the touch foils. The touch is not usable in 80% of all devices.

So I have rewritten the touchscreen driver to avoid the hardware pen detection and do that in software. IMO the hardware pen detection should not be used in production devices.

debian 5 lcd touch screen drivers factory

FirmwareGTT Firmware2.13474.4KiBFirmware files for the GTT series, including the GTT Client Library.  Supported units: GTT29A, GTT35A, GTT38A, GTT38C, GTT43A, GTT50A, GTT52B, GTT70A.

32/64 Bit USB Drivers Version 2.12.28.1 For Windows 7, 8, 8.1, and 10 and Windows Server 2008 R2, 2012 R2, and 2016.Based on 2.12.28 Drivers from FTDI.

FirmwareGTT Firmware2.12476.21KiBFirmware files for the GTT series, including the GTT Client Library.  Supported units:GTT29A,GTT35A,GTT38A,GTT43A,GTT50A,GTT52B,GTT70A.Changelog from R2.11.0.10067New Feature: Added Communication Logging feature

FirmwareGTT Firmware2.11437.37KiBFirmware files for the GTT series, including the GTT Client Library.  Supported units:GTT29A,GTT35A,GTT38A,GTT43A,GTT50A,GTT52B,GTT70A.Changelog from R2.10.0.9823New Feature: Added GTT Client Library

FirmwareGTT Firmware2.10384.38KiBFirmware files for the GTT series.  Supported units:GTT29A,GTT35A,GTT38A,GTT43A,GTT50A,GTT52B,GTT70A.Changelog from R2.9.0.9625New Feature: Added a Visual Bitmap feature for future Designer tool.

DriversUSB Drivers2.08.241.28MiBLegacy USB Drivers for all USB displays, except the GX. Including LK/ELK/VK/PK/OK/GLK/EGLK/GLT/GTT/MOU/X-Board/MX/Eve Series.

FirmwareGTT Firmware2.8384.38KiBFirmware files for the GTT series. Supported units:GTT29A,GTT35A,GTT38A,GTT43A,GTT50A,GTT52B,GTT70A.Changelog from R2.7.0.8424Object Update: Updated all implementation of Buttons

SoftwareGTT Support Software02.2306.13KiBSupport Software for the GTT Rev2.0 line, supports the GTT35A, GTT38A, GTT43A, GTT50A, and GTT70A. Version 2.2.0.0 adds support for firmware version 2.6 commands and fixes an issue with the Print UTF-8 command.

SoftwareGTT Support Software02.1231.11KiBSupport Software for the GTT Rev2.0 line, supports the GTT35A, GTT38A, GTT43A, GTT50A, and GTT70A. Version 2.1.0.0 adds support for byte and signed word array parameters.

SoftwareGTT Designer Software1.1437.44MiBDevelop and maintain gorgeous user interfaces and menu structures for your GTT using this immersive Windows environment tool. Design Software for the GTT Rev2.0 line, supports the GTT29A, GTT35A, GTT38A, GTT43A, GTT50A, GTT52B, and GTT70A.Changes from v1.13.0.10242:New Feature: Added Secure Communications Option Tick Box

SoftwareGTT Designer Software1.1336.64MiBDevelop and maintain gorgeous user interfaces and menu structures for your GTT using this immersive Windows environment tool. Design Software for the GTT Rev2.0 line, supports the GTT29A, GTT35A, GTT38A, GTT43A, GTT50A, GTT52B, and GTT70A.

Version 1.13.0.10242 brings the release of a major new GTT2.5 tool: charts, as well as development features such as logging and screenshots, in addition to minor bug fixes.Changes from v1.12.0.10123New Feature: Added Screenshot command to Tools

SoftwareGTT Designer Software1.1236.64MiBDevelop and maintain gorgeous user interfaces and menu structures for your GTT using this immersive Windows environment tool. Design Software for the GTT Rev2.0 line, supports the GTT29A, GTT35A, GTT38A, GTT43A, GTT50A, GTT52A, and GTT70A.

Version 1.12.0.10123 brings new GTT2.5 tools, including Images, ImageLists, and Animations, optimizations for screen loading and switching, and implements a number of bug fixes.Changes from v1.11.0.9989New Tool: Image (GTT2.5)

SoftwareGTT Designer Software1.1136.6MiBDevelop and maintain gorgeous user interfaces and menu structures for your GTT using this immersive Windows environment tool. Design Software for the GTT Rev2.0 line, supports the GTT29A, GTT35A, GTT38A, GTT43A, GTT50A, GTT52A, and GTT70A.

SoftwareGTT Designer Software1.1013.87MiBDevelop and maintain gorgeous user interfaces and menu structures for your GTT using this immersive Windows environment tool. Design Software for the GTT Rev2.0 line, supports the GTT29A, GTT35A, GTT38A, GTT43A, GTT50A, GTT52A, and GTT70A. Version 1.10.0.9818 brings new tools, such as Axis Ticks and Two Colour Bargraphs, updates the Actions tab with options such as Set Bargraphs Colour and Set Gauge Test Colour, optimizations found in the updated Settings windows that allow even more loading options, and a number of bug fixes.Changes from v1.9.0.9645New Tool: Gui Axis Ticks

SoftwareGTT Designer Software1.813.82MiBDevelop and maintain gorgeous user interfaces and menu structures for your GTT using this immersive Windows environment tool. Design Software for the GTT Rev2.0 line, supports the GTT29A, GTT35A, GTT38A, GTT43A, GTT50A, GTT52A, and GTT70A. Version 1.8.0.9367 brings full support for the integrated keypad of the GTT29A, exciting tool updates that offer enhanced customization, new event actions that improve object interaction, and minor GUI improvements to the Designer, including additional gauge designs.Changes from v1.7.0.9105New Display: Added GTT52B support

SoftwareGTT Designer Software1.78.73MiBDevelop and maintain gorgeous user interfaces and menu structures for your revision 2.0 GTT using this immersive Windows environment tool. Design Software for the GTT Rev2.0 line, supports the GTT29A, GTT35A, GTT38A, GTT43A, GTT50A, GTT52A, and GTT70A. Version 1.7.0.9105 includes enhanced reporting for advanced tools, property additions to the gauge tick parameters, and GUI improvements.

SoftwareGTT Designer Software1.68.71MiBDevelop and maintain gorgeous user interfaces and menu structures for your revision 2.0 GTT using this immersive Windows environment tool. Design Software for the GTT Rev2.0 line, supports the GTT29A, GTT35A, GTT38A, GTT43A, GTT50A, GTT52A, and GTT70A. Version 1.6.0.8429 includes major feature improvements including new tools, such as gauges and bars, updates to exisiting tools, GUI improvements, the addition of a Links tab for connecting objects, and full support for new commands released in GTT Firmware Version 2.7.

SoftwareGTT Designer Software1.58.53MiBDevelop and maintain gorgeous user interfaces and menu structures for your revision 2.0 GTT using this immersive Windows environment tool. Design Software for the GTT Rev2.0 line, supports the GTT29A, GTT35A, GTT38A, GTT43A, GTT50A, and GTT70A. Version 1.5.0.8080 includes minor updates to the deployment window, style updates, the addition of an Events tab for visual script creation, and full support for new commands released in GTT Firmware Version 2.6.

SoftwareGTT Designer Software1.48.41MiBDevelop and maintain gorgeous user interfaces and menu structures for your revision 2.0 GTT using this immersive Windows environment tool. Design Software for the GTT Rev2.0 line, supports the GTT35A, GTT38A, GTT43A, GTT50A, and GTT70A. Version 1.4.0.7878 includes minor updates to the user interface, the addition of new Image Assets, and new tools such as Animations, Image Sliders, and Image Nine-Slices.

SoftwareGTT Designer Software1.36.4MiBDevelop and maintain gorgeous user interfaces and menu structures for your revision 2.0 GTT using this immersive Windows environment tool. Design Software for the GTT Rev2.0 line, supports the GTT35A, GTT38A, GTT43A, GTT50A, and GTT70A. Version 1.3.0.7797 includes minor updates to user interface and features, as well as new tools, such as Triangle Buttons and Sliders.

SoftwareGTT Designer Software1.26.35MiBDevelop and maintain gorgeous user interfaces and menu structures for your revision 2.0 GTT using this immersive Windows environment tool. Design Software for the GTT Rev2.0 line, supports the GTT35A, GTT38A, GTT43A, GTT50A, and GTT70A. Version 1.2.0.7732 includes major updates to user interface, features, and tools.

SoftwareGTT Designer Software1.12.86MiBDevelop and maintain gorgeous user interfaces and menu structures for your revision 2.0 GTT using this immersive Windows environment tool. Design Software for the GTT Rev2.0 line, supports the GTT35A, GTT38A, GTT43A, GTT50A, and GTT70A. Version 1.1.0.6970 includes fixes for labels and traces.

SoftwareGTT Support Software01.05.35MiBSupport Software for the Legacy GTT Rev1.0 line, supports the GTT480272A. Version 1.0.0.44 includes a small fix to add flow control back into the auto detect process.

SoftwareAlphanumeric Software1.0.0.0802.25KiBDisplay Tuner Pro (MOCD#) is an update to our popular uProject testing software for Matrix Orbital displays. It adds support for new features and displays, including legacy and graphic units, to our established base of features and scripting. This tool supports all Matrix Orbital Intelligent and Economy Series displays, including the following:GLK Series (GLK12232-25-SM, GLK12232-25, GLK19264-7T-1U, GLK24064-25, GLK24064R-25-1U, GLK240128-25)

DriversGX Drivers1.010.81MiBThe latest release available, this software pack includes the GX Installation/Upgrade manual, DriverCore build 97, GX Firmware Upgrade 2235, and LCDStudio revision 806.

SoftwareAlphanumeric Software524.62KiBBoot Edit is designed for modification of advanced features of the LK/VK/PK USB and MX series. This is a more advanced version of the Boot Logo software.

SoftwareAlphanumeric Software40.03KiBBoot Logo is designed for modification of the startup screen for some alphanumeric displays with startup screens.

SoftwareAlphanumeric Software407KiBThis basic application allows you to test and set LCD Contrast, Brightness, VFD Brightness, set baudrate and send text to the display.

SoftwareGraphic Fonts17.12KiB\"Small\" is the 5 x 7 pixel monospaced font. It allows 40 characters per line and 8 lines of text on a 240 x 64 pixel display. Set font metrics to: character spacing = 1; line spacing = 1; left margin = 1; right margin = 0

SoftwareGraphic Fonts15.88KiB\"Clean\" is a very small, but still remarkably readable proportional font designed by William Ferrell of LCDproc fame. Depending on the specific characters printed, this font allows approximately 59 characters across the screen and 9 lines of text (GLK24064-25). Set font metrics to: character spacing = 1; line spacing = 1; left margin = 0; right margin = 0

SoftwareGraphic Fonts18.68KiB\"Futura\" is the 14 pixel high proportional font which is loaded as font 2 at the factory. Depending on the specific characters printed, this font allows approximately 35 characters across the screen and 4 lines of text. Set font metrics to: character spacing = 1; line spacing = 0; left margin = 0; right margin = 0

SoftwareGraphic Fonts19.09KiB\"Lucida Mono\" is a 10 x 15 pixel monospaced font. It allows 21 characters per line and 4 lines on a 240 x 64 pixel display. Set font metrics to: character spacing = 1; line spacing = 1; left margin = 5; right margin = 0

SoftwareGraphic Fonts13.75KiB\"Recta\" is a fairly small proportional font. At 11x11 pixels, it is about as small as you can make a font and still have proper looking characters - especially lower case characters with \"decenders\" like \"j\" and \"g\". The font is clean and readable and allows about 40 characters per line and 5 lines on a 240x64 display. Set font metrics to: character spacing = 1; line spacing = 1; left margin = 0; right margin = 0

DriversGX Drivers13.09MiBThe software contains update drivers for Windows 7/Vista/XP in 32 and 64 bits and updated LcdStudio, this completely replaces the 2008 pack.

FirmwareGTT Firmware165.15KiBNote: This is a bootloader upgrade only, simply copy the .bin and .raw files to your GTT Upgrade folder and cycle power. Do not delete the existing .bin firmware file.Changelog from R1.2.6076

FirmwareGTT Firmware165.16KiBNote: This is a bootloader upgrade only, simply copy the .bin and .raw files to your GTT Upgrade folder and cycle power. Do not delete the existing .bin firmware file.Changelog from R1.3.6632

FirmwareGTT Firmware165.19KiBNote: This is a bootloader upgrade only, simply copy the .bin and .raw files to your GTT Upgrade folder and cycle power. Do not delete the existing .bin firmware file.Changelog from R1.4.0.6931

SoftwareGX Series Software13.09MiBThe software contains update drivers for Windows 7/Vista/XP in 32 and 64 bits and updated LcdStudio, this completely replaces the 2008 pack.

The EVE screen editor is a Windows based tool, designed to allow EVE customers to experiment with creating display lists, utilizing a simple “drag and drop” method to control the EVE graphics controller.