3.6.7 Controller area network (CAN)
Table 37. CAN_SM_0
SM CODE CAN_SM_0
Description Periodical read-back of configuration registers
Ownership End user
Detailed implementation
This method must be applied to CAN configuration registers.
Detailed information on the implementation of this method can be found in Section 3.6.5
Error reporting Refer to NVIC_SM_0
Fault detection time Refer to NVIC_SM_0
Addressed fault model Refer to NVIC_SM_0
Dependency on MCU configuration Refer to NVIC_SM_0
Initialization Refer to NVIC_SM_0
Periodicity Refer to NVIC_SM_0
Test for the diagnostic Refer to NVIC_SM_0
Multiple faults protection Refer to NVIC_SM_0
Recommendations and known limitations Refer to NVIC_SM_0
Table 38. CAN_SM_1
SM CODE CAN_SM_1
Description Protocol error signals
Ownership ST
Detailed implementation
CAN communication module embeds protocol error checks (like error counters) conceived to detect
network-related abnormal conditions. These mechanisms are able anyway to detect a marginal
percentage of hardware random failures affecting the module itself.
Error signals connected to these checkers are normally handled in a standard communication
software, so the overhead is reduced
Error reporting Several error condition are reported by flag bits in related CAN registers.
Fault detection time Depends on peripheral configuration (e.g. baud rate), refer to functional documentation
Addressed fault model Permanent and Transient
Dependency on MCU configuration None
Initialization Depends on implementation
Periodicity Continuous
Test for the diagnostic NA
Multiple faults protection CAN_SM_2: Information redundancy techniques on messages, including end-to-end safing
Recommendations and known limitations None
Table 39. CAN_SM_2
SM CODE CAN_SM_2
Description Information redundancy techniques on messages, including end-to-end safing
Ownership End user
UM1845
Description of hardware and software diagnostics
UM1845 - Rev 4
page 32/108
To Next Page
Loading...
