sainsmart 5 inch tft lcd 800x480 touchscreen display factory

The Raspberry Pi 5"HDMI LCD is a 52pi design made from a 5-inch 800*480 resolution LCD panel and a Mini USB resistive touch screen. This LCD monitor can also be used on platforms such as Beaglebone Black, Banana Pi / Pro (drives will be Upgraded). This LCD is also an ordinary HDMI display that users can use for other mini PCs (requires driver support), even as an HDMI touch screen display module for computer monitors with 5-inch LCD display (Raspberry Pi, Banana Pi, etc.)

ER-TFTV050-3 is 800x480 dots 5" color tft lcd module display with vga,video,av signal driver board,optional 4-wire resistive touch panel with USB driver board and cable, optional capacitive touch panel with USB controller board and cable, optional remote control,superior display quality,super wide view angle.It can be used in any embedded systems,car,industrial device,security and hand-held equipment which requires display in high quality and colorful video.

ER-TFT050-3 is 800x480 dots 5" color tft lcd module display with ILI6122 driver IC,optional 5 points capacitive multi-touch panel with controller GSL1680 and optional 4-wire resistive touch panel screen,superior display quality,super wide view angle and easily controlled by MCU such as 8051, PIC, AVR, ARDUINO, ARM and Raspberry PI.

It can be used in any embedded systems,car,mp4,gps,industrial device,security and hand-held equipment which requires display in high quality and colorful image.It supports rgb interface. FPC with zif connector is easily to assemble or remove.

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

Unfortunately, their “driver” is an SD card image containing a complete installation of Raspbian which has been preconfigured to use their display. Which is fine if you’re setting up a brand new system that doesn’t need to be a specific distro, but if you’re trying to add the display to an existing Raspberry Pi, already configured the way you want it, with software installed and data present, or if you want to use a specific distro such as Octopi, then it’s not terribly helpful.

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 ?

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.

[ 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.

i have a watterott display (https://github.com/watterott/RPi-Display) and changed the device-name to “rpi-display”. i use a rsapberrypi 2 and hae the latest raspian image installed.

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 :)

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

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.

I do not think that has anything to do with it. Other than power pins, the rest are communication. If it still works then you are good. No, there is something else. I do suspect it us related to the BCM pin numbering. The real question is… Why isnt the eeveloper responding? I have since abandoned this TFT because of his lack of response.

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.

The SainSmart 3.2 sold by MicroCenter (20-111-971) is actually the exact same WaveShare SpotPear v3 documented here. So maybe your 2.8 would work if you tried a WaveShare driver?

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?

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.

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 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.

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?

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, 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

I have purchased a raspberry pi B+ total kit and waveshare 3.2 TFT display online. In the package i have been given a pre-loaded NOOBS installed SD card. I did not even start anything yet. What should i do what r the things needed and how to connect the display i really want to know. I need help as i don’t know anything. Does the above solution help or will u suggest something………………..

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

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.

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

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?

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.

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 )

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.

i am sorry, but i am a naive , and i have this question, can we upload any file into it for the display? like have a software in which if i tap it gives back a feedback to the code?

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

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.

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 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.

PLEASE DELETE this article. You have great power with this article showing up for so many people in their search results, and you display ZERO responsibility. This is terrible!

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 ‘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 .

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.

Purplewave India Pvt Ltd. is an AV equipment manufacturing Company. We offer a range of high-quality products such as Active LED displays, video wall displays, digital kiosks, speaker phones, conference video cameras, interactive displays, and much more!

RFF50VB-1IW-DHG is a 5-inch, resolution 800x480 pixels, TN transmissive color active matrix TFT LCD display, featuring HDMI signal with projected capacitive touchscreen (USB interface). This module has built-in controller TFP401, supporting HDMI connector (only DVI signal) interface. The PCAP touchscreen has a built-in IC ILI2130 which enables 1-point/2-point/multiple-point touch.

★RFF50VB-1IW-DHG: with a 40-pin header connector on board, supports up to Raspberry Pi 3B+ (contain Pi 4B) version. If customers choose displays supporting Raspberry Pi 4, please note that the interface is only compatible with micro HDMI. Customers need to use “Micro HDMI to HDMI” cable for these TFT series.

