SM CODE
FLASH_SM_0
module is recommended. In principle
feature for data transfer can be used.
Unused Flash memory sections can be excluded from testing.
Table 24.
FLASH_SM_1
SM CODE
FLASH_SM_1
Description
Control flow monitoring in
Application software
Ownership
End user
Detailed implementation
Permanent and transient faults affecting the system Flash memory, memory cells and address
decoder, can interfere with the access operation by the
CPU
, leading to wrong data or
instruction fetches.
Such failures can be detected by control flow monitoring techniques implemented in
Application software
loaded from Flash memory.
For more details on the implementation, refer to description CPU_SM_1.
Error reporting
Depends on implementation
Fault detection time
Depends on implementation. Higher value is fixed by watchdog timeout interval.
Addressed fault model
Permanent/transient
Dependency on
Device
configuration
None
Initialization
Depends on implementation
Periodicity
Continuous
Test for the diagnostic
Not applicable
Multiple-fault protection
CPU_SM_0: Periodic core self-test software
Recommendations and known limitations
CPU_SM_1 correct implementation supersedes this requirement.
Table 25.
FLASH_SM_2
SM CODE
FLASH_SM_2
Description
Arm
®
Cortex
®
-M4 HardFault exceptions
Ownership
ST
Detailed implementation
Hardware random faults (both permanent and transient) affecting system Flash memory
(memory cells, address decoder) can lead to wrong instruction codes fetches, and eventually
to the intervention of the Arm
®
Cortex
®
-M4 HardFault exceptions. Refer to CPU_SM_3 for
detailed description.
Error reporting
Refer to CPU_SM_3
Fault detection time
Refer to CPU_SM_3
Addressed fault model
Permanent/transient
Dependency on
Device
configuration
None
Initialization
Refer to CPU_SM_3
Periodicity
Continuous
Test for the diagnostic
Refer to CPU_SM_3
Multiple-fault protection
Refer to CPU_SM_3
Recommendations and known limitations
Refer to CPU_SM_3
UM2305
Hardware and software diagnostics
UM2305
-
Rev 10
page 22/110