Commmand-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, ensure that the following these instructions:
Qul_DIRto the Qt for MCUs SDK install path.
<QT_INSTALL_PATH>is the Qt install directory,
<VERSION>is the directory containing the Qt Quick Ultralite version you are using, for example
- Toolchain install path, depending on which toolchain is being used
- For the armgcc toolchain, set
ARMGCC_DIRto the ARM Toolchain install path.
- For the IAR toolchain, set
IAR_ARM_COMPILER_DIRto the IAR Build Tools install path.
- For the armgcc toolchain, set
- Add the CMake and Ninja tools to your system
PATH. If you installed these tools using the Qt online installer, they are installed under
- 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.
- Create an environment variable and set its value to the path of the board SDK. The name of this variable varies depending on the board in use. For example, use the
STM32Cube_FW_F7_SDK_PATHname for the STM32F769I board:
where, <QT_INSTALL_PATH> is the Qt install directory.
The following is a list of the environment variables and the corresponding ST board(s), which depend on the variable:
Configure the following CMake variables. For more information, see the CMake Manual.
|QUL_PLATFORM||The platform must be set to the corresponding board and the OS you plan to use. For example, set the variable for |
|CMAKE_TOOLCHAIN_FILE||For example, set it to the armgcc compiler.|
|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.
|QUL_COPY_TO_RAM||By default, the asset data for application is copied to SDRAM on application startup. In order to keep resources in external flash, and not load it to RAM on startup, use the QUL_COPY_TO_RAM CMake option with the value |
Note: STM32F469i Discovery board is equipped with a fast external flash, which can be used to store assets that are used for blending/blitting operations, without the need to copy those into RAM.
The following command builds the
minimal example for the
STM32F469I discovery board:
cd $Qul_DIR/examples/minimal mkdir build cd build cmake .. -G "Ninja" -DCMAKE_BUILD_TYPE=Release -DCMAKE_TOOLCHAIN_FILE=$Qul_DIR/lib/cmake/Qul/toolchain/armgcc.cmake -DQUL_PLATFORM=STM32F469I-DISCOVERY-baremetal cmake --build .
cd %Qul_DIR%\examples\minimal mkdir build cd build cmake .. -G "Ninja" -DCMAKE_BUILD_TYPE=Release -DCMAKE_TOOLCHAIN_FILE=%Qul_DIR%\lib\cmake\Qul\toolchain\armgcc.cmake -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.