Example of configuration using TIM2 as HAL timebase source

When TIM2 is used as HAL timebase source, a new stm32f4xx_hal_timebase_TIM.c file is generated to overload the HAL timebase related functions, including the HAL_InitTick function that configures the TIM2 as the HAL time-base source.

The priority of TIM2 timebase interrupts is set to 0 (High). The SysTick priority is set to 15 (Low) if FreeRTOS is used, otherwise is set to 0 (High).

Figure 83. NVIC settings when using FreeRTOS and TIM2 as HAL timebase

The stm32f4xx_it.c file is generated accordingly:

•SysTick_Handler calls osSystickHandler when FreeRTOS is used, otherwise it calls HAL_SYSTICK_IRQHandler.

•TIM2_IRQHandler is generated to handle TIM2 global interrupt.

4.5Pinout & Configuration view for STM32MP1 series

For the STM32MP1 series the Pinout & Configuration view allows the user to:

•assign components to one or several run time contexts

•configure peripherals as boot devices

•select the peripherals to be managed by boot loaders

•assign GPIOs to one runtime (see Figure 85).

These possibilities are offered in two different panels (see Figure 84)

1.from the component tree panel, that lists all supported peripherals and middleware (the “Show contexts” option must be enabled)

2.from each component mode panel, opened by clicking the component name.

Figure 85. STM32MP1 series: assignment options for GPIOs

4.5.1Run time configuration

The STM32MP1 devices are multi-core (Arm® Cortex®-A7 dual-core and Cortex-®M4) and multi-firmware, each firmware executing on one of the cores. The association between firmware and core defines a runtime context where the firmware executes its code.

Three runtime contexts are available:

1.Cortex-A7 Non Secure running the Linux kernel

2.Cortex-A7 Secure running the SP_min

3.Cortex-M4 running the STM32Cube firmware.