tft lcd interface with microcontroller brands

This note will discuss the considerations made when choosing a microcontroller that will work for your display. A few requirements need to be met depending on the display’s features, interface, and size. These can also be determined by the embedded IC in the display. An overview of the considerations when choosing a microcontroller can be seen below. It should be noted that these items are separated for definition but may serve the same purpose and be interconnected in the ecosystem of the controller.

Flash and RAM memory requirements. Minimum frame buffer memory is dependent on the size andresolution of the display. Location of memory (external or internal) can restrict interface speed and must becompatible with the chosen interface.

Communication speed requirements defined by the interface and intended application. Refresh rateis determined on the size of the display and location of memory. This will indicate which processors arecompatible.

Availability of resources for programming and debugging the microcontroller. Online resources andexampleprograms to leverage from can a lot of save time. Compatibility with a familiarprogramming environment isadditionally beneficial.

The interface selection is dependent on the intended application of the display. Each display has a different interface or different choices for a connection interface. For smaller displays a 3/4-wire serial interface would be sufficient. For larger display’s with high resolution a faster interface should be chosen. A parallel RGB interface is capable of high-speed data transmission however requires many pin connections. If the intended application for the display is video a MIPI, LVDS or HDMI connection would be a good choice.

The available memory of a microcontroller often becomes a highlighted issue when determining which microcontroller to select. The microcontroller needs a minimum amount of RAM to hold the frame buffer of the display. Even small displays require more RAM than a typical microcontroller possess. To verify that your microcontroller will have enough memory, it is important to calculate the frame buffer.

The minimum RAM required for the frame buffer in this example would then be 768kB. It is important to note that external RAM can be provided for the frame buffer if the microcontroller does not provide it internally. Clocking speed should be verified if using external RAM as the microcontroller cannot access external RAM as quickly. The clock frequency constrained by external RAM sometimes does not meet the minimum requirements of some very high-speed interfaces (ex. DSI-MIPI). Additionally, the display can contain some form of RAM depending on the IC controller inside the display. This can be verified on the specification sheet of the IC.

The speed of the microcontroller is heavily dependent on the interface used in the application. The minimum and maximum of the clock frequency is specified in the datasheet of the display and in the specification sheet of the display’s controller IC. The frame rate is typically around 50-60Hz, which is the median oscillation frequency to refresh the display to maintain an image. The display will often provide an internal high frequency clock that can be initialized to certain frequencies.

It is important to verify in the controller data sheet which resources are provided by the internal IC of the display. Some key information to look for would be: Does the display have sufficient RAM or does this need to be provided? Does the display have an internal oscillator for clock generation for the interface chosen? An additional graphics controller can be used to interface the display with the microcontroller to meet these requirements. Features like these can be utilized to avoid additional cost, space, and memory of your application.

After a brief consideration of intended application and interface of the display you can get some idea of which microcontroller processor and architecture you will need. There are a few different microcontroller processors to choose from. The main choices are ARM, AVR, PIC, and 8051. The difference between them is the bit size of the processor, 8-bit, 16-bit, 32-bit or 64-bit data . The data bit width is the amount of data that can be sent at a time. This determines the speed of data transfer and thus compatible applications and interfaces.

The AVR has an 8-bit processor and is a RISC type microcontroller. This type of processor is compatible with low speed interfaces (SPI, I2C) and smaller displays. A common AVR microcontroller board is the Arduino which has the embedded 8-bit ATMEL RISC processors. These processors are widely popular which provide the benefit of numerous online resources and availability. The Arduino processors (ATmega/SAM3X) are typically available in most microcontroller programming environments. Additionally, Arduino offers 32-bit AVR development boards which function closely to the ARM processors.

The AVR microcontrollers are constrained by the low frequency, internal memory availability and power costs. AVR’s cannot use external program memory but some may allow expansion of external SRAM. These microcontrollers alone would be incompatible for high frequency applications such as video, large displays, or capacitive touch panels.

The ARM microprocessors have a RISC architecture. They offer 32-bit or 64-bit processors and are great options for high speed interfaces (Parallel, LVDS, MIPI, HDMI) and high-resolution displays. Common ARM processors can be found from STMicroelectronics and Raspberry Pi. The most common version of the ARM processors is the “Microcontroller” Arm-M group which include the Cortex-M0 and Cortex-M4 series.

