How to start with Secure Manager default configuration on STM32H5

This message will disappear after all relevant tasks have been resolved.

Semantic MediaWiki

There are 1 incomplete or pending task to finish installation of Semantic MediaWiki. An administrator or user with sufficient rights can complete it. This should be done before adding new data to avoid inconsistencies.

Target description

The purpose of this article is to explain step by step how to use the Secure Manager provided in the STM32Cube_FW-H5, using the STM32H57 discovery board.
This how to start is using the default configuration provided in the STM32Cube_FW_H5.
If you want to modify the default configuration, please refer to the How_to_start_with_Secure_Manager_customized_config_on_STM32H5 article.

But it is strongly advised to start with this practical example before starting to customize your solution.
Especially if you want to regenerate some keys, you need to understand the implications and store these keys preciously.

Introduction

Start by reading the Secure_Manager_STM32H5_How_to_Intro article.
For technical background, please refer to the Secure_Manager_for_STM32H5 article.

Prerequisites

Hardware
- STM32H573 discovery board: the STM32H573 devices have all the available security features, including the HW crypto accelerator. (Note: the Secure Manager is not supported for STM32H56x devices, the HW crypto is not available)
- Discovery MB1677- STM32H573 (need USBC cable)

Figure 1 STM32H573 DK MB1677.png

Required tools
- STM32Cube_H5_V1.1.0 with Le STM32Cube_H5_V1.1.1 patch, or later
- STM32CubeProgrammer_rev2.14.0 or more recent (with STM32TrustedPackageCreator (TPC) selected at installation).
- One of the supported IDE: EWARM, MDK_ARM or STM32CubeIDE
- Tera Term / Putty or equivalent UART terminal emulator.