Figure 3. Linker File Architecture - ST X-CUBE-SBSFU STM32Cube Integration Manual

AN5056
The linker file definitions shared between the three projects (SECoreBin, SBSFU, UserApp)
are grouped in the Linker_Common folder as presented in
•
mapping_fwimg.icf: contains firmware image definitions such as active slots, download
slots, and swap area
• mapping_sbsfu.icf: contains SBSFU definitions such as SE_Code_region,
SE_Key_region, and SE_IF_region
•
mapping_export.h: export the symbols from mapping_sbsfu.icf and mapping_fwimg.icf
to the SBSFU applications
Each region can be extended when adding more code is needed or shifted to another
address as long as the resulting security settings satisfy security requirements.
The security peripheral configuration (RDP, WRP, PCROP, FWALL, secure user memory if
available for the series) is automatically computed based on the SBSFU linker symbols
except for MPU configuration due to the following constraints:
•
each MPU region base address must be a multiple of the MPU region size.
• each MPU region can be divided into 8 sub-regions to adjust the size.
The mapping constraints with MPU isolation are illustrated in
Porting X-CUBE-SBSFU onto another board

Figure 3. Linker file architecture

AN5056 Rev 8
Figure 3:
Figure 4.
11/49
48