mcufriend.com lcd tft display for sale

This note introduces a low-cost Thin Film Transistor (TFT) display to enhance the operation and usefulness of Liquid Crystal Display(LCD) devices. TFT technology controls the pixel element on the glass surface thereby greatly reducing image blurring and improving viewing angles.

The test board chosen for this exercise is the Elegoo Arduino UNO board from the corresponding Super Starter Kit. The kit already has several simple numeric and text displays. The TFT display may perhaps provide better ways to interact in applications.

The controller for the illustrated model of the TFT display is SSD1297.This information is important because the display (owing to its low cost and high popularity) has many different manufacturers who may not leverage the same controller instruction set. The specification of the controller in the coding exercises is examined in the Appendix section of this note.

Some familiarity with the coordinate system for displays (i.e. top-left is0, 0) and the packing of RGB values into a 16-bit word (5 for R &B, 6 for G) makes the learning curve ramp at a faster pace.

Of course, the display can be mounted elsewhere and the pins connected to the Arduino directly or indirectly using, for example, a breadboard. Other components can then use the breadboard in lieu of a shield with custom connectors. Of course, without access to such anon-standard or readily available breadboard, it is impossible to illustrate this arrangement in this note.

The Examples folder for the library provides the starter files for the tests. If you are using a newer display you will need the updated libraries from the GitHub repository (see link in References below)and using the#definestatement to identify the display model.

The output from the diagnostic program, LCD_ID_reading.ino, is shown below:Read Registers on MCUFRIEND UNO shieldcontrollers either read as single 16-bite.g. the ID is at readReg(0)or as a sequence of 8-bit valuesin special locations (first is dummy)reg(0x0000) 97 97ID: ILI9320, ILI9325, ILI9335, ...reg(0x0004) 97 97 97 97Manufacturer IDreg(0x0009) 97 97 97 97 97Status Registerreg(0x000A) 97 97Get Power Modereg(0x000C) 97 97Get Pixel Formatreg(0x0061) 97 97RDID1 HX8347-Greg(0x0062) 97 97RDID2 HX8347-Greg(0x0063) 97 97RDID3 HX8347-Greg(0x0064) 97 97RDID1 HX8347-Areg(0x0065) 97 97RDID2 HX8347-Areg(0x0066) 97 97RDID3 HX8347-Areg(0x0067) 97 97RDID Himax HX8347-Areg(0x0070) 97 97Panel Himax HX8347-Areg(0x00A1) 97 97 97 97 97RD_DDB SSD1963reg(0x00B0) 97 97RGB Interface Signal Controlreg(0x00B4) 97 97Inversion Controlreg(0x00B6) 97 97 97 97 97Display Controlreg(0x00B7) 97 97Entry Mode Setreg(0x00BF) 97 97 97 97 97 97ILI9481, HX8357-Breg(0x00C0) 97 97 97 97 97 97 97 97 97Panel Controlreg(0x00C8) 97 97 97 97 97 97 97 97 97 97 97 97 97GAMMAreg(0x00CC) 97 97Panel Controlreg(0x00D0) 97 97 97Power Controlreg(0x00D2) 97 97 97 97 97NVM Readreg(0x00D3) 97 97 97 97ILI9341, ILI9488reg(0x00D4) 97 97 97 97Novatek IDreg(0x00DA) 97 97RDID1reg(0x00DB) 97 97RDID2reg(0x00DC) 97 97RDID3reg(0x00E0) 97 97 97 97 97 97 97 97 97 97 97 97 97 97 97 97GAMMA-Preg(0x00E1) 97 97 97 97 97 97 97 97 97 97 97 97 97 97 97 97GAMMA-Nreg(0x00EF) 97 97 97 97 97 97ILI9327reg(0x00F2) 97 97 97 97 97 97 97 97 97 97 97 97Adjust Control 2reg(0x00F6) 97 97 97 97Interface Control

The controller is referenced as SSD1297 with ID=0x9797. This display requires the use of the following statement in the code prior to the invocation of other header files for the display. Please review the header files for the equivalent#define SUPPORT_1289

Many thanks toDavidPrenticefor the display driver library and the guidance, support and advice during the tests for this display. I would have failed at the starting block without his generous assistance. He is an authority on the drivers for this class of displays.

there are (now) a lot of 2.8" TFT Pi designs out there. I believe mine was the first, and has been around in one form or another for over a year now. I offer full support on this forum, and here is the support thread :

A while ago I bought this 2.4"" Inch TFT LCD Touch Display Shield for Arduino UNO, but only recently I came up with a project where I could make use of this piece of hardware.

Displaying these images stored on the SD card would be an integral part of this project, so I did a quick proof of concept ... which happened to be very disappointing!

Next, I created a much simpler test image which just displayed some basic colors and interestingly, those were mainly Ok for the "primary" RGB colors, but already off for composite colors like cyan, yellow or purple.

It turned out that indeed the RGB packing function from the Adafruit library did not play well with that display, but shifting and OR"ing the bits only slightly different would do the trick.

Then, instead of calling the method tft.clor565, a call to the newly created function fixed_color565 made sure that images got displayed correctly from now on..

I am trying to interface a touch scren lcd with stm32 board. I have an mcufriend 2.4" touch screen lcd and i intend to interface it with nucleo-f303re board. I ,unfortunately, am not able to find a datasheet for the lcd. I know that the lcd can be interfaced with spi. but as i mentioned i do not have any datasheet for the lcd. Does anyone has any information on where to find the datasheet or a library for the lcd?

