For each board, a set of examples is provided with preconfigured projects for EWARM, MDK-ARM, and

STM32CubeIDE toolchains.

Figure 5 shows the project structure for the NUCLEO-U575ZI-Q board.

Figure 5. STM32CubeU5 examples overview

The examples are classified depending on the STM32Cube level that they apply to, and are named as explained

below:

•

Level 0 examples are called "Examples", " Examples_LL", and "Examples_MIX". They use, respectively,

HAL drivers, LL drivers, and a mix of HAL and LL drivers without any middleware component.

•

Level 1 examples are called applications. They provide typical use cases of each middleware component.

Any firmware application for a given board can be built quickly using the template projects available in the

Templates and Templates_LL directories.

4.2.1

TrustZone-enabled projects

TrustZone-enabled “Examples” names are prefixed with "_TrustZone". This rule is also applied to “Applications”

(except TFM, which is native to TrustZone®).

TrustZone-enabled “Examples” and “Applications” are provided with a multiproject structure, composed of secure

and nonsecure subprojects, as presented below in Figure 6.

TrustZone-enabled projects are developed according to the CMSIS-5 device template, extended to include the

system partitioning header file partition_<device>.h. This file is responsible for the principal setup of the secure

attribute unit (SAU), the FPU, and the secure/nonsecure interrupts assignment in a secure execution state.

UM2883

STM32CubeU5 MCU package overview

UM2883 - Rev 4

page 12/30