Table 26. Ram_Sm_5 - ST STM32F2 Series User Manual

SM CODE
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
RAM_SM_4
NA
CPU_SM_0: periodical core self-test software
Needed just in case of application software execution from SRAM.
CPU_SM_1 correct implementation supersedes this requirement
Table 26. RAM_SM_5
RAM_SM_5
Periodical integrity test for application software in RAM
End user
In case application software or diagnostic libraries are executed in RAM, it is needed to protect the
integrity of the code itself against soft-error corruptions and related code mutations. This method must
check the integrity of the stored code by checksum computation techniques, on a periodic basis (at
least once per PST). For implementation details refer to similar method FLASH_SM_0
Depends on implementation
Depends on implementation
Permanent and Transient
None
Depends on implementation
Periodic
Self-diagnostic capabilities can be embedded in the software, according the test implementation
design strategy chosen.
CPU_SM_0: periodical core self test software
CPU_SM_1: control flow monitoring in application software
This method must be implemented only in case of application software or diagnostic libraries are
executed from RAM
Description of hardware and software diagnostics
UM1845
page 24/108