The ARM processors are compatible with most displays and connection interfaces. These microcontrollers have become increasingly popular, so the cost has become comparable between the ARM and the AVR types. These processors provide the speed, but it is recommended to verify the available RAM as these boards vary widely on included features.

The PIC architecture consists of 8, 16, and 32-bit processors developed by Microchip. The PIC 32-bit series of microcontrollers have been geared toward graphical embedded applications and there are a lot of resources online for these devices. There is a huge variety of PIC controllers which make them easily available. These microcontrollers are known for being low cost and are comparable to the ARM processors. The drawback of the PIC controllers is using Microchips programming environment, but this is based on preference.

The Intel MCS-51, more commonly known as the 8051 microcontrollers have a CISC architecture and an 8-bit processor. These processors differ in architecture from the previous and are programmed using a combination of C and assembly languages. The program memory is read only and does not have an on-board ISP. A special programming device is needed to rewrite the EEPROM or flash memory. These processors are typically small, low cost and low powered. This can make them favorable for battery powered devices. These processors are commonly used to initialize TFT displays and are combined with a graphics controller to provide the required resources such as RAM and clock frequency.

Development environments and online resources become considerably valuable when creating an application for your display. A brand new or uncommon microcontroller will have very few resources for reference. Even knowledgeable engineers can find frustrations with the manufacturers programming environments. There are many microcontroller choices that will support your display with similar and overlapping features. Choosing a microcontroller with an available FAQ, application notes or is accessible on a familiar programming platform can save a lot of time.

Buyers and others who are developing systems that incorporate FocusLCDs products (collectively, “Designers”) understand and agree that Designers remain responsible for using their independent analysis, evaluation and judgment in designing their applications and that Designers have full and exclusive responsibility to assure the safety of Designers" applications and compliance of their applications (and of all FocusLCDs products used in or for Designers’ applications) with all applicable regulations, laws and other applicable requirements.

Designer agrees that prior to using or distributing any applications that include FocusLCDs products, Designer will thoroughly test such applications and the functionality of such FocusLCDs products as used in such applications.

The display used in this project is a 1.8” TFT with 128x160 pixels of resolution. The microcontroller used is the SimpleLink MSP-432P401R from Texas Instruments. The TFT display will be interfaced with the microcontroller via a 4-wire serial connection and programmed using the Energia IDE platform.

In just a few steps the TFT can be wired and programmed to display up to 65K colors and 128x160 pixels of resolution. The display can be powered from the 3.3V output of the TI. Various wiring and interface options are available, from 3-4 wire serial, to 16/18-bit RGB and 8/9/16/18-bit MCU parallel. Additional features of this display are below. As always, check out the data sheet for the specs of this specific display. (datasheet)

First you will need to download the Energia IDE software if you have not already. This IDE was chosen because of the similarities is has to the Arduino IDE. This is beneficial because there is a large variety of open sourced examples that demonstrate the features of this display. An alternative programming IDE is Code Composer Studios, which is also compatible with the TI microcontroller. The IDE is up to preference. We will come back to this after the hardware is setup.

There are only a few connections that need to be made between the display for the 4-wire serial interface. The unused parallel data pins will be pinned to GND. Consult the datasheet for a detailed explanation of each pin assignment and their functions. The 4-wire serial data pins are connected to the TI specific serial inputs for the “Hardware SPI” programming option. While any pins can be used, their location must be defined in the “Software SPI” programming option.

Pin definitions and connection points are described in the table below. We will use the 4-wire serial interface for this example to save data pins on the TI. A more in-depth description of each of the pins can be found on thedatasheet. All unused pins are connected to ground, with the exception of the reset pin. This pin is optional to connect to the TI, if not used it needs to be pulled high.

The TI microcontroller has dedicated serial input pins specific to the board. The pin locations can be seen below and are described in the table for how they are connected to the display. These and other hardware pin definitions can be verified on the TI website.

After the screen is connected, and the TI microcontroller is plugged into the computer you will see the white LED backlight come on. That is a good sign that things are connected correctly.

Now it is time to program the microcontroller. For this example, we will be using the Energia IDE. An alternative platform that can be used is Code Composer Studios. I have found that Energia IDE is more practical for this example because of the compatibility with Arduino specific code with only minor changes.

