Flexible Static Memory Controller (Fsmc); Table 98. Fsmc_Sm_0; Table 99. Fsmc_Sm_1 - ST STM32F2 Series User Manual

3.6.25

Flexible static memory controller (FSMC)

SM CODE
Description
Ownership
Detailed implementation
Error reporting
Fault detection time
Addressed fault model
Dependency on MCU configuration
Initialization
Periodicity
Test for the diagnostic
Multiple faults protection
Recommendations and known
limitations
SM CODE
Description
Ownership
Detailed implementation
Error reporting
Fault detection time
Addressed fault model
Dependency on MCU configuration
Initialization
Periodicity
Test for the diagnostic
Multiple faults protection
Recommendations and known
limitations
UM1845 - Rev 4
Table 98. FSMC_SM_0
FSMC_SM_0
Control flow monitoring in application software
End user
If FSMC is used to connect an external memory containing software code to be executed by the CPU,
permanent and transient faults affecting the FSMC memory controller are able to interfere with the
access operation by the CPU, leading to wrong data or instruction fetches. A strong control flow
mechanism linked to a system watchdog is able to detect such failures, in case they interfere with the
expected flow of the application software.
The implementation of this method is identical to the one reported for CPU_SM_1, refer there for details
Depends on implementation
Depends on implementation. Higher value is fixed by watchdog timeout interval
Permanent and Transient
FSMC interface is available only on selected part numbers
Depends on implementation
Continuous
N/A
CPU_SM_0: Periodical core self test software
This mechanism must be used just if FSMC external memory is used to store executable programs
Table 99. FSMC_SM_1
FSMC_SM_1
Information redundancy on external memory connected to FSMC
End user
If FSMC interface is used to connect an external memory where safety-relevant data are stored,
information redundancy techniques for stored data are able to address faults affecting the FSMC
interface. The possible techniques are:
To use redundant copies of safety relevant data and perform coherence check before consuming.
To organize data in arrays and compute the checksum field to be checked before use
Depends on implementation
Depends on implementation
Permanent and Transient
FSMC interface is available only on selected part numbers
Depends on implementation
On demand
Not needed
CPU_SM_0: Periodical core self test software
This mechanism must be used just if FSMC external memory is used to store safety-related data.
This safety mechanism can overlap with information redundancy techniques implemented at system
level to address failure of physical device connected to FSMC port
Description of hardware and software diagnostics
UM1845
page 67/108