C

Supported target boards and development hosts

Qt Quick Ultralite supports a variety of microcontroller-based hardware platforms that are available in the market. Currently supported boards are listed below. Click the board name in the table for information on how to get started with the board.

Note: The tables below list the reference (Tier 1) and verified (Tier 2) target boards. For information on other (Tier 3) targets, see Other supported target boards.

Qt for MCUs can be ported to any modern microcontroller that is capable of driving a display. If your hardware is not listed, contact us for an estimation of the porting effort, or follow the Qt Quick Ultralite Platform Porting Guide to port Qt Quick Ultralite to this hardware.

Support levels for target hardware

There are multiple levels of support that apply across specific hardware and OS combinations.

Tier 1: Reference targets

  • Issues on this reference target are given a higher priority than lower tier targets.
  • Maintained for the entire 2.x series.
  • Upgraded to support all Qt Quick Ultralite features when possible.
  • Covered by Standard Qt Support.
  • Releases are available via Qt Online Installer.

The reference target boards are listed in the following table, grouped by vendor.

Hardware boardMCUCompilerOperating system(s)
MIMXRT1050-EVKBMIMXRT1052DVL6BGNU Arm GCC 12.3.rel1, IAR Build Tools for Arm V9.40Bare Metal, FreeRTOS
MIMXRT1064-EVKMIMXRT1064DVL6AGNU Arm GCC 12.3.rel1, IAR Build Tools for Arm V9.40FreeRTOS, Zephyr
MIMXRT1170-EVKBMIMXRT1176DVMAAGNU Arm GCC 12.3.rel1, IAR Build Tools for Arm V9.40FreeRTOS
Hardware boardMCUCompilerOperating system(s)
RH850/D1M1A Evaluation BoardRH850/D1M1A (R7F701461)Green Hills MULTI 7.1.6, Compiler 2015.1.7 or 2018.1.5AUTOSAR Classic Platform, Bare Metal
Hardware boardMCUCompilerOperating system(s)
STM32H750B-DISCOVERYSTM32H750XBGNU Arm GCC 12.3.rel1, IAR Build Tools for Arm V9.40Bare Metal
Hardware boardMCUCompilerOperating system(s)Host(s)
TRAVEO T2G Cluster 4M Lite KitCYT3DLIAR Functional Safety Build Tools for Arm 8.22.3, Green Hills MULTI Compiler for Embedded ARM 2017.1.4Bare MetalWindows host only
TRAVEO T2G TVII-C-2D-6M Evaluation KitCYT4DNIAR Functional Safety Build Tools for Arm 8.22.3, Green Hills MULTI Compiler for Embedded ARM 2017.1.4Bare MetalWindows host only

Note: Infineon TRAVEO T2G prebuilt libraries are built using the GHS 2017.1.4 compiler. To use a different compiler version you have to rebuild the Qt Quick Ultralite libraries. See Building Qt Quick Ultralite from sources for more information.

Tier 2: Verified targets

Note: Tier 2 platforms will be supported in the upcoming 2.10.1 patch release.

The verified target boards are listed in the following table, grouped by vendor.

Hardware boardMCU / MPUCompilerOperating system(s)
MIMXRT1060-EVKBMIMXRT1060DVL6B MCUGNU Arm GCC 12.3.rel1, IAR Build Tools for Arm V9.40BareMetal, Zephyr
MCIMX93-EVKi.MX 93 MPUGNU Arm GCC 12.3.rel1Linux
Hardware boardMCUCompilerOperating system(s)
EK-RA8D1 (Technology Preview)R7FA8D1BHECBDGNU Arm GCC 12.2.MPACBTI-Rel1Bare Metal
Hardware boardMCUCompilerOperating system(s)
STM32F769I-DISCOVERYSTM32F769NIGNU Arm GCC 12.3.rel1, IAR Build Tools for Arm V9.40Bare Metal, FreeRTOS
Hardware boardMCUCompilerOperating system(s)Host(s)
TRAVEO T2G TVII-C-2D-4M Evaluation KitCYT3DLIAR Functional Safety Build Tools for Arm 8.22.3, Green Hills MULTI Compiler for Embedded ARM 2017.1.4Bare MetalWindows host only
TRAVEO T2G TVII-C-2D-6M_LITE Lite KitCYT4DNIAR Functional Safety Build Tools for Arm 8.22.3, Green Hills MULTI Compiler for Embedded ARM 2017.1.4Bare MetalWindows host only