You will also need to include Adafruit’s GFX library which can be downloaded here. This is a popular library that contains examples and features for TFT displays that prove to be useful for this application.

This 1.8” TFT is a good option for displaying 16-bit 65K color images. This is compatible with most microcontrollers as it saves on-board memory. This is beneficial for storing bitmaps on flash memory since the screen is small and the 65K color bitmap image won’t take up all the on-board storage on the TI. This display also has a version with a resistive touch screen. This would be a good option for a digital push button. This may be further discussed in a future application note.

Buyers and others who are developing systems that incorporate FocusLCDs products (collectively, “Designers”) understand and agree that Designers remain responsible for using their independent analysis, evaluation and judgment in designing their applications and that Designers have full and exclusive responsibility to assure the safety of Designers" applications and compliance of their applications (and of all FocusLCDs products used in or for Designers’ applications) with all applicable regulations, laws and other applicable requirements.

Designer agrees that prior to using or distributing any applications that include FocusLCDs products, Designer will thoroughly test such applications and the functionality of such FocusLCDs products as used in such applications.

The display is a critical component in every project, impacting the case, firmware, electrical design, user interface, and even battery life. For these reasons, and because it is the most visible component of your product, it must be approved by the mechanical design team, management and marketing.Before these teams can approve, they need to see it in action. But it can take days or weeks to connect a display to your platform, initialize it and build a code library able to create believable demonstrations. Meanwhile, the whole project is on hold.Our 8051 development kit / demonstration board can solve this problem. Use it to get the display seen, demonstrated and approved for your project.

ER-DBTM080-2 is a microcontroller 8051(80C51) demonstration and development kit for ER-TFTM080-2 product that is 8 inch tft lcd display with RA8875 controller board.The kit includes MCU board controlled by STC12LE5A60S2,ISP(In System Programming) with USB port and cable to customize the demonstration that includes your own bitmap images,personalized fonts,symbols,icons and burn sketches,microSD card that is written graphic and text into it,the power adaptor,the adaptor board with various pitch dimension used to connect MCU board and display.Optional for 8080 8/16-bit,6800 8/16-bit parallel interface and I2C,3-wire,4-wire serial interface.

The display is a critical component in every project, impacting the case, firmware, electrical design, user interface, and even battery life. For these reasons, and because it is the most visible component of your product, it must be approved by the mechanical design team, management and marketing.Before these teams can approve, they need to see it in action. But it can take days or weeks to connect a display to your platform, initialize it and build a code library able to create believable demonstrations. Meanwhile, the whole project is on hold.Our 8051 development kit / demonstration board can solve this problem. Use it to get the display seen, demonstrated and approved for your project.

ER-DBT028-4 is a microcontroller 8051(80C51) demonstration and development kit for 2.8 inch tft lcd display with ILI9341 controller.The kit includes MCU board controlled by STC12LE5A60S2,ISP(In System Programming) with USB port and cable to customize the demonstration that includes your own bitmap images,personalized fonts,symbols,icons and burn sketches,microSD card that is written graphic and text into it,the power adaptor,the adaptor board with various pitch dimension used to connect MCU board and display.Optional for 8080 8-bit,8080 16-bit parallel interface and 3-wire,4-wire serial interface.

I have a small 3.5 in TFT LCD display from a Chinese manufacturer. It doesn"t have an integrated LCD controller. The documentation claims it is a "16 bit RGB/parallel interface" and it uses a Renesas R61581B0 driver chip.

These types of displays are very common and cheap. They sell for less than $15 a pop on Alibaba.com, but I don"t really have a high esteem for these manufacturers since they do not provide any good / consistent documentation, and their English is riddled with mistakes! But I did get the display, and the product looks and feels like it will do the job!

My question now is, how do I get started ? I have looked on the internet and cannot find a good starting point. I have a 32MHz microcontroller in mind, but I am stumped on how to interface it with the LCD.

Most display projects online that I"ve seen assume that the LCD module comes with an integrated controller , so the MCU"s job becomes pretty simple.. Provide image updates when necessary, and the controller will do the job of refreshing the LCD module at the required 60hz (or so)

This LCD module that I have has raw data lanes that I need to drive myself at 60hz. Are there any good documents on how to interface an MCU directly with such an LCD module?

