SFFS779 December 2024 TMS320F28P550SJ
Hardware redundancy techniques can be applied using hardware, or as a combination of hardware and software, to provide runtime diagnostic. In this implementation, redundant hardware resources are utilized to provide diagnostic coverage for elements within and outside (wiring harness, connectors, and transceiver) the TMS320F28P55x MCU.
In case of peripherals like GPIO, XBAR, PWM, OTTO, DAC, CMPSS, and XINT, hardware redundancy can be implemented by having multichannel parallel outputs (where independent outputs are used for transmitting information and failure detection is carried out using internal or external comparators) or input comparison and voting (comparison of independent inputs to comply with a defined tolerance range, time and value). In such scenarios, the system can be designed so the failure of one input or output does not cause the system to go into a dangerous state. While servicing the error conditions (redundancy conditions), as in two redundant sources tripping the PWM, always read back the status flags and verify that both sources are active while tripping and thus providing latent fault coverage for the trip logic.
In case of peripherals like ADC, ECAP, EQEP, and so forth, hardware redundancy can be implemented by having multiple instances of the peripheral sample the same input and simultaneously perform the same operation followed by a cross check of the output values.
In case of communication peripherals like MCAN, SPI, SCI, and so forth, hardware redundancy during signal reception can be implemented by having multiple instances of the peripheral receive the same data followed by a comparison to verify data integrity. Hardware redundancy during transmission can be employed by having a complete redundant signal path (wiring harness, connectors, and transceiver) from the transmitter to the receiver or by sampling the transmitted data by a redundant peripheral instance followed by a data integrity check.
While implementing hardware redundancy for ADC and DAC modules, additional care must be taken to verify common-cause failures do not impact both instances in the same way. Reference voltage sources, configured for redundant module instances, must be independent. Additionally, ADC SOC trigger sources, used for redundant ADC instances, must be configured to different PWM module instances. In case of a DAC module, the comparator can be implemented using an external device.
While implementing hardware redundancy for the PWM module, TI recommends that the PWM module instance used is part of separate sync chains. This requirement is to avoid a common-cause failure on a sync signal that affects both PWM modules in the same way.
While implementing hardware redundancy for the GPIO module, TI recommends using GPIO pins from different GPIO groups to avoid common-cause failures.