No, seriously!! The Mega is brilliant at what it does, but if you buy a DUE after you buy a MEGA, you will wish you got the DUE sooner, and your Mega will start gathering dust............. the difference is THAT dramatic! If you are tempted to go down the SPI display route, you DEFINITELY want a DUE, not a Mega! Simple reason being, the SPI speed of the Mega is 4Mhz? You can squeeze 42Mhz out of the DUE SPI, AND you can drive it via DMA, the Mega has no DMA.

If you INSIST on going down the Mega route, it would be advantageous to get an intelligent display just to make up for inadequacies of the Mega, some of these are overcome when using the Due, so a dumb display is less of a performance hit.

Is 7" one of your Mandatory design choices? The reason I ask is that the youtube video of the 4D systems display you saw was a 4.3" device and you can get those for about $50....

The inteligent 4.3" display goes for US$ 150,00 so no big difference, but that "dumb" one from the video, is really cheap. How your friend managed to control it?

And about the standard UTFT devices, I didn"t find any 7" inch, and the processing is left all for the Arduino right? I don"t know if I"m ready to the task, the screens I want to make are not that hard if it"s done graphically, but it"s alot harder if done by coding, my HTML code as almost 250 lines for it...

NMLCD-70800480-RTPis a colour active matrix LCD module incorporating amorphous silicon TFT (Thin Film Transistor). It is composed of a colour TFT-LCD panel, driver IC, FPC and a back light unit and with a Resistive Touch Panel(RTP). The module display area contains 800 x 480 pixels. This product accords with RoHS environmental criterion.

Shenzhen SLS Industrial Co.,ltd established in 2003, is a professional LCD module manufacturer and solution provider. We have 1 full-auto COG assembly line, 2 semi-auto assembly line, backlight assembly line, no dust TP bonding line and manufacturing tech support, we can provide unique, innovative and cost effective LCD module development and manufacturing. Our product range includes: middle-small size TFT LCD, industrial capacitive touch panel... Our LCD products have been widely used in communications, GPS, Equipment, electronic audio-visual, instrumentation, household appliances, PDA and other industries.

I bought a Raspberry Pi 3 Display Kit with 5inch 800*480 display at AliExpress:https://www.aliexpress.com/item/2017-Raspberry-Pi-3-Display-Kit-with-5inch-800-480-Capacitive-Touch-Screen-Monitor-16GB-Card/32829333501.html?spm=2114.13010708.0.0.ShtrHE

Edit3: Here you can buy just the single screen:https://www.aliexpress.com/store/product/High-Quality-5-inch-800x480-Display-Capacitive-Touch-Screen-Monitor-for-Raspberry-Pi-Windows-Beagle-Bone/2955027_32823498387.html?spm=2114.12010612.0.0.e2725c46A5RERo

I"ve been using the Sainsmart 3.2" and 3.5" TFT LCD (http://www.sainsmart.com/sainsmart-3-5-inch-tft-lcd-320-480-touch-screen-display-for-raspberry-pi-2-b-b.html) with my Raspberry Pi 2"s. I recently bought the Pi 3 and can"t seem to get the screen working.

It seems to fail at the point I download notro"s drivers from github (they download successfully, but on reboot, all I see on the hdmi display is the colored test square, and the SPI display is still backlight white with no image). It fails on this step even if I mix up the order.

We are touch screen with LCD display, Capacitive Touch Sensor Foil, 3 2 Inch Small Capacitive Touch Screen a professional motor manufacture, which integrates with technical research, production and sale, and is dedicated to providing customers with various motor products and services.In the face of the fierce market competition, we will be perfecting our own management and developing direction constantly, in order to make our Sainsmart 7 Inch TFT LCD Display capture the international market rapidly. The company strictly conducts quality management, strictly controls every link, and is determined to build a high-end brand image. Our company can meet the research and development and production needs of different market fields and different customers. The company has an elite market development team, professional technical support, and perfect logistics and distribution system. The company pays attention to detail management, relying on high-quality professionals and high-quality and efficient service concepts, has established a good corporate image in the society, and has been recognized and affirmed by all sectors of society and customers. Through cultural training, incentive mechanism and work experience, we create an atmosphere that stimulates people"s progress and growth, and inspires employees" career, responsibility and mission. We very seriously promise:Csame top quality, better price; exact same selling price, higher quality. The company attaches great importance to the investment in scientific research, and we have a well-equipped testing center and perfect production equipment.

