Getting started on NXP
This topic provides all the necessary information to get started on the NXP platforms supported by Qt Quick Ultralite.
Assuming that you have all the prerequisites installed, follow these instructions configure the Qt Creator IDE for NXP boards:
To develop for MCUs using the Qt Creator IDE, the MCU plugin is required. The Qt online installer enables it by default when you install the Qt for MCUs SDK.
To enable or disable the plugin, follow these instructions:
- Select Help > About Plugins and choose the MCU Support plugin from the list.
- Restart Qt Creator to apply changes
To build and run your application on MCUs, you must create a kit:
- Select Edit > Preferences > Devices > MCU
- If not already set, provide the path to the Qt for MCUs installation directory.
- Select a Target supported by the Qt for MCUs SDK. For example, Qt for MCUs 2.3 - Desktop 32bpp.
- In the Requirements section, ensure that the platform-specific requirements are met.
- Select Automatically create kits for all available targets on start to create kits automatically.
Note: You could also manually create/remove kits using Create Kit and Remove Kit.
- Click Apply and restart Qt Creator if you choose to create kits automatically.
Note: The Automatically create kits for all available targets on start option is available from Qt Creator v4.14 onwards. On older versions of Qt Creator, you have to explictly create or remove kits using Create kit or Remove kit.
You could also set up the development environment from the command prompt. See Command-line Setup for NXP Boards for more information.
Flashing and debugging NXP boards requires the board to have the OpenSDA firmware. If an incorrect firmware is flashed, the tools may fail to establish connection with the device.
To check the firmware, connect your device to your development host and open the provided USB storage device. In the
DETAILS.TXT file, look for the line starting with "USB Interfaces". It has to list "CDC" and "HID". If these are missing, you are probably using an incorrect firmware.
NXP provides the firmware for download. On the download page, select the type of your type of board and download the "Default firmware application, DAPLink". After flashing this to your board by following the instructions from NXP, the CDC and HID interface should be listed.
Open the CMake project file for the example you want to build and configure it with the kit you created earlier. Once the project is configured, select Run or press Ctrl+r on your keyboard to build and flash the binary to the target.
|Hardware board||MCU||Compiler||Operating system(s)|
|MIMXRT1050-EVKB||MIMXRT1052DVL6B||GNU Arm GCC 10.3-2021.10, IAR Build Tools for Arm V9.20||Bare Metal, FreeRTOS|
|MIMXRT1060-EVK||MIMXRT1060DVL6A||GNU Arm GCC 10.3-2021.10, IAR Build Tools for Arm V9.20||Bare Metal|
|MIMXRT1064-EVK||MIMXRT1064DVL6A||GNU Arm GCC 10.3-2021.10, IAR Build Tools for Arm V9.20||Bare Metal, FreeRTOS|
|MIMXRT1170-EVK||MIMXRT1176DVMAA||GNU Arm GCC 10.3-2021.10, IAR Build Tools for Arm V9.20||FreeRTOS|
By default, an application's resource data is copied to SDRAM on startup. In order to retain these resources in flash and not load them to RAM on startup, add the following CMake option to your CMake project file:
Alternatively, it can be enabled only for individual images like this:
set_source_files_properties( big/button.png PROPERTIES QUL_RESOURCE_CACHE_POLICY "NoCaching" )
Note: Set these CMake options before the qul_add_resource entry.
Available under certain Qt licenses.
Find out more.