setting up 7 inch raspi tft display supplier

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:

I just tested this, and it looks like the difference is how SPI is enabled. In the RPi 2 it’s enabled in raspi-config, not commented out in the blacklist file. I just updated the post so it should work now!

Looks like the only difference is in how SPI is enabled. In the new release of Raspbian, SPI is enabled in the raspi-config menu under advanced settings. In older versions of Raspbian, it is enabled by commenting out the line in the blacklist file

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 ?

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

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.

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

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

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.

[ 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

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

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?

Also can you someone explain what exactly happen when do rpi-update? Want to understand what this step actualy doing and help me to debug any such situation and able to help others.

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.

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

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.

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

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.

Great write up – worked first time for me. The only difference is by modules blacklist file was empty so there was no change needed there. Maybe to do with me being on a newer rasbian?

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

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

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.

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

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.

Please check out my answer, it may help you if it works. I’m not in that case but I’m assuming that the desktop environment simply doesn’t automatically start running anymore… This can be changed in the raspi-setup

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

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.

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.

what if OS is not Raspbian, any other distro like Yocto project, etc.? Could you please specify process without “rpi-update” that makes driver installation process more generic, not dedicated to Raspbian.

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.

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

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.

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?

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’m a proper novice, have no coding experience. A these tutorials and walk throughs are invaluable. So thank you in advance for all the help and support.

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

No matter what I do, I can’t get this to work. It works perfectly fine on my Pi2, but when I follow and use the guide on my Zero, I always end up with the activity LED blinking 8 times (corrupt SD/filesystem error).

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

The owner of this article should including a WARNING in the header that if someone follows the steps, they will install a deprecated driver (which is only visible as tiny text on its gethub page here https://github.com/notro/rpi-firmware). This driver after install will break Raspberry Pi and the SD card will need to be reimaged, for some less experienced users, this could also mean lost work if they failed to backup their code or resources. On windows, it requires installing Linux reader software and it takes a long time to fix this f**kup which could easily have been avoided if the author had and sense of responsibility.

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!

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

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?

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!

There are a few options for powering the Pi and the display. If you wanted, you could power the Pi and the display using separate power adapters, but we"re going to power the Pi directly, then use jumper cables to supply power to the display board.

The kit comes with four jumper cables, but, for a Raspberry Pi 4, you need cables for only two pins: 5V and GND. Connect one cable to the 5V pin on the Pi and the 5V pin on the display board. Then connect to a GND pin on the Pi and the GND pin on the display board. See the image for details.

Before we assemble the touch screen, we need to make sure that our Raspberry Pi has the latest version of Raspberry Pi OS, and that all the software is up to date.

Hook up your Pi to a monitor, plug in your keyboard and mouse and boot your Pi into Raspberry Pi OS. Once booted up, open a new Terminal window and type the following commands, hitting enter after each one:

Using the white ribbon cable supplied, connect one end to the controller board, making sure that this end has the blue tab facing down, towards the board (the opposite end, the end not being attached to the controller board, should have the blue tab facing up, so you can see it):

Now it’s time to power it all. Plug an official Raspberry Pi power supply into the controller board (the controller board will power your Pi via the jumper wires) and away you go!).

Depending on your display stand, you might find that the LCD display defaults to being upside-down. You can fix this by rotating it with /boot/config.txt.

If some windows in X are cut off at the side/bottom of the screen, this is unfortunately a side-effect of developers assuming a minimum screen resolution of 1024x768 pixels.

This application note is part 1 of our 2 part TFT LCD screen series. Part 1 discusses configuring the screen resolution of a TFT with a Raspberry Pi. Part 2 discusses calibrating the touch screen of a TFT. Click here to read part 2.

This application note discusses how to setup a TFT touch screen display with Raspberry Pi. The display chosen for this project is a 7-inch LCD with a capacitive touch feature. The display has 1024x600 pixels of resolution and when calibrated for the Raspberry Pi can display 16.7M colors. With a few changes to the Raspberry Pi configuration files the dimensions of this display can be matched for perfect resolution.

The display in this project is easy to interface with the Raspberry Pi because it has an LVDS to HDMI backpack adapter connected. This makes it simple to connect an HDMI cable between the two devices and begin your project. In a few steps any display can be configured for optimal resolution. Additionally, this display has a capacitive touch screen which can be calibrated through Raspberry Pi for accuracy. These features combined with the large size of the display make it a great choice for a variety of Raspberry Pi projects.

Connecting the TFT to the Raspberry Pi is simple and only requires a few steps. The display has a HDMI connection backpack interfaced with the device so there is no need for soldering or individual pin connections. If you have used Raspberry Pi before, you will notice that the connection to the TFT is standard and straightforward. Before powering the Raspberry Pi you should make all the necessary connections to the screen. Plug in the HDMI. Connect the CTP port with a micro-USB cable. Power the screen with micro-USB cable connected to a USB port on the Raspberry Pi or a power adapter that provides 5V. You only need three connections to the HDMI backpack module on the TFT.

You will need a mouse and keyboard to setup the Raspberry Pi before the touch screen is enabled. You will also need a micro SD card with Noobs loaded onto it before powering. (Installing NOOBS) Lastly you will need an ethernet cable to setup internet to download or update the software. Once you power the Raspberry Pi, Noobs will give you some options of what software platform you want to install. For this project I chose Raspbian (recommended option). (Installing Raspbian) After installation you will likely notice that the graphics are distorted or that the width and height of the screen are not the desired dimensions. This is because Raspberry Pi’s auto-calibrate feature doesn’t recognize this display. So, to get the best picture, we will need to calibrate it manually.

If it’s not terrible, and you can still see what you’re doing on the display, you can do this through Terminal. We want to edit the “config.txt” which loads from the boot file. The other option is to remove the SD card and load the file on the computer or setup SSH and edit the file remotely.

The file will open in a text editor called nano. We need to add the specifics of our display to the file by adding the following commands to the file:

If you notice that turning safe mode off results in a blank screen you could have a bad HDMI connection. First try another HDMI cable. If this does not fix the problem, then we can increase the signal strength of the HDMI by editing the config_hdmi_boost command in the config.txt file. The standard setting in the configuration file is set as:

This default value is 2 and can be increased up to 11 if necessary. Try adding this command at increased increments until the issue is solved. You will need to edit the config.txt file on your computer or remotely for this step.

With only a few changes to the Raspberry Pi’s default configuration file the TFT can become compatible with the Raspberry Pi. This display is a great choice for interfacing with the Raspberry Pi because it has an HDMI connection type which makes for any easy setup. After the resolution and is set to a desired value we can now optimize the touch feature of the display. See here for more information on how to further calibrate this display.

Inky wHAT is a 400x300 pixel electronic paper (ePaper / eInk / EPD) display for Raspberry Pi, a larger version of our popular Inky pHAT display, with more than 5x the number of pixels, and available in three colour schemes - red/black/white,...

Waveshare 22689 - 1.9inch Segment E-Paper Module, 91 Segments, I2C Bus, Ideal For Temperature And Humidity Meter, Humidifier, Digital Meter - 1.9inch Segment e-Paper Module

A high-resolution 8", IPS, 1024x768, HDMI display, with Pimoroni-made display driver board and keypad, that"s perfect for building into projects like arcade cabinets, or just use it as a handy display for your Raspberry Pi!

Build a full-featured media center capable of playing nearly all of your digital media using any 40 pin Raspberry Pi and the Media Center HAT Raspberry Pi touchscreen display. Native support in...

Inky wHAT is a 400x300 pixel electronic paper (ePaper / eInk / EPD) display for Raspberry Pi, a larger version of our popular Inky pHAT display, with more than 5x the number of pixels - red/black/white version.

If you"re looking for the most compact li"l color display for a Raspberry Pi B+, Pi 2, & Pi 3 (most likely a Pi Zero) project, this might be just the thing you need!

In honour of Raspberry Pi"s 10th birthday, we"ve fused a RP2040 microcontroller with an EPD display to make a stylishly monochrome, maker friendly, e-paper badge(r)...

Pico Inky Pack features the speedy 2.9" e-paper display that you can find on Badger 2040, coupled with three handy buttons for interfacing. Equip it to the back of your...

ER-TFTV070A1-5 is 800x480 dots 7" color tft lcd module display with small HDMI signal driver board and superior display quality,super wide view angle. It"s optional for 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,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.It"s also ideal for Raspberry PI by HDMI.

GDTE070A1-5 is 800x480 dots 40 Pin 7" color tft lcd module display with small HDMI signal driver board and 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.It"s also ideal for Raspberry PI by HDMI.

It is the cutest display for the Raspberry Pi. It features a 3.5" display with 480x320 16-bit color pixels and a resistive touch overlay. It"s designed to fit nicely not only to the Pi Model A or B but also works perfectly fine with the Model B+/2B/3B/4B.

Need a display screen for your next Raspberry Pi project? Check out our range of LCD, OLED, and eInk displays. We"ve got everything from capacitive touch screens, tiny crisp OLED screens, to eInk displays that are easy on your eyes or for power-saving applications.

All orders are processedwithin 24 hoursafter they are placed. Usually, we are able to ship orders the next day. Weekend orders are shipped on the following Monday. You will receive a shipping confirmation email from our system when the shipping information has been uploaded.

A working Raspberry Pi system requires lots of other parts in addition to the tiny Pi board itself. You"ll need a power supply, a mouse, various cables, and, unless you already own one, a monitor to display screen output for your Raspberry Pi system. Raspberry Pi users are accustomed to hunting up old monitors from long-discarded computers, or temporarily requisitioning a monitor from a currently running system to use as a display for the Rasp Pi.

Since the first days of the Rasp Pi, users have dreamed of a mini-monitor that runs on the Rasp Pi power and is tailored for the needs of the Rasp Pi environment. Some third-party Rasp Pi displays have appeared in the past, and we have reviewed some in this magazine, but those who follow the Pi have known for some time that the Raspberry Pi Foundation would eventually announce an official Pi display.

The Raspberry Pi display [1] was announced on September 8. In addition to serving as a general device for viewing screen output, according to the foundation, the new display also "gives users the ability to create all-in-one, integrated projects such as tablets, infotainment systems, and embedded projects." The new 7-inch display has touchscreen capabilities. With a price tag of $60, the Rasp Pi display came to market nine months past its originally planned release date [2]. The foundation has explained that the delays resulted from efforts to integrate the Raspberry Pi 2 and difficulties encountered in locating a supplier for the screen.

The display screen measures 7 inches across the diagonal or 155x86mm. The entire screen, including the frame, measures 194x110mm, and the overall depth, minus an attached Rasp Pi, is about 20mm, with a weight of 277 grams. The screen has 10-finger capacitative touch, although standard Linux desktop environments currently do not handle touch gestures well.

The Rasp Pi supports a number of display interfaces, such as HDMI. For some screens that are already available for the Raspberry Pi, the little computer also relies on the GPIO interface. The Raspberry Pi Foundation looked to the underused Display Serial Interface (DSI) in order to connect the Rasp Pi with the screen . You will find the DSI port on the side that is opposite from the network and USB ports.

The DSI connector transmits more than just images. It also sports an integrated I2C-Bus, which makes it possible to transmit gesture entries and control signals for background lighting. As a result, the screen will only work with second-generation Raspberry Pis or the plus models, which are the first series Rasp Pi A+ and the B+. The display board does have two extra pins for the Rasp Pi B. However, according to Pi developer Gordon Hollingworth, the foundation still needs to work on support for the pins.

The first purchasers receive the display as a kit that requires assembly. Even though no assembly instructions are included, the components are easily put together. You should first set the display board upside down next to the screen and connect the board to the ribbon cable that comes out of the screen. Then, turn the board over and adjust it so you can properly mount it.

Next, very carefully plug the second ribbon cable that comes out of the screen into the small jack on the front side of the display board. This cable carries signals from the touchscreen. With the braid side facing upwards, plug in the ribbon cable, which will be connected to the Rasp Pi, and then, using a spacer, screw the board to the screen (Figure 1).

Now you need to decide how you want to supply power to the Rasp Pi and to the screen. Like the Rasp Pi, the screen has a micro USB connector, which means you can either run the power from the display to the Rasp Pi via the USB jack, or you can use the jumper cables that are included to wire the Rasp Pi for 5V and GND with the pins that are on the pin strip. We chose the jumper cable method for our test. The first step is to connect the red cable to the 5V pin and the black cable to the GND pin, then set the Rasp Pi on the spacer. Then, connect the two connectors to the 5V and GND on the Rasp Pi.

Figure 2 shows the pin assignment of the GPIO port for a Raspberry Pi 2. To reduce the size of the depth of this arrangement, you can also mount the Rasp Pi the opposite way around to the display board. The final step to this process is to connect the DSI cable with the USB power supply (Figure 3).

Figure 2: The GPIO pin assignment for a Raspberry Pi 2. The user will find the 5V and GND pins across from pins 2 and 3 for connecting to a power supply.

With respect to the software, all you need to do is update the system (Listing 1). If updates are not properly installed, you will be able to see images on the screen, but the screen will not accept any entries. After a restart, the Rasp Pi will promptly display the image that is familiar from the HDMI port on the screen without any modifications to the system. Touch entries will also immediately function properly within the X server GUI. The 800x480 resolution should suffice for everyday use, even though it is not a substitute for a desktop monitor (Figure 4). The touchscreen has the same level of precision as tablets or smartphones that are currently available on the market.

Figure 4: The 800x480 resolution of the RasPi touchscreen is sufficient for most projects. The Matchbox keyboard from the package sources even gives the user a virtual keyboard.

Connecting the Rasp Pi display screen through the DSI port frees the HDMI port, which is then available for attaching a second monitor. However, you do not automatically get an image on a second monitor. Instead, you first need to indicate to the program, such as a video player, that you would like to send the images to an external screen.

The example from Listing 3 starts the video on the second screen while the GUI on the Raspberry Pi screen remains free for other activities. At this point, there is still no genuine dual-display function that turns the Rasp Pi display and a monitor connected via HDMI into a large display. The graphical tools used for setting up the resolution via Menu | settings | screen settings still only recognize the Rasp Pi screen. Instructions for manually configuring a monitor set up via the /etc/X11/xorg.conf file are not yet available.

Step 1: Format the SD Card using SD formatter. Download the SD Formatter from below link. Run the setup file in your windows PC and launch/run the application(SD card should be connected to PC). Select “Option” Select FORMAT SIZE ADJUSTMENT “ON” and Click “OK” Now Click on “Format” Click on “OK” Click on “OK” Click […]