3.5 tft lcd touch screen raspberry pi driver quotation

The touch screen LCD is ready with 320×480 resolution, 50 FPS (Frame per second). Resistive touch control is being supported by the Raspberry Pi OS or Raspbian (directly-pluggable). However, we will still need to install the driver for graphic display :)

However, there is a dedicated case/enclosure and a low-profile heatsink with a fan for this LCD to fit perfectly on the Raspberry Pi 4 Model B. The case has an opening for the LCD, and the low-profile heatsink with a fan keeps the Raspberry Pi 4 Model B protected and cool! You get a perfect console :) Don"t forget to remove the top lid/cover of the enclosure for the 3.5-inch LCD.

Note: The Raspberry Pi 4 Model B, 3.5-inch Enclosure, and the Low-Profile Heatsink with a fan are NOT INCLUDED in this product, please get them separately.

As we understand, Raspberry Pi 4 Model B delivers great performance and of course, more power will generate more heat as of all CPU :) So we need a way to install an additional heatsink to dissipate the extra heat. It will be better if we can have the option to add a cooling fan for active cooling. Well, this 3.5-inch touch screen LCD comes ready with the heatsink and cooling fan for you to use with the Raspberry Pi 4 Model B. it solves all the concerns.

The 3.5-inch touch screen uses the GPIO on the Raspberry Pi board, so it stretches out 2 pins as the power to supply the cooling fan on the low profile heatsink, and keep the Raspberry Pi board cool!

Note: The Raspberry Pi 4 Model B, 3.5-inch Enclosure, and the Low-Profile Heatsink with a fan are NOT INCLUDED in this product, please get them separately.

The Graphic driver is provided and can be downloaded for Raspberry Pi OS/Raspbian. It also supports Ubuntu and Kali Linux. Do follow the steps here: http://www.lcdwiki.com/MHS-3.5inch_RPi_Display

Note: Please use the recommended system for the touch screen. If another system is used, it may not have the touch function or may not work. You need to configure it yourself. Because there are many systems that the Raspberry Pi can use, we can’t make every system compatible with the touch screen.

All the accessories listed below tier pricing need to pay.We won"t deliver until you select. Power adaptor should be 5V/2000mA in output and center pin for positive voltage and the outer shield for negative voltage .The temperature for controller RTD2660 would increase during working.That"s normal phenomenon,not quality problem.

ER-TFTV070A1-3 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.

While googling for any info about lcd controller I came across this page: http://heikki.virekunnas.fi/2015/raspberry-pi-tft/, author managed to get from manufacturer patch file for kernel sources and tested it with 4.1.y - on which lcd worked. But still LCD replace HDMI, but I want to use this screen as additional for user interaction, while the bigger on HDMI as presentation monitor.

I have looked through files that he (author of page `heikki.virekunnas.fi`) published, and I came to conclusion that the patch do not changes standard ILI9341 driver but only replace default framebuffer and directs it to ili driver while cutting out hdmi, only single mention in patch file about ili9341 is adding it"s .ko file to $obj in makefile... wow I"m so smart

Since, fbtft has been merged with rpi kernel, so the fb drivers (including ili9341.c) was moved to fbtft_device driver (so the author of page can"t compile latest kernel with driver+patch).

So something about hardware, which I reverse engineered by the "hard way" - "grab multimeter and run through all LCD FPC pins and shift register pins"

Now I noticed there is "9486L" which can suggest that LCD screen is controlled by ILI9486L, I found this LCD on taobao too but I can"t contact seller.

I"m pretty sure about D/C (Pin 37 on LCD) and Reset (Pin 19 on LCD) pins by looking into driver code, but I can"t identify other signals (WR/RD/CS/etc...)

[ 0.000000] Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2709.boardrev=0xa01041 bcm2709.serial=0x2938b030 smsc95xx.macaddr=B8:27:EB:38:B0:30 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

[ 4.838806] input: MOSART Semi. Rapoo 2.4G Wireless Touch Desktop as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:24AE:1000.0001/input/input1

[ 4.862704] hid-generic 0003:24AE:1000.0001: input,hidraw0: USB HID v1.10 Keyboard [MOSART Semi. Rapoo 2.4G Wireless Touch Desktop ] on usb-bcm2708_usb-1.3/input0

[ 4.902783] input: MOSART Semi. Rapoo 2.4G Wireless Touch Desktop as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.1/0003:24AE:1000.0002/input/input2

[ 4.926400] hid-generic 0003:24AE:1000.0002: input,hiddev0,hidraw1: USB HID v1.10 Mouse [MOSART Semi. Rapoo 2.4G Wireless Touch Desktop ] on usb-bcm2708_usb-1.3/input1

- Controller is not ILI9341/ILI9325 - those are for smaller displays (320x240, etc...), I guess this might be ILI9486/9488 because they are for 480x320 displays. But when I compared init with DS it does not fit right so LCD can have a clone of ILI9486/9488 ...

- Module use only SPI interface and two CE signals (CE0 for touch controller, CE1 for LCD shift registers - compared to others lcd modules, in KeDei module this is swapped),

3.5 inch RPi LCD V3.0 HVGA 480X320. There is a XPT2046, 74HC04D, 74HC4040D, and 2 74HC4094D chips on the back. Is there a way to determine which driver I need to use in software?

I am not 100% convinced that the distribution given works with the LCD (the item I bought is dis-continued but the seller provided another item that has identical specifications - 3.5" IPS 15fps 480x320 resolution - but I suspect it has a slightly, or altogether different, controller.

[*]Is there any way I can extract some information of what driver has been used, or tried to use, for the TFT via that half working distribution? As far as I know, a GPIO/ SPI connection will not gather connected hardware information...

I am not 100% convinced that the distribution given works with the LCD (the item I bought is dis-continued but the seller provided another item that has identical specifications - 3.5" IPS 15fps 480x320 resolution - but I suspect it has a slightly, or altogether different, controller.

[*]Is there any way I can extract some information of what driver has been used, or tried to use, for the TFT via that half working distribution? As far as I know, a GPIO/ SPI connection will not gather connected hardware information...

I bought a display off Amazon described as [ SainSmart 3.5" inch TFT LCD 240x320 RGB Pixels Touch Screen Display Monitor For Raspberry Pi for Model B & B+] and sold by: Sain Store. What I received is the 320x480 display you described. I am also trying to verify the model before I try to set it up.

What I would like to do is be able to "diff" a clean image and the modified image to find out exactly which drivers were used, what files have been modified for their use to be able to create a standalone install package that be used on a clean install.

TheQuestor wrote:What I would like to do is be able to "diff" a clean image and the modified image to find out exactly which drivers were used, what files have been modified for their use to be able to create a standalone install package that be used on a clean install.

Although, after following the installation instructions, the screen I have behaves weirdly: there seems to be a symmetry between the point where I click on the screen and the real place of the pointer. Depending on the argument of the rotate instruction in

the symmetry is vertical or horizontal. I haven"t figured out yet how to fix this and have the pointer exactly where I touch on the touchscreen. Hope this helps...

It was working but was a bit too slow so, I Increased the speed After setting Everything back to normal the screen is not working properly. The display is fine , but the touch is not responding. Please help! Did I BROKE it ?

3.5inch RPi LCD (A) and 3.5inch RPi LCD (B) are hardware compatible with each other (uses different driver), and can be mutually substituted in most cases. (A) for low cost ver. while (B) for IPS ver. with better displaying.

Why the LCD doesn"t work with my Raspbian?To use the LCD with the Raspberry Pi official image, driver (SPI touch interface only) should be installed first. Please refer to the user manual.

However, for the first testing, you may want to use our image directly (if provided).Why the LCD still doesn"t work with the Waveshare provided image?Make sure the hardware connection is correct and connects fine.

The PWR will keep on and the ACT will keep blinking when the Raspberry Pi starts up successfully, in case both of the two LEDs keep on, it is possible that the image was burnt incorrectly OR the TF card was in bad contact.Which power supply should I use?It is recommended to use a 5V/3A power adapter for the Raspberry Pi other than USB connection, otherwise the Pi may failed to start up because the PC"s USB port might have not enough power.

Since the first-generation Raspberry Pi released, Waveshare has been working on designing, developing, and producing various fantastic touch LCDs for the Pi. Unfortunately, there are quite a few pirated/knock-off products in the market. They"re usually some poor copies of our early hardware revisions, and comes with none support service.

3.5inch RPi LCD (A) and 3.5inch RPi LCD (B) are hardware compatible with each other (uses different driver), and can be mutually substituted in most cases. (A) for low cost ver. while (B) for IPS ver. with better displaying.

The PWR will keep on and the ACT will keep blinking when the Raspberry Pi starts up successfully, in case both of the two LEDs keep on, it is possible that the image was burnt incorrectly OR the TF card was in bad contact.

It is recommended to use a 5V/2A power adapter for the Raspberry Pi other than USB connection, otherwise, the Pi may fail to start up because the PC"s USB port might have not enough power.

My problem is, that when I use VNC to remotely access the PI, (I assume) because of the LCD driver the resolution is too small and I can only see part of the windows and can"t change resolution. Why can"t I change the resolution?

Any idea how to solve the problem? Can I somehow delete the driver or revert to the original display configuration? Unfortunately I only have remote access to the PI right know. (BTW I"m using RealVNC and PI 3B+)

It is the cutest, little 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+.

You can create a 99-calibration.conf file to save the touch parameters (not necessary if file exists)./ect/X11/xorg.conf.d/99-calibration.confSave the touch parameters (may differ depending on LCD) to 99-calibration.conf, as shown in the picture:

This small 3.5 inch touch screen Raspberry Pi Display module is designed especially for Raspberry Pi, using the latest Linux Core system. This is ideal for DIY anywhere, anytime and does not require any separate power source or case to hold it. The module sits right on top of Pi and an ideal alternative solution for HDMI monitors. The screen also comes with a stylus to interact with the small screen.

Would you like the SPI kernel module to be loaded by default? YESS! thats what we wanted. Once done, exit the configuration menu and type in terminal command ‘sudo reboot‘; for the changes to take effect.Note:This method is applicable, only with the Raspbian version released after 1-31-2015.

Now we will have to configure the fbturbo video driverso as to change the video out from HDMI bus to SPI bus. For that, enter the following command in the terminal window:

After system reboot there wont be any output on the HDMI screen. So, to enter the further commands in the terminal we will have to use SSH method for remote connection to the Raspberry Pi board. Click here to see the steps on how to setup a remote connection.

Next step is to configure the kernel modules for the LCD and the touchscreen for which we need to edit the /etc/modules file. Use the following command:

Currently, the module for Raspberry Pi’s Broadcom processor snd-bcm2835 is set to load automatically. Add this code below the snd-bcm2835 line to support fbtft_device:

Some people seems to have issues with the touch panel,  having the y-axis inverted in X11. If you experience this problem all you have to do is modify the configuration file usr/share/X11/xorg.conf.d/10-evdev.conf. For that enter

The PWR will keep on and the ACT will keep blinking when the Raspberry Pi starts up successfully, in case both of the two LEDs keep on, it is possible that the image was burnt incorrectly OR the TF card was in bad contact.