4.9Project Manager view

This view (see Figure 101) comes with three tabs:

•General project setting: to specify the project name, location, toolchain, and firmware version.

•Code generation: to set code generation options such as the location of peripheral initialization code, library copy/link options, and to select templates for customized code.

•Advanced settings: dedicated to ordering STM32CubeMX initialization function calls.

Figure 101. Project Settings window

The code is generated in the project folder tree shown in Figure 102.

Figure 102. Project folder

4.9.1 Project tab

The Project tab of the Project Settings window allows configuring the following options (see Figure 101):

• Project settings:

– Project name: name used to create the project folder and the .ioc file name at a given project location

– Project location: directory where the project folder is stored.

– Application structure: select between Basic and Advanced options.

Basic structure: recommended for projects using one or no middleware. This structure consists in placing the IDE configuration folder at the same level as the sources, organized in sources and includes subfolders (see Figure 103)

Advanced structure: recommended when several middleware components are used in the project, makes the integration of middleware applications easier (see

Figure 104)

– Toolchain folder location: by default, it is located in the project folder at the same level as the .ioc file.

– Toolchain/IDE: selected toolchain

– For the STM32MP1 series only, OpenSTLinux settings: location of generated device tree and manifest version and contents for current project (see Figure 105). These information enable the synchronization of the right SW components versions with STM32CubeMP1 for Cortex® M and Linux, tf-a, u-boot for

Cortex® A. It is important to take them into account especially to ensure one Cube firmware version is aligned with SW components for Cortex® A around OpenAMP / RPM link and resource management API.

Selecting Makefile under Toolchain/IDE leads to the generation of a generic gcc-based makefile.

•Additional project settings for STM32CubeIDE toolchain:

Select the optional Generate under root checkbox to generate the toolchain project files in STM32CubeMX user project root folder or deselect it to generate them under a dedicated toolchain folder.

STM32CubeMX project generation under the root folder allows the user to benefit from the following Eclipse features:

–Optional copy of the project into the Eclipse workspace when importing a project.

–Use of source control systems such as GIT or SVN from the Eclipse workspace.

Choosing to copy the project into workspace prevents any further synchronization between changes done in Eclipse and changes done in STM32CubeMX, as there will be two different copies of the project.

•Linker settings: value of minimum heap and stack sizes to be allocated for the application. The default values proposed are 0x200 and 0x400 for heap and stack sizes, respectively. These values may need to be increased when the application uses middleware stacks.

•Firmware package selection when more than one version is available (this is the case when successive versions implement the same API and support the same MCUs). By default, the latest available version is used.

•Firmware location selection option

The default location is the location specified under the Help > updater settings menu.

Deselecting the Use Default Firmware Location checkbox allows the user to specify a different path for the firmware that will be used for the project (see Figure 106).

Figure 103. Selecting a basic application structure

Figure 105. OpenSTLinux settings (STM32MP1 series only)

Figure 106. Selecting a different firmware location

The new location must contain at least a Drivers directory containing the HAL and CMSIS drivers from the relevant STM32Cube MCU package. An error message pops up if the folders cannot be found (see Figure 107).

Figure 107. Firmware location selection error message

To reuse the same Drivers folder across all projects that use the same firmware location, select the Add the library files as reference from the Code generator tab allows (see Figure 108).

Figure 108. Recommended new firmware repository structure