3.6.16 General-purpose input/output (GPIO) - port A/B/C/D/E/F/G/H/I
Table 72. GPIO_SM_0
SM CODE GPIO_SM_0
Description Periodical read-back of configuration registers
Ownership End user
Detailed implementation
This method must be applied to GPIO 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 GPIO availability can differ according to part number
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 73. GPIO_SM_1
SM CODE GPIO_SM_1
Description 1oo2 for input GPIO lines
Ownership End user
Detailed implementation
This method addresses GPIO lines used as inputs. Implementation is done by connecting the
external safety-related signal to two independent GPIO lines. Comparison between the two GPIO
values is executed by application software each time the signal is used to affect application software
behavior
Error reporting Depends on implementation
Fault detection time Depends on implementation
Addressed fault model Permanent and Transient
Dependency on MCU configuration None
Initialization Depends on implementation
Periodicity On demand
Test for the diagnostic Not needed
Multiple faults protection CPU_SM_0: periodical core self-test software
Recommendations and known
limitations
To reduce the potential impact of common cause failure, it is recommended to use GPIO lines:
• Belonging to different i/o ports (for instance PORT A and B)
• With different bit port number (for instance PORTA.1 and PORTB.5)
• Mapped to non-adjacent pins on the device package
Table 74. GPIO_SM_2
SM CODE GPIO_SM_2
Description Loopback scheme for output GPIO lines
UM1845
Description of hardware and software diagnostics
UM1845 - Rev 4
page 52/108
To Next Page
Loading...