Note: Infineon TRAVEO T2G prebuilt libraries are built using the GHS 2017.1.4 compiler. To use a different compiler version you have to rebuild the Qt Quick Ultralite libraries. See Building Qt Quick Ultralite from sources for more information.

Supported features

NXP 1050NXP 1060NXP 1064NXP 1170MCIMX93-EVK
Hardware accelerated blitting
- Alpha8HW 5HW 5HW 5HWSW
- Alpha1SWSWSWSWSW
- RGB332SWSWSWSWSW
- ARGB4444HWHWHWHW 3
- RGB565HWHWHWHW 3
- RGB888SWSWSWHWSW
- ARGB8888HWHWHWHW 3
- RLE_ARGB8888SWSWSWSWSW
- RLE_RGB32n/an/an/an/an/a
- RLE_RGB888HW 6 7HW 6 7HW 6 7SWSW
Hardware accelerated basic shapes 1
- Rectangle 3 3 3 1
- Rounded rectangle
Layers
- ItemLayer
- SpriteLayer
- ImageLayer
Monotype Spark
Multiple screens 1
Shapes (vector graphics) 14 14 14 14
Touch
Transformations
- TranslateHWHWHWHWHW
- Uniform scaleSWSWSWHWSW
- ScaleSWSWSWHWSW
- RotationSWSWSWHWSW
- Scale rotationSWSWSWHWSW
- ShearSWSWSWHWSW
- ProjectSWSWSWHWSW
Font quality
- VeryHighSWSWSWHWSW
- VeryLowSWSWSWSW
Framebuffers
Double buffering 16
Single buffering 9 9 9 9
Partial buffering 15 15 15
32 bpp color depth 11 11 11
24 bpp color depth 11 11 11
16 bpp color depth 12
  • Feature is supported by the platform adaptation
  • 1 Platform library has to be rebuilt
  • 1 Feature is supported by the hardware, but not implemented in the reference platform adaptation
  • 2 Feature is partially supported by the hardware, but not implemented in the reference platform adaptation
  • 3 Blended as an image that is rendered by the CPU
  • 4 Feature is supported by the hardware but self intersecting paths are not supported
  • 5 Hardware blending via an intermediate ARGB8888 buffer
  • 6 Accelerated blending when opacity != 1 is used
  • 7 Source images are decompressed into small intermediate buffers chunk by chunk before blending
  • 8 The reference board has limited available memory, so by default single buffering is used. This comes with a certain risk of visual flickering if the application contents are expensive to render
  • 9 Single buffering is supported by the hardware, although it is likely to cause visual flickering. For this reason it's not implemented in the reference platform adaptation
  • 10 Single buffering is supported by the hardware without any visual flickering, since the display contains its own framebuffer memory. It does however come with a significant performance cost. The reference platform adaptation needs modifications to enable the single buffering support
  • 11 The board families support 24 bpp and 32 bpp framebuffers, but the reference boards have only 16 lines physically connected to the LCD interface, so only 16 bpp is supported
  • 12 These color depths are available using the ItemLayer API, but not by using QUL_COLOR_DEPTH
  • 13 TRAVEO T2G specific hardware accelerated RLE format is used
  • 14 Feature is supported by software
  • 15 Feature could be supported if the display has dedicated framebuffer memory, but it is not implemented in the reference platform adaptation
  • 16 Currently only the LinuxFB render backend is supported, and an offscreen buffer is used in addition to the main framebuffer to reduce flickering artifacts.
  • Feature is not supported by the hardware
  • HW is short for hardware accelerated blending
  • SW is short for software based blending

Supported target runtime environments and operating systems

With Qt for MCUs, applications can run on bare metal. Additionally, the following target runtime environments and operating systems are supported:

If you need to run applications on other target operating systems, contact The Qt Company.

Supported development hosts

The development hosts supported by Qt for MCUs are:

  • Windows 10 64-bit
  • Ubuntu 22.04 LTS 64-bit

Running applications on host platforms

Qt Quick Ultralite applications can be run on host platforms to avoid having to flash the board too often and save time during development, or when a board is not available. The supported configurations are:

Operating SystemArchitectureCompiler
Windows 10x86_64MSVC 2019, MinGW 11.2
Ubuntu 22.04 LTSx86_64GNU Arm GCC 10, GNU Arm GCC 11, GNU Arm GCC 12, GNU Arm GCC 13

If you need to run applications for other host architectures or operating systems, build and install a custom Qt platform library. See Building Qt Quick Ultralite platform library against the evaluation packages for more information.

Available under certain Qt licenses.
Find out more.