1. Create a project

To create a new project, start either from the template project, provided for each board in \Projects\<STM

32xxx_yyy>\Templates, or from any available project in \Projects\<STM32xxy_yyy>\Examples or \

Projects\<STM32xx_yyy>\Applications (where <STM32xxx_yyy> refers to the board name, such as

STM32CubeU5).

The template project provides only an empty main loop function, which is a good starting point to understand

the STM32CubeU5 project settings. The template has the following characteristics:

–

It contains the HAL source code, CMSIS, and BSP drivers that are the minimum set of components

required to develop code on a given board.

–

It contains the include paths for all the firmware components.

–

It defines the supported STM32U5 series devices, allowing the correct configuration of the CMSIS and

HAL drivers.

–

It provides ready-to-use user files that are preconfigured as shown below:

◦

HAL initialized with default time base with Arm® core SysTick.

◦

SysTick ISR implemented for HAL_Delay() purpose.

Note:

When copying an existing project to another location, make sure all the include paths are updated.

2. Add the necessary middleware to the project (optional)

To identify the source files to be added to the project file list, refer to the documentation provided for each

middleware component. Refer to the applications in \Projects\STM32xxx_yyy\Applications\<MW_Sta

ck> (where <MW_Stack> refers to the middleware stack, such as USBX) to know which source files and

include paths must be added.

3. Configure the firmware components

The HAL and middleware components offer a set of build time configuration options, using macros (#define)

declared in a header file. A template configuration file is provided within each component that has to be copied

to the project folder (usually the configuration file is named xxx_conf_template.h, and the word

"_template" needs to be removed when copying it to the project folder). The configuration file provides enough

information to understand the impact of each configuration option. More detailed information is available in the

documentation provided for each component.

4. Start the HAL library

After jumping to the main program, the application code must call the HAL_Init() API to initialize the HAL

library, which carries out the following tasks:

a. Configuration of the flash memory prefetch and SysTick interrupt priority (through macros defined in stm3

2u5xx_hal_conf.h).

b. Configuration of the SysTick to generate an interrupt every millisecond at the SysTick interrupt priority

TICK_INT_PRIORITY, defined in stm32u5xx_hal_conf.h, which is clocked by the MSI (at this stage,

the clock has not been configured yet and the system is running from the 4 MHz MSI).

c. Setting the NVIC group priority to 0.

d. Calling the HAL_MspInit() callback function defined in the stm32u5xx_hal_msp.c user file to perform

global low-level hardware initializations.

UM2883

Getting started with STM32CubeU5

UM2883 - Rev 4

page 19/30