- Products
Development Framework & Tools
-
Qt Framework Cross-platform software libraries and APIs
-
Qt Development tools Qt Creator IDE and productivity tools
-
Qt Design Studio UI Design tool for UI composition
-
Qt Quality Assurance for Qt projects
-
Qt Digital Ads Digital advertising for UI apps
-
Qt Insight Usage intelligence for embedded devices
- Qt product updates
-
Qt 6 The latest version of Qt
Quality Assurance Tools
- Solutions
We have solutions for your entire cross-platform software development lifecycle.
- Which platform are you targeting?
-
Desktop and Mobile Applications
-
Embedded devices
-
Microcontrollers (MCUs)
- At what stage is your project?
-
Planning and resourcing
-
Designing UI and prototyping
-
Developing, compiling and coding
-
Testing and debugging
-
Deploying and maintaining
- What do you want to improve?
-
Scalable software and UI development
-
User-Centric UX/UI Design
-
Virtual Qt World
-
- Which industry needs are you looking to optimize?
-
Automotive design
-
Industrial automation
-
Consumer electronics creation
-
Medical device development
- What is your main responsibility in your current role?
-
Managing a team
-
Developing apps or embedded solutions
-
UI design and prototyping
-
Quality assurance and testing
- Resources
Development Framework and Tools
- The latest Qt resources
-
Qt Blog
-
Live Webinars and Events
-
Qt Customer cases
-
Qt Demos
-
All Qt resources
- Learn Qt tools
-
Get started with Qt
-
Browse courses and tutorials
-
Get Qt Educational license
- Connect with Qt community
-
Qt Documentation
-
Qt Forum
-
Qt Wiki
-
Contribute to Qt
-
Qt Partners
-
Login to your Qt account
Design Studio, Qt Creator etc.
Quality Assurance Tools
Login to your QA account
Other known-to-work target devices for Qt for Device Creation
Verified QBSP Targets
The target hardware and operating system combo where:
- Target device OS source code is available.
- Building target is documented and/or
- There is a Qt Board Support Package (QBSP) file available and it has been constructed as per instructions and policies: https://doc.qt.io/QtForDeviceCreation/b2qt-how-to-create-b2qt-image.html
In short, a QBSP verification has been carried out either by the QBSP provider or the Qt Company (TQC) release management. Please note that the Qt community may also provide support for a target. Additionally, the QBSP test bench can be used by partners to get a target into list after test result validation by TQC.
The supported targets are typically using embedded Linux, in particular Yocto builds of Poky. In addition to Embedded Linux versions such as Poky, also Real Time Operating Systems (RTOS) are supported by Qt versions, most notably QNX, INTEGRITY. Although the QBSP packaging concept is generic and allows various packages to be used, is not currently used with RTOS but is for Linux only.
Note that this table may be updated outside the usual Qt Release time frames.
| Vendor | Model | QBSP Supplied By | Development Host | Target Os | Qt Release |
| Intel |
NUC10 |
The Qt Company |
Windows |
Yocto 4.0 |
6.2 |
| Nvidia | Jetson TX2 | The Qt Company | Windows Linux |
Yocto 4.0 Embedded Linux |
6.2 |
| NXP | i.MX 8M Nano DDR4 EVK | The Qt Company | Windows Linux |
Yocto 4.0 Embedded Linux |
6.2 |
| NXP | i.MX 8MQuad EVK | The Qt Company | Windows Linux |
Yocto 4.0 Embedded Linux |
6.2 |
| Raspberry Pi | Raspberry Pi 4 | The Qt Company | Windows Linux |
Yocto 4.0 Embedded Linux |
6.2 |
| Toradex | Apalis iMX8 | The Qt Company | Windows Linux |
Yocto 4.0 Embedded Linux |
6.2 |
|
Boundary Devices |
i.MX6 | The Qt Company | Windows Linux |
Yocto 3.1 Embedded Linux |
5.15.6 |
| NXP | i.MX7 Solo WaRP | The Qt Company | Windows Linux |
Yocto 3.1 Embedded Linux |
5.15.6 |
| NXP | i.MX 8QuadMax MEK | The Qt Company | Windows Linux |
Yocto 3.1 Embedded Linux |
5.15.6 |
| NXP | i.MX 8MQuad EVK | The Qt Company | Windows Linux |
Yocto 3.1 Embedded Linux |
5.15.6 |
|
Raspberry Pi |
Raspberry Pi3 Model B | The Qt Company | Windows Linux |
Yocto 3.1 Embedded Linux |
5.15.6 |
|
Raspberry Pi |
Raspberry Pi4 Model B | The Qt Company | Windows Linux |
Yocto 3.1 Embedded Linux |
5.15.6 |
| Toradex | Apalis iMX8 | The Qt Company | Windows Linux |
Yocto 3.1 Embedded Linux |
5.15.6 |
| Toradex | Colibri iMX6 | The Qt Company | Windows Linux |
Yocto 3.1 Embedded Linux |
5.15.6 |
| Toradex | Colibri iMX6 ULL | The Qt Company | Windows Linux |
Yocto 3.1 Embedded Linux |
5.15.6 |
| ST |
STM32MP157 DK |
The Qt Company |
Windows Linux |
Yocto 4.0 Embedded Linux |
6.3 |
| ST | STM32MP157 Eval |
The Qt Company |
Windows Linux |
Yocto 4.0 Embedded Linux |
6.3 |
| TI |
AM62xx |
The Qt Company |
Windows Linux |
Yocto 3.1 Embedded Linux |
5.15.11 |
| TI |
AM62xx |
The Qt Company |
Windows Linux |
Yocto 4.0 Embedded Linux |
6.5 (Pre-version, some limitations apply) |
Qt Community Targets
There is a large number of working targets that have been made without the involvement of the Qt Company Engineering organisation. These targets fall into three main categories:
- They are supported by TQC under the Device Creation License, or have a verified QBSP.
- The Qt Company Professional Services have assisted in porting Qt to the target platform.
- Do It Yourself (DIY) targets where a working OS/HW platform combination has been constructed from either source code or by using the Yocto project, BuildRoot, LinuxLink or a similar system.
Please see the table below for examples of targets that have been tested against one or more Qt releases (non-exhaustive list including targets known to work as well as Partner or TQC Verified QBSPs or TQC Supported Targets.). Note that this table may be updated outside the usual Qt Release time frames.
| Vendor | Model | SoC | GPU |
| BeagleBone | BeagleBone Black | TI AM335x | PowerVR SGX530 |
| Boundary Devices | Boundary Devices i.MX6 Boards | NXP i.MX 6 | Vivante GC2000 |
| Boundary Devices Nitrogen7 | NXP i.MX 7 | N/A | |
| Boundary Devices Nitrogen8M | NXP i.MX 8MQuad | Vivante GC7000Lite | |
| Boundary Devices Nitrogen8M Mini | NXP i.MX 8M Mini | Vivante GCNanoUltra | |
| Garz & Fricke | Garz & Fricke | NXP i.MX 6 | Vivante GC2000 |
| Hilscher | NETX 4000 | Hilscher netX 4000 | N/A |
| Intel | Intel NUC | Atom, Celeron, i3, i5, i7 | Intel Graphics |
| Intrisyc | SA8155P Automotive Development Platform | Qualcomm Snapdragon 8155P | Qualcomm Adreno |
| S820Am v2 Automotive Development Platform | Qualcomm Snapdragon 820 | Qualcomm Adreno | |
| Kontron | Kontron SMARC-sAMX6i | NXP i.MX 6 | Vivante GC2000 |
| NVIDIA | NVIDIA DRIVE CX | NVIDIA Tegra X1 | NVIDIA Maxwell |
| NVIDIA Drive PX 2 | NVIDIA Tegra X2 | NVIDIA Pascal | |
| NVIDIA Driver PX Xavier | NVIDIA Drive Xavier | NVIDIA Volta | |
| NVIDIA Jetson TX1 | NVIDIA Tegra X1 | NVIDIA Maxwell | |
| NVIDIA Tegra X2 | NVIDIA Pascal | ||
| NXP | NXP iMX8M Nano | NXP i.MX 8M Nano | Vivante GC7000Lite |
| NXP i.MX8M Mini | NXP i.MX 8M Mini | Vivante GC Nano Ultra | |
| NXP iMX8M Quad | NXP iMX 8MQuad | Vivante GC7000Lite | |
| NXP i.MX8QuadMax | NXP i.MX 8QuadMax | Vivante GC7000 | |
| NXP SABRE Board for Smart Devices | NXP i.MX 6 | Vivante GC2000 | |
| NXP Warp 7 | NXP i.MX 7 | N/A | |
| Qualcomm | Qualcomm Snapdragon 820D | Qualcomm Snapdragon 820 | Qualcomm Adreno |
| Qualcomm Snapdragon 8155P | Qualcomm Snapdragon 8155P | Qualcomm Adreno | |
| Raspberry Pi | Raspberry Pi 4 B | Broadcom BCM2711 | VideoCore 6 |
| Raspberry Pi 3 B+ | Broadcom BCM283B | VideoCore 4 | |
| Raspberry Pi 3 B | Broadcom BCM283x | VideoCore 4 | |
| Raspberry Pi 2 Model B | Broadcom BCM283x | VideoCore 4 | |
| Raspberry Pi Model B | Broadcom BCM283x | VideoCore 4 | |
| Renesas | Renesas E2 | Renesas R-Car E2 | PowerVR SGX540 |
| Renesas E2 | Renesas R-Car E2 | PowerVR GE8300 | |
|
Renesas D3 |
Renesas R-Car D3 | PowerVR Series8XE GE8300 | |
| Renesas H3 Salvator-X/XS | Renesas R-Car H3 | PowerVR Series6XT GX6650 | |
| Renesas M3 Salvator XS | Renesas R-Car M3 | PowerVR Series6XT GX6250 | |
| ST | STM32MP157A | STM32MP1 | Vivante GCNano |
| TechNexion | PICO-IMX8M-MINI | NXP i.MX 8M Mini Solo, NXP i.MX 8M Mini Dual, NXP i.MX 8M Mini Quad | Vivante GC Nano Ultra |
| PICO-IMX8M | NXP i.MX 8M QuadLite, NXP i.MX 8M Quad | Vivante GC7000Lite | |
| PICO-IMX7 | NXP i.MX 7 Solo, NXP i.MX 7 Dual | N/A | |
| PICO-IMX6 | NXP i.MX 6 Solo, NXP i.MX 6 DualLite, NXP i.MX 6 Quad | Vivante GC2000 | |
| Texas Instruments | Sitara AM335x Starter Kit | TI AM335x | PowerVR SGX530 |
| Toradex | Apalis iMX6 | NXP i.MX 6 | Vivante GC2000 |
| Colibri iMX6ULL | NXP i.MX 6ULL | N/A | |
| Toradex Apalis iMX8 | NXP i.MX 8 | Vivante GC7000 | |
| Toradex Colibri iMX8X | NXP i.MX 8X | Vivante GC7000Lite | |
| Toradex Colibri iMX6 | NXP i.MX 6 | Vivante GC2000 | |
| Toradex Colibri VF50 | NXP Vybrid | N/A | |
| Toradex Colibri VF61 | NXP Vybrid | N/A |
Additional Target Hardware for Device Creation Enterprise
Everything in Device Creation Professional licence is included also in Device Creation Enterprise licence. However you need a Device Creation Enterprise license for The Qt Company to provide support for the following target device and operating system combinations. Additionally for MCU, to use the hardware and operating systems combinations in the table below, you need to purchase the Device Creation Enterprise licence. All MCU hardware-operating system combinations below may not be fully supported today.
| Supported Hardware | Operating System | Supported Qt Version | Comment |
| Renesas R-Car series: E2,E3,D3,H3 Salvator-X/XS, M3 Salvator-X/XS | Yocto | Qt 6.2, Qt 5.15 | B2Qt supported |
| Qualcomm: SA8155P, SA6155P | AAOS11/12, INTEGRITY 19.03, QNX 7.1 | Qt 6.2 | B2Qt support not available |
| NXP: iMX8QM | QNX 7.1 | Qt 6.2 | iMX8 with Yocto is included in DCP licence |
| NXP: MIMXRT1170-EVK (MCU) |
Autosar | QUL 2.x |
RT1170 with FreeRTOS included in DCP licence |
| Renesas RH850 all variants (MCU) |
Bare Metal, Autosar |
Qt for MCUs 2.x |
|
| Traveo II all variants (MCU) | Bare Metal, Autosar |
Qt for MCUs 2.x |
Windows host only |
| Renesas R-Car series Cortex-R (MCU) |
Bare Metal, Autosar | Qt for MCUs 2.x |
|
| NXP iMX8QM with Cortex-M4 (MCU) |
Bare Metal, Autosar |
Qt for MCUs 2.x |
|
QBSP Test Bench
QBSP test bench is a test suite (tool) run locally in partner host machine.
The test cases run by the tool are also available as a document. They are based on selected Qt Company RTA tests.
The test bench is intended to provide reliable test results for QBSP validation, once results are validated the new board can be listed in the validated QBSP section in documentation on this page.