STM32F469I Discovery Kit
- STM32F469NIH6 microcontroller featuring ARM® Cortex®-M4 core and 324 Kbytes of RAM
- 4” TFT Color LCD Touch Display
- 128-Mbit SDRAM
- 128-Mbit QSPI NOR Flash
Supported color depths
The reference port for this board supports 16bpp and 24bpp (default) color depths. The board also supports 32bpp, but it is not implemented in the reference port. See QUL_COLOR_DEPTH and Color depth for more information.
Note: The prebuilt platform library is provided for default 24bpp only. For 16bpp color depth, rebuild the platform library with QUL_COLOR_DEPTH value set to 16. See Building Qt Quick Ultralite platform library against the evaluation packages to build platform from sources.
Partial framebuffer support
This board supports the partial framebuffer strategy. To enable it, set QUL_PLATFORM_ENABLE_PARTIAL_FRAMEBUFFER and rebuild the Platform library.
Using the partial framebuffer can significantly lower the memory requirements of an application, but can lead to reduced performance and potential visual tearing artifacts for complex applications.
Note: Qt Quick Ultralite uses double partial framebuffer for 16bpp color depth, and single partial framebuffer for 24bpp color depth.
Prebuilt demos and examples
STM32F469I-DISCO board is provided with following prebuilt demos:
You can flash them onto the device using images from the
demos_images folder. Follow the flashing instructions for ST boards, and use
STM32469I-DISCO as the board name and
N25Q128A_STM32469I-DISCO as the external loader script.
Reading debug messages
By default, the output of
printf calls is redirected to a virtual serial port, which is exposed on the host machine via USB.
The reference port utilizes the STMicroelectronics Chrom-Art Accelerator™ (DMA2D) for hardware accelerated graphics.
DMA2D is a specialized direct memory access (DMA) accelerator dedicated to image manipulation. It can perform the following operations:
- Fill an image with a specific color.
- Copy a source image into a destination image.
- Copy a source image into a destination image with a pixel format conversion.
- Blend two complete source images, each with a different pixel format, and copy the result into a destination image with a different pixel format.
All of the listed operations can be done to a part or whole image.
For more information, refer to STMicroelectronics' documentation:
- STM32F7 - Chrom-ART™ (applies also for the STM32F4 series).
- RM0386 Reference manual section Chrom-Art Accelerator™ controller (DMA2D).
For more information about the STM32F469NIH6 MCU-specific peripherals mentioned below, refer to STMicroelectronics' documentation:
Note: In the following sections both low layer (LL) and hardware abstraction layer (HAL) refer to the STM32Cube abstraction layers.
The hardware configuration for the
STM32F469I-DISCO board is comprised of STM32CubeMX generated code and peripheral BSP drivers from the repository for
STM32Cube MCU Package for STM32F4 series.
All the STM32CubeMX generated code (except the system clock configuration is located in the
System clock configuration
The system clock configuration is located in the Qt Quick Ultralite platform source file
SystemClock_Config() function is declared weak, so that it can be overridden by a custom clock configuration.
System timer configuration
The TIM6 timer instance is configured as the timebase source in the Qt Quick Ultralite platform source file
stm32f469i-discovery-baremetal/3rdparty/Core/Src/stm32f4xx_hal_timebase_tim.c with the
The low layer (LL)
SysTick_Handler() function is defined in the Qt Quick Ultralite platform source file
The low layer (LL) processor exception and peripheral interrupt handlers are defined in
The hardware abstraction layer (HAL) interrupt handlers for the display serial interface host (DSI) interrupt callbacks, and the touch interrupt pin callback are defined in the
stm32f469i-discovery-baremetal/platform_irq.cpp Qt Quick Ultralite platform source file.
Chrom-ART Accelerator (DMA2D)
The DMA2D configuration is defined in the
platform/boards/st/common/platform_drawing.cpp Qt Quick Ultralite platform source file.
The nested vectored interrupt controller (NVIC) and clock configuration for DMA2D are defined in the STM32Cube MCU package repository file,
You can find the LCD-TFT display controller (LTDC) and display serial interface host configuration settings in the
stm32f469i-discovery-baremetal/platform_display.cpp Qt Quick Ultralite platform source file.
You can use the
setLcdClockConfiguration() function to give the clock settings for LTDC.
The LTDC clock enabling and GPIO configuration settings are defined in the STM32Cube MCU package repository file,
Quad serial peripheral interface (QSPI)
For the QSPI configuration, check
BSP_QSPI_Init() for peripheral settings and
QSPI_MspInit() for pinout/clock configuration from the STM32Cube MCU package repository file
The QSPI is configured to memory-mapped mode in the Qt Quick Ultralite platform source file
Random number generator (RNG)
You can find the random number generator (RNG) initialization in Qt Quick Ultralite platform source file
The clock configuration for the RNG hardware instance is located in
The SDRAM BSP configuration is located in the STM32Cube MCU package repository file
The touch panel configuration is located in the STM32Cube MCU package repository file
The touch panel driver IC is connected to the I2C1 hardware instance and the touch interrupt signal is connected to the GPIOJ pin 5.
The I2C1 configuration is in a function called
I2C1_Init(), which is located in the STM32Cube MCU package repository file
The USART3 hardware instance is used for logs over the virtual COM port. The USART3 configuration including GPIO and clock settings is located in the Qt Quick Ultralite platform source file
STM32F469NI does not have double-precision floating-point support.
Due to limited SDRAM bandwidth, accessing SDRAM with the CPU may cause visual artifacts while the framebuffer is being scanned by the display controller, due to LTDC FIFO Underrun.
LTDC FIFO Underrun has also been observed in applications with heavy animations, even when the SDRAM is not accessed directly from the CPU. It might help to use a different build type or to simplify the animations.
The CPU on this board cannot blend compressed images directly onto the framebuffer in SDRAM. Such images are decompressed into intermediate buffers of a limited size, before blending them using DMA2D onto the framebuffer in SDRAM. This approach has a significant performance overhead to blend RLE-compressed images compared to the uncompressed images.
Performance can be improved to some degree by increasing the size of qul_scratch_buffer in platform_stm32.cpp, at the cost of more RAM usage.
Available under certain Qt licenses.
Find out more.