tft display interface with stm32 price

Established in 2015, Shenzhen Hongshuyuan Technology Co.,Ltd.(LAFVIN) is a professional manufacturer and exporter that is concerned with design, development and production of aduino board,sensor modules,robot car,3d printer etc. STEM items.

IMPORTANT The touchscreen has a maximum frequency of 2MHz, which is probably slower than you want your TFT SPI clock. So in the routine that reads touch coordinates (ili9341_touch_pressed_t ili9341_touch_coordinate(ili9341_t *,uint16_t *,uint16_t *) in ILI9341/ili9341.c), make sure to adjust the lines that modify the SPI clock so that your baud rate is less than 2MHz before communicating with the touchscreen (e.g. MODIFY_REG(lcd->spi_hal->Instance->CR1, SPI_CR1_BR, SPI_BAUDRATEPRESCALER_128)), and then restored to whatever setting you use here immedaitely afterwards. See the comments in that source file for both locations.

If using the touchscreen, you will probably want to set Hardware NSSP=Disabled (slave/chip-select) in favor of a software implementation, since you will need one signal for the TFT and a separate one for the touchscreen. Any two unused GPIO digital output pins will work.

Add a Memory->Peripheral DMA TX request for your SPI device with PeriphInc=Disabled, MemInc=Enabled, PeriphDataAlignment=Byte, MemDataAlignment=Byte, Mode=Normal.

IMPORTANT If using FreeRTOS, you will need to raise the DMA interrupt priority to something logically higher (numerically lower) than the FreeRTOS idle thread priority. For example, if FreeRTOS priority is set to 3 and SPI DMA TX is configured as DMA1 channel 4, set DMA IRQ priority to 2 with HAL_NVIC_SetPriority(DMA1_Channel4_IRQn, 2, 0).

If using the touchscreen, be sure to configure the GPIO pin as external interrupt (EXTI) with rising/falling edge trigger detection (i.e. GPIO_InitStruct.Mode = GPIO_MODE_IT_RISING_FALLING).

This solution delivers a comprehensive offer enabling advanced and cost effective Graphical User Interfaces (GUI) on display resolution up to QVGA(320x240) and typically in form factors from 1.5 to 2.5 inches.

Different STM32 can be used to handle the GUI for such resolutions. The STM32G0 and STM32F0 represents the entry cost solution offering simple SPI display and SPI flash interfaces and enabling simple user interfaces. The STM32F412 MCU enables higher UI capabilities thanks to Quad SPI NOR Flash extension possibility and parallel 8080 display interface. The STM32F429 completes the offer bringing Chrom-ART 2D graphic acceleration and LCD-TFT embedded controller. TouchGFX and Advanced graphic partners solutions take the full benefit of STM32 hardware and bring the needed performance, advanced effects and ease of use to enable state of the ART user interfaces in embedded devices

Before I start, I want to mention that I did not write this code. This is a PORT from the mcufriend’s arduino code, which can be found HERE. I merely made some changes, so that it can be used with the CubeMx with a little modifications.

Now comes the part for setting up the Pins for the display. As, we are using the parallel connection, there are 8 DATA Pins and 5 CONTROL Pins. It would be really easy, if you connect all the data pins to thesame PORTand in the same order.

According to the Setup, the LCD_D2 is connected to the PA15. So if I want to write the DATA to the LCD_D2 pin, first I will select the 2nd bit of the data (d & (1<<2)), and than shift this by 13 using <<13. This will be like adding 2 with 13 to make a total of 15, and that’s where the LCD_D2 is connected to.

After all the Pins work is done, we still need to select the delays according to our clock frequency. As I am using STM32F103C8 at72 MHz, I am going to uncomment the respective code as shown below.