Apr 21, 2014 · SainSmart Support for TFT 7 inch display. Ask Question Asked 8 years, 6 months ago. Modified 8 years, 6 months ago. Viewed 114 times 1 I"m trying to hook SainSmart"s 7 inch display to...

Display only results from: All Trade Shows; Fashion Show; Mobile Electronics Show; Smart Home and Appliances Show; ... Our main products include TFT LCD monitors, VGA touchscreen...

4.3 Inch TFT Monitor With Rearview Camera -in CCTV Monitor & Display. 17 Pics about 4.3 Inch TFT Monitor With Rearview Camera -in CCTV Monitor & Display : Pillow Tft Lcd Color Monitor Wiring Diagram,...

Sainsmart 7 Inch TFT LCD Display. Original Quality Mobile Phone Touch LCD Display Screen for Samsung A10 LCD A105/Ds A105... LCM Screen 800X480 TFT LCD Display TFT 7 Inch Digital....

1944 "7 inch tft" 3D Models. Every Day new 3D Models from all over the World. Click to find the best Results for 7 inch tft Models for your 3D Printer. ... SainSmart 7 inch TFT LCD Touch Screen...

5.0inch TFT LCD Display; 5.7inch Inch TFT LCD Display; 6.5inch TFT LCD Display; 7.0inch TFT LCD Display; 8.0inch TFT LCD Display; 8.4 Inch TFT LCD Display; 9.7inch TFT LCD Display; 10.1inch TFT LCD...

We have stable and reliable 4 3 Inch Capacitive Touch Panel Arduino, 1 3 Inch Mini Capacitive Touch Panel, 7 0 Inch Capacitive Touch Screen Devices, 8 Inch Tablet Capacitive Touch Screen that make users feel at ease, and the company"s reputation and brand image are well-known in the industry. As one of the best Sainsmart 7 Inch TFT LCD Display manufacturers and suppliers in China, we warmly welcome you to wholesale quality Sainsmart 7 Inch TFT LCD Display at competitive price from our factory.

Early LCDs had terrible ghosting (anyone remember trying to play Doom on an early mono LCD and the image instantly turning into incomprehensible hash?), but I can"t find any references for actual numbers for the pixel flip time. I"d be interested to know how they compare to eink. Does anyone know?

Even in non-power-constrained environments e-paper can be preferable - the glow of a typical LCD display is really distracting and doesn"t fit in a lot of (most) environments. Have enough gadgets around with LED displays and indicators and your home suddenly seems like a really bad 80s movie.

Smart but task-dedicated devices should probably run the display/buttons on a dedicated chip that talks to the CPU asynchronously, to avoid this problem.

Your microwave and VCR are always on - their displays are also always on, so they don"t need to be woken up before being used, they are already awake.

A thermostat with an always-on screen is the same, they"re already displaying information and the touch screen can be immediately used without delay - but we don"t want the display to be always on, because in general LCDs look awful in their environments. In general people prefer their homes to not look like server rooms with blinking lights and garish panels everywhere.

EDIT2: I measured it frame-by-frame, it takes 5 frames from the moment the button starts to move until the screen is completely functional, showing the proper image. The video is at 25 fps, so that"s 200ms, for the whole device to go from non-powered to fully working animation.

And this is also why this is fundamentally a product design problem that isn"t fixable via simply faster software - a non-primed human will take 500ms+ at each of these steps just in reaction time, the 200ms wake-time and whatnot is minor in comparison to the delay caused by having the human take multiple steps to do something. This is fundamentally about modes of interaction and not really about software performance.

Now, you could have a single home control display - or perhaps a single display in every room. And they"d all show the same information, maybe customised for each room, and include a few extra pages for setting up timers, lights, proximity sensors, or whatever.

There are plenty of applications for this kind of IoT, but the tech just hasn"t come together yet. I think the lack of good, cheap, large, low-energy displays is more of an issue than wake up times - because if the display uses very little energy, you can skip the wake up time.

Sure, yes, one reason we keep displays off most of the time is because of their usage, but more and more so it"s the secondary reason - there are lots of power efficient displays nowadays that can maintain an always-on screen at relatively low power cost, and smarthome devices generally aren"t reliant on battery power.

But the bigger problem is that LCD displays are ugly. They are backlit, and their response to better lighting in the room is to increase its own strength to make itself even more apparent. They are ugly, obnoxious, and annoying in the same way blinking router lights are, but multiplied several times over.

So we keep them off - we can afford to keep them on, but the fact that we keep them off 99% of the time less environmental consciousness but more an acknowledgment that they"re visually noisy, distracting, and just kind of don"t fit in. When you walk into a room you don"t want your attention immediately drawn to this LCD panel on the wall with its pale glow.

E-ink fortunately doesn"t suffer from this problem. It"s clearly legible, doesn"t require backlighting, and more importantly doesn"t appear distractingly electronic in everyday use. You can afford to keep an always-on e-ink display, not just because of its low power use, but because it won"t be this annoying glow in your peripheral vision always.

I think those are much more common in new installations. These are segmented LCD displays. An eInk display would not require an explicit segmentation layout, so new layouts could be programmed on the fly, prototyped very quickly, etc. And might even be a little easier to read, even during daylight hours I find these types of LCD displays difficult to read, especially from off-angles.

I"m more inclined to do the 6 rows of 7 displays which allow for a day aligned calendar for every month. It wastes a few displays of course, but the displays are easier to get.

I spent this weekend creating a small micro-controller system (freescale uC) with an attached tft lcd+touch, the latter cost me less than a 1/4 of this display and uses standard connections and readily available datasheets.

In their own words, the raspberry pi display uses interface signals that most other manufactures shunned due to several issues (EMI,etc) and their connector is hard to find on any other sbc currently in the market.

The display is huge compared to the raspberry pi board, what is the use case, considering the low resolution? Why go through all the trouble of using the connector on the pi instead of its other standard hdmi port ?

I"ve been working with these types of LCDs for a long time, and when it comes to these WVGA/SVGA 7" units you can get a ton from Asia at great prices but the factory will literally disappear in a few months. The LCD fabs constantly get bought/sold/churned as the major players like Sharp and LG shed off their last-generation fabs and the other smaller fish scoop them up.

Ideally a group like RPi will want to have the same part available for a long time so that they don"t need to create new revisions of the interface cables, power supplies, or software drivers to handle the change. It"s nearly impossible to autodetect one 7" LCD from another via software so you need to configure it entirely in a bootloader or kernel configuration line. And then that becomes a massive support issue.

There is a recycling tax here that is as low as ~5 cts for a tablet or a comparable electronic device. The burden of recycling is on the developping countries we send our used gear to. Not to mention the use of raw materials.

"How many customers want to record video from an external source anyway? It"s not worth adding $5 to the MSRP for a feature that isn"t going to get used."

[edit] I have an existing PiTFT which also doesn"t have a power button. I can turn it on/off programatically, but still a power button would be highly useful.

This is $60 plus taxes and shipping. I just found a 7-inch tablet for £28 ($43.10) on Amazon (plus a camera and RAM and stuff). Including taxes and shipping. Why is this so expensive?

The vast majority of the cost of this display is driven by factors unrelated to the technology level. Labour to build it, logistical costs, EMC qualification etc. That"s the case for almost all cheap consumer electronics.

Also, not all screens are equal. It"s not just resolution: there"s colour reproduction, viewing angles, brightness, contrast and response time. On the non-technical side mentioned on the blog, they mentioned they wanted a manufacture who would make the panel for a long time. I would bet a dollar that Pi screen beats the £28-tablet display on all the above parameters

narrow viewing angle, but wider temperature range[1]". The Innolux panel I mentioned in another comment here (https://news.ycombinator.com/item?id=10185433 ) is an example of this type.