I"ll be happy with any info that points me in the right direction, whether it be an answer on stackexchange or a reference to any good documentation online.

μEZ® is an open source, embedded middleware platform providing underlying RTOS and processor abstraction features enhancing portability of application code to multiple ARM and Renesas platforms with high reusability.

FDI BootloaderThe μEZ+ Bootloader is perfect for upgrading your firmware in the field through mediums such as an SD card, USB flash drive, or even over a serial interface such as Ethernet or USB.

Developed in partnership with the world’s leading chip companies over a 12 year period, FreeRTOS is the market leading real time operating system (or RTOS), and the de-facto standard solution for microcontrollers and small microprocessors.

TouchGFX is a unique software framework that unlocks the graphical user interface (GUI) performance of your low-resource hardware. The revolutionizing technology breaks existing restraints, as it lets you create sophisticated GUIs that fully live up to today’s smartphone standards at a fraction of the cost.

emWin is designed to provide an efficient, processor- and LCD controller-independent graphical user interface (GUI) for any application that operates with a graphical LCD. It is compatible with single-task and multitask environments, with a proprietary operating system or with any commercial RTOS. emWin is shipped as “C” source code. It may be adapted to any size physical and virtual display with any LCD controller and CPU.

Micrium is a global RTOS leader and a top choice of embedded engineers building microprocessor, microcontroller, and DSP-based devices. Micrium’s commercial RTOS components such as the μC/OS product family are the preferred solution at thousands of companies around the globe. Offering unprecedented ease-of-use, μC/OS-III is delivered with complete 100% ANSI C source code and in-depth documentation. μC/OS-III runs on the largest number of processor architectures, with ports available for download from the Micrium Web site. µC/OS-III allows for unlimited tasks, semaphores, mutexes, event flags, message queues, timers and memory partitions. µC/OS-III provides features to allow stack growth of tasks to be monitored. µC/OS-III also supports an unlimited number of priority levels. µC/OS-III’s footprint can also be scaled to contain only the features required for a specific application.

Crank™ Software Inc. is an innovator in embedded user interface (UI) solutions. Compared to traditional electronic design automation tools, Crank’s products and services enable R&D teams to more quickly develop rich graphical displays—also called UIs or HMIs—for resource-constrained embedded devices. Applications include in-car graphical displays, animated GPS systems, and rich user interfaces on factory floors. Crank Software bridges the gap between UI design and embedded systems to deliver competitive advantage because streamlining the development lifecycle enables their customers to get products to market faster, with higher ROI and lower TCO, while delivering a superior customer experience. Crank Storyboard™ Designer enables user interface (UI) designers to easily prototype the look and feel of a product, and then deploy a production-ready interface directly to the embedded target. Designers maintain full control over the UI and user experience (UX) without having to perform a hand off to an embedded systems engineer for implementation.

J-Link Product PageSEGGER J-Links are the most widely used line of debug probes available today. They’ve been proven for more than 10 years with over 250,000 units sold, including OEM versions and on-board solutions. This popularity stems from the unparalleled performance, extensive feature set, large number of supported CPUs, and compatibility with all popular development environments.

The SparkFun TFT LCD Breakout is a versatile, colorful, and easy way to experiment with graphics or create a user interface for your project. With a 4-wire SPI interface and microSD card holder, you can use this breakout to easily add visual display/interface capabilities to a project as well as providing all the storage you might need for multimedia files.

To get started with this breakout, you will need an Arduino compatible microcontroller of your choice - we recommend something with extra RAM like the SparkFun Thing Plus. The breakout can be powered with either 5V or 3.3V. The microSD card holder is connected to the same SPI bus as the display which keeps the required pin count low and exists to relieve the burden from your microcontroller"s poor memory due to having to store hundreds of images of cats, or really whatever you want to keep there. We have also gone ahead and tricked out the SparkFun HyperDisplay library with a driver made especially for this breakout!

Out of the box, the SparkFun TFT LCD Breakout will come with a large backing PCB that makes it easy to securely mount the display in a project. If you need a more flexible solution you can remove the display module, snap off half the backing board, and then re-insert the display module. When this is done you"ll be left with the bare minimum frame around the display to more seamlessly integrate with your project.