Command-line Setup for STM Boards
Assuming that the prerequisites are installed, the following subsections provide instructions to set up your environment using the command line.
To get started from the command line, make the following changes to
- Add STM32CubeProg install directory to
System PATHif it is not installed in the default location.
ST-LINK_gdbserver.exedirectory to your
<STM32_CUBE_IDE_INSTALL_PATH>is the Cube IDE install path.
Note: STM32CubeIDE is optional and required only for on-chip debugging purposes.
This page uses
QUL_TOOLS in command line examples as if they were set as environment variables. For example:
export QUL_ROOT=$HOME/Qt/QtMCUs/2.6 export QUL_TOOLS=$HOME/Qt/Tools/QtMCUs
set QUL_ROOT=C:\Qt\QtMCUs\2.6 set QUL_TOOLS=C:\Qt\Tools\QtMCUs
Configure the following CMake variables. For more information, see the CMake Manual.
|Qul_ROOT||Set the |
Note: This CMake variable is intentionally mixed-case since it needs to match the package name.
|QUL_PLATFORM||The platform name must indicate the board and the OS you want to target. It's a combination of the chosen board's name and the OS you are targeting. The platform name in the following example indicates that your target is |
Note: If you want to target another board or OS, refer to Supported platforms for more information.
|Absolute path to the FreeRTOS sources directory. It is required for FreeRTOS targets only. Refer to FreeRTOS platforms for more information about boards on FreeRTOS.|
-DFREERTOS_DIR=< FreeRTOS directory path >
|CMAKE_TOOLCHAIN_FILE||For example, set it to the Arm GCC toolchain configuration file.
|QUL_TARGET_TOOLCHAIN_DIR||QUL_TARGET_TOOLCHAIN_DIR cmake cache entry needs to be used to provide the location of the used toolchain.|
|QUL_BOARD_SDK_DIR||For example, set it to the STM32F769I SDK install path|
|QUL_COLOR_DEPTH||The color depth supported by the platform you have chosen. For example, set it to 16-bit.|
Note: If this variable is not set, default color depth is used while configuring for the platform.
Note: In a Qt Quick Ultralite project,
CMAKE_BUILD_TYPE is set to
MinSizeRel by default.
MinSizeRel is the build type used for the prebuilt platform libraries shipped with Qt Quick Ultralite. To change the build type (to
Release for example), invoke CMake with the
-DCMAKE_BUILD_TYPE=Release option. For more information, see CMAKE_BUILD_TYPE.
The following command builds the
minimal example for the
STM32F469I discovery board:
cd $QUL_ROOT/examples/minimal mkdir build cd build cmake .. -G "Ninja" -DCMAKE_BUILD_TYPE=MinSizeRel -DQul_ROOT=$QUL_ROOT -DCMAKE_TOOLCHAIN_FILE=$QUL_ROOT/lib/cmake/Qul/toolchain/armgcc.cmake -DQUL_TARGET_TOOLCHAIN_DIR=$QUL_TOOLS/arm_gcc_10 -DQUL_BOARD_SDK_DIR=$QUL_TOOLS/STM/STM32Cube_FW_F4_V1.27.1 -DQUL_PLATFORM=STM32F469I-DISCOVERY-baremetal cmake --build .
cd %QUL_ROOT%\examples\minimal mkdir build cd build cmake .. -G "Ninja" -DCMAKE_BUILD_TYPE=MinSizeRel -DQul_ROOT=%QUL_ROOT% -DCMAKE_TOOLCHAIN_FILE=%QUL_ROOT%\lib\cmake\Qul\toolchain\armgcc.cmake -DQUL_TARGET_TOOLCHAIN_DIR=%QUL_TOOLS%\arm_gcc_10 -DQUL_BOARD_SDK_DIR=%QUL_TOOLS%\STM\STM32Cube_FW_F4_V1.27.1 -DQUL_PLATFORM=STM32F469I-DISCOVERY-baremetal cmake --build .
Once you have successfully built the
minimal example application, use the following command to flash it:
cmake --build . --target flash_minimal
The same procedure applies to other STM boards that are supported by Qt Quick Ultralite.
Available under certain Qt licenses.
Find out more.