Figure 8. Firewall Configuration Constraint On Dual Bank Products; Figure 9. Firewall Configuration After Bank Swap - ST X-CUBE-SBSFU STM32Cube Integration Manual

Expansion package
Hide thumbs Also See for X-CUBE-SBSFU STM32Cube:
Table of Contents

Advertisement

AN5056

Figure 8. Firewall configuration constraint on dual bank products

For the STM32G0 Series, STM32G4 Series, and STM32H7 Series, one constraint exists:
the header of the active slot must be mapped just after the SBSFU code to be protected by
the secured memory.
The SFU_IMAGE_OFFSET value depends on the STM32 microcontroller series:
For the STM32L4 Series, STM32L0 Series, STM32L1 Series, STM32WB Series, and
STM32F4 Series, the default value is used: 512 bytes.
For the STM32F7 Series and STM32H7 Series: 1024 bytes.
(With the Cortex
For the STM32G0 Series: 2048 bytes.
The secure user memory end address is aligned on the Flash sector size.
For the STM32G4 Series: 4096 bytes.
The secure user memory end address is aligned on the Flash sector size.
For the STSAFE-A variant: 2048 bytes.
The image header has a 2048-byte length to include X509 certificates.

Figure 9. Firewall configuration after bank swap

®
-M7, the vector table must be aligned on 1024 bytes).
AN5056 Rev 8
Porting X-CUBE-SBSFU onto another board
15/49
48

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the X-CUBE-SBSFU STM32Cube and is the answer not in the manual?

Table of Contents

Save PDF