I bought four MCU Friend 3.5″ TFT shields.  And, unfortunately, they have spiraled me into a deep, dark place trying to figure out how to use them.  The the documentation consists of a sticker on the antistatic bag, a picture of the shield with a list of 5 different possible LCD drivers, a pinout, and a block of code that supposedly represents the startup code.  The unfortunate part is that none of these have been exactly right – they all have errors.  This article is a description of the journey to figuring out how to use them.

It also has a picture which says the LCD has one of several different controllers (and after digging in I know for a fact that two of mine were made by Raydium and are not on the list)

Next, I started down the path of trying to figure out what the controllers were by using register reads.  David Prentice (the guy who wrote/maintains the MCU Friend_kbv Arduino library) has an absolute ton of responses on the Arduino forum trying to help people figure out what their shield is.  He asks them to post the register report from his example program LCD_ID_readnew which is included as an example in the library.

When you look at these LCD controllers they all have some variant of “Read ID” which responds with 1-6 bytes.  The basic idea of this program is to look at what bytes are returned to try to identify the controller.  Here is an example of what I got when I ran the LCD_ID_readnew program on my shields:

The key thing to see in this output is the register 0x04 which says 54,80,66 which identifies this as a Raydium RM68140 LCD controller.  Here is a snapshot from the data sheet.

After digging some more, I decided that it is super ugly out there, as you find that there are a significant number of LCD controllers that are clones, copies, pirated etc… and that they all present themselves differently.  And, in hindsight I think that this is the reason that my ILI9341 from the previous article doesnt quite work correctly.

At this point I have spent a frightening amount of time figuring out how these screens work.  Although it has been a good learning experience, I have generally decided that using unknown displays from China with LCD drivers of questionable origin is not worth the pain of trying to sort out the interface.  Beyond that:

Btw. I think that is what is all about! After the turn off sequence, the display must be turn off by shutting the power. That is what is in Figure 75 of the specs (LGDP4532 v0.12), "Turn the power supply off (Vcc, Vci, IOVcc)" after the power off sequence. So the display is perfectly fine, just needs additional hardware care to turn it off.

Hi community, i have Wemos Lolin32, and a TFT display recognized by id 0x4532 (mcufriend 2.4 inch TFT LCD shield). I have connected just RS to 15, CS to 33 and RST to 32, but the display is very dark. I found the wiring to be this:

my question is, do GPIO33 and GPIO34 have to be connected both to LCD_CS? Same for RST--32--36, RS--15--35. I"m worried that connecting two pins (15-35 for example) may kill my hardware (like short circuit it), if i don"t understand the comments correctly, even that is directly written. I"m new in hardware. Is it "ok" to connect all this pins together? Please help.

I have one of these TFT LCD shields, but mine is a ILI9335. It has taken me nearly 2 weeks to find a working Library and code for my 9335 driver and I am now setting about creating sketches based around my working Library.

One major issue: the LCD driver seems not to be ILI9341. After trying many libraries for Arduino I checked the web address on the back of LCD PCB, the mcufriend. From there I found a couple of links to library files for 2.4 inch LCD. The library which worked for my LCD is MCUFRIEND_kbv, but that is not all... the library has a sketch named "diagnose_TFT_support", which reported via terminal that the LCD chip ID is 0x9595, which means that the line "#define SUPPORT_8347D" must be uncommented in MCUFRIEND_kbv.cpp file in library folder (see mcufriend_how_to.txt file for explanation). Thats it, my LCD works, even the touch panel.

Actually a cheap color display has lot of advantages over any other type displays. Monochrome graphic LCD display actually costs same. Other options of cheap display is Nokia 5110 Display (which is often reported by many users as buggy), standard 1602A LCD Display (which is an all purpose standard basic LCD display). Here is Getting Started Guide For Arduino TFT Touch Screen Shield Manufactured by MCUFRIEND. This is possibly the cheapest 2.4″ color display for Arduino. It costs around $8 to $10. MCUFriend is a China company and has an useless website. However, all over the web, there is huge support for this cheap display. The display works as intended. I purchased it from physical shop. It is a 2.4″ diagonal LCD TFT display, has white-LED backlight, resistive touchscreen, 240×320 resolution, has SPFD 5408 controller with built in video RAM buffer, has 8 bit digital interface and 4 control lines, it uses digital pins 5-13 and analog 0-3. there is a micro SD card reader.

Made in China cheap stuffs usually means made from recycled electronics parts (in case you are not aware). The disgusting part of this screen is the odd red colored PCB delivering a cheap feel. I noticed that one corner slightly get warm after some time. However, peoples could use this display quite effectively.

Obviously! Except China none can give such thing at that price. Commonly with a microcontroller like Arduino, we are not going to do huge graphic intensive works unlike Raspberry Pi. You can save the money for Raspberry Pi’s good display. Our basic usage commonly will be making clock, calculator, showing some tracing from sensor, temperature humidity and so on. This quality of display usually enough.

Hi, the schematic of this display is similar to mine and shows at header JP3 the Arduino Uno power header. Do you know if this 3.3V on this TFT shield/board is actual used. In the schematic it is shown as a label but is not connected to any one. It can not be connected to schematic internal 3.3V coming form the regulator because this would mean a short cut between two power sources. My feeling is that is and auxiliary power source for a non installed chip that I have on my board. Since that chip is not installed it looks like its not needed.

I ask this because I want to use this TFT with a Arduino nano which doesn’t have much 3.3v power on that pin. If it is used i need to implement and extra 3.3V regulator, if not its not needed.