SPRAD57 August   2022 TDA4VM

 

  1.   Abstract
  2.   Trademarks
  3. 1Jacinto™ 7 Safety Architecture Concepts
    1. 1.1 Safety Architectural Overview: MCU Island and Extended MCU Island
    2. 1.2 Implementing Mixed Criticality - Freedom from Interference (FFI)
  4. 2Overview of Safety Mechanisms
  5. 3Implementation of Safety in Your System
    1. 3.1 Hardware Collateral
    2. 3.2 Software Support

Overview of Safety Mechanisms

For system level safety, robust hardware diagnostics for basic operations are layered with system and software diagnostic to meet random fault integrity metrics on the SoC. There are three basic categories of diagnostic coverage:

  • Hardware safety mechanisms: Once enabled, these mechanisms operate continuously.
    • Examples of this include but are not limited to: SECDED ECC and Parity for memories and interconnect, PLL slip and loss of lock detection, over/under-voltage detection.
  • Hardware + Software safety mechanisms: These mechanisms depend on hardware but require periodic software interaction to initiate or maintain the operation.
    • Examples of this include but are not limited to: watchdog timers, CRC hardware support for checks of memory and registers, dual clock comparators.
  • Software safety mechanisms: These mechanisms are based on software performing some test and checking the results.
    • Examples of this include but are not limited to: Information redundancy techniques, transmission redundancy, software test of basic functionality. Implementation of these mechanisms are usually dependent on customer application and use case.

GUID-23561C6F-FB34-44B4-BA4C-858CC9E2AE2E-low.jpg Figure 2-1 Select Diagnostics on TDA4VM

Figure 2-1 demonstrates some safety mechanisms that can be implemented in the SoC (based of TDA4VM). This diagram is for informational purposes only and is not all inclusive. Please refer to SoC specific Safety Reference Manual for in depth descriptions of the diagnostics as well as for SOC specific modules and peripherals.