SFFS022 December   2022 TMS320F28384D , TMS320F28384D-Q1 , TMS320F28384S , TMS320F28384S-Q1 , TMS320F28386D , TMS320F28386D-Q1 , TMS320F28386S , TMS320F28386S-Q1 , TMS320F28388D , TMS320F28388S

 

  1.   Safety Manual for TMS320F2838xD and TMS320F2838xS
  2.   Trademarks
  3. 1Introduction
  4. 2TMS320F2838x Product Safety Capability and Constraints
  5. 3TI Development Process for Management of Systematic Faults
    1. 3.1 TI New-Product Development Process
    2. 3.2 TI Functional Safety Development Process
    3. 3.3 C2000 Architecture and Product Overview
      1. 3.3.1 TMS320F2838xD Real-Time MCUs
      2. 3.3.2 TMS320F2838xS Real-Time MCU
    4. 3.4 Functional Safety Concept
      1. 3.4.1 VDA E-GAS Monitoring Concept
      2. 3.4.2 TMS320F2838xD/S MCU Safety Philosophy
        1. 3.4.2.1 TMS320F2838xS Safety Philosophy
        2. 3.4.2.2 TMS320F2838xD MCU Safety Philosophy
      3. 3.4.3 Fault Tolerant Time Interval (FTTI)
      4. 3.4.4 TMS320F2838x MCU Safe State
      5. 3.4.5 Assumed Safety Requirements
      6. 3.4.6 Operating States
      7. 3.4.7 Management of Faults
      8. 3.4.8 Suggestions for Improving Freedom From Interference
      9. 3.4.9 Suggestions for Addressing Common Cause Failures
  6. 4TMS320F2838x Diagnostics Libraries
    1. 4.1 Assumptions of Use - F2838x Self-Test Libraries
    2. 4.2 Operational Details - F2838x Self-Test Libraries
      1. 4.2.1 Operational Details – CLA Self-Test Library
      2. 4.2.2 Operational Details - SDL
    3. 4.3 C2000 Safety STL Software Development Flow
    4. 4.4 TMS320F2838x MCU Safety Implementation
      1. 4.4.1 Assumed Safety Requirements
      2. 4.4.2 Example Safety Concept Implementation Options on TMS320F2838x MCU
        1. 4.4.2.1 Safety Concept Implementation: Option 1
          1. 4.4.2.1.1 Safety Concept Implementation: Option 2
  7. 5Brief Description of Safety Elements
    1. 5.1 C2000 MCU Infrastructure Components
      1. 5.1.1 Power Supply
      2. 5.1.2 Clock
      3. 5.1.3 Reset
      4. 5.1.4 System Control Module and Configuration Registers
      5. 5.1.5 Efuse Static Configuration
      6. 5.1.6 JTAG Debug, Trace, Calibration, and Test Access
    2. 5.2 Processing Elements
      1. 5.2.1 C28x Central Processing Unit (CPU)
      2. 5.2.2 Control Law Accelerator
    3. 5.3 Memory (Flash, SRAM and ROM)
      1. 5.3.1 Embedded Flash Memory
      2. 5.3.2 Embedded SRAM
      3. 5.3.3 Embedded ROM
    4. 5.4 On-Chip Communication Including Bus-Arbitration
      1. 5.4.1 Device Interconnect
      2. 5.4.2 Direct Memory Access (DMA)
      3. 5.4.3 Inter Processor Communication (IPC)
      4. 5.4.4 Enhanced Peripheral Interrupt Expander (ePIE) Module
      5. 5.4.5 Dual Zone Code Security Module (DCSM)
      6. 5.4.6 CrossBar (X-BAR)
      7. 5.4.7 Timer
      8. 5.4.8 Configurable Logic Block
    5. 5.5 Digital I/O
      1. 5.5.1 General-Purpose Input/Output (GPIO) and Pin Muxing
      2. 5.5.2 Enhanced Pulse Width Modulators (ePWM)
      3. 5.5.3 High Resolution PWM (HRPWM)
      4. 5.5.4 Enhanced Capture (eCAP)
      5. 5.5.5 High Resolution Capture (HRCAP)
      6. 5.5.6 Enhanced Quadrature Encoder Pulse (eQEP)
      7. 5.5.7 Sigma Delta Filter Module (SDFM)
      8. 5.5.8 External Interrupt (XINT)
    6. 5.6 Analog I/O
      1. 5.6.1 Analog-to-Digital Converter (ADC)
      2. 5.6.2 Buffered Digital-to-Analog Converter (DAC)
      3. 5.6.3 Comparator Subsystem (CMPSS)
    7. 5.7 Data Transmission
      1. 5.7.1 Controller Area Network (DCAN)
      2. 5.7.2 ECAT
      3. 5.7.3 Serial Peripheral Interface (SPI)
      4. 5.7.4 Serial Communication Interface (SCI)
      5. 5.7.5 Inter-Integrated Circuit (I2C)
      6. 5.7.6 Fast Serial Interface (FSI)
      7. 5.7.7 Power Management Bus Module (PMBus)
      8. 5.7.8 Multichannel Buffered Serial Port (McBSP)
      9. 5.7.9 External Memory Interface (EMIF)
    8. 5.8 Not Safety Related Elements
  8. 6Brief Description of Diagnostics
    1. 6.1 C2000 MCU Infrastructure Components
      1. 6.1.1  Clock Integrity Check Using CPU Timer
      2. 6.1.2  Clock Integrity Check Using HRPWM
      3. 6.1.3  EALLOW and MEALLOW Protection for Critical Registers
      4. 6.1.4  Efuse Autoload Self-Test
      5. 6.1.5  Efuse ECC
      6. 6.1.6  Efuse ECC Logic Self-Test
      7. 6.1.7  External Clock Monitoring via XCLKOUT
      8. 6.1.8  External Monitoring of Warm Reset (XRSn)
      9. 6.1.9  External Voltage Supervisor
      10. 6.1.10 External Watchdog
      11. 6.1.11 Glitch Filtering on Reset Pins
      12. 6.1.12 Hardware Disable of JTAG Port
      13. 6.1.13 Internal Watchdog (WD)
      14. 6.1.14 Lock Mechanism for Control Registers
      15. 6.1.15 Missing Clock Detect (MCD)
      16. 6.1.16 NMIWD Reset Functionality
      17. 6.1.17 NMIWD Shadow Registers
      18. 6.1.18 Multibit Enable Keys for Control Registers
      19. 6.1.19 Online Monitoring of Temperature
      20. 6.1.20 Periodic Software Read Back of Static Configuration Registers
      21. 6.1.21 Peripheral Clock Gating (PCLKCR)
      22. 6.1.22 Peripheral Soft Reset (SOFTPRES)
      23. 6.1.23 Software Test of Reset (Type 1)
      24. 6.1.24 PLL Lock Profiling Using On-Chip Timer
      25. 6.1.25 Reset Cause Information
      26. 6.1.26 Software Read Back of Written Configuration
      27. 6.1.27 Software Test of ERRORSTS Functionality
      28. 6.1.28 Software Test of Missing Clock Detect Functionality
      29. 6.1.29 Software Test of Reset
      30. 6.1.30 Software Test of Watchdog (WD) Operation
    2. 6.2 AUXPLL
      1. 6.2.1 Clock Integrity Check Using DCC
      2. 6.2.2 PLL Lock Indication
      3. 6.2.3 Internal Watchdog (WD)
      4. 6.2.4 Software Test of DCC Functionality Including Error Tests
      5. 6.2.5 External Clock Monitoring
      6. 6.2.6 Software Test of PLL Functionality Including Error Tests
      7. 6.2.7 Interleaving of FSM States
      8. 6.2.8 Dual Clock Comparator (DCC) – Type 1
      9. 6.2.9 Peripheral Access Protection - Type 0
    3. 6.3 Processing Elements
      1. 6.3.1  CLA Handling of Illegal Operation and Illegal Results
      2. 6.3.2  CLA Liveness Check Using CPU
      3. 6.3.3  CPU Hardware Built-In Self-Test (HWBIST)
      4. 6.3.4  CPU Hardware Built-In Self-Test (HWBIST) Auto-Coverage
      5. 6.3.5  CPU Hardware Built-In Self-Test (HWBIST) Fault Injection Capability
      6. 6.3.6  CPU Hardware Built-In Self-Test (HWBIST) Timeout Feature
      7. 6.3.7  CPU Handling of Illegal Operation, Illegal Results and Instruction Trapping
      8. 6.3.8  Reciprocal Comparison by Software
      9. 6.3.9  Software Test of CLA
      10. 6.3.10 Stack Overflow Detection
      11. 6.3.11 VCU CRC Check of Static Memory Contents
      12. 6.3.12 VCU CRC Auto Coverage
      13. 6.3.13 Embedded Real Time Analysis and Diagnostic (ERAD)
      14. 6.3.14 Inbuilt hardware redundancy in ERAD bus comparator module
      15. 6.3.15 Disabling of Unused CLA Task Trigger Sources
    4. 6.4 Memory (Flash, SRAM and ROM)
      1. 6.4.1  Bit Multiplexing in Flash Memory Array
      2. 6.4.2  Bit Multiplexing in SRAM Memory Array
      3. 6.4.3  Data Scrubbing to Detect/Correct Memory Errors
      4. 6.4.4  Flash ECC
      5. 6.4.5  Flash Program Verify and Erase Verify Check
      6. 6.4.6  Software Test of ECC Logic
      7. 6.4.7  Software Test of Flash Prefetch, Data Cache and Wait-States
      8. 6.4.8  Access Protection Mechanism for Memories
      9. 6.4.9  SRAM ECC
      10. 6.4.10 SRAM Parity
      11. 6.4.11 Software Test of Parity Logic
      12. 6.4.12 Software Test of SRAM
      13. 6.4.13 Memory Power-On Self-Test (MPOST)
      14. 6.4.14 Background CRC
      15. 6.4.15 Watchdog for Background CRC
      16. 6.4.16 Redundant Parity Engine
      17. 6.4.17 Test of SRAM Parity
    5. 6.5 On-Chip Communication Including Bus-Arbitration
      1. 6.5.1  1oo2 Software Voting Using Secondary Free Running Counter
      2. 6.5.2  DMA Overflow Interrupt
      3. 6.5.3  Event Timestamping Using IPC Counter
      4. 6.5.4  Maintaining Interrupt Handler for Unused Interrupts
      5. 6.5.5  Majority Voting and Error Detection of Link Pointer
      6. 6.5.6  PIE Double SRAM Comparison Check
      7. 6.5.7  PIE Double SRAM Hardware Comparison
      8. 6.5.8  Power-Up Pre-Operational Security Checks
      9. 6.5.9  Software Check of X-BAR Flag
      10. 6.5.10 Software Test of ePIE Operation Including Error Tests
      11. 6.5.11 Disabling of Unused DMA Trigger Sources
      12. 6.5.12 Software Test of CLB Function Including Error Tests
      13. 6.5.13 Monitoring of CLB by eCAP or eQEP
      14. 6.5.14 Lock Mechanism for Control Registers
      15. 6.5.15 Internal Watchdog (WD)
      16. 6.5.16 Periodic Software Read Back of SPI Buffer
      17. 6.5.17 IPC 64-Bit Counter Value Plausibility Check
    6. 6.6 Digital I/O
      1. 6.6.1  ECAP Application Level Safety Mechanism
      2. 6.6.2  ePWM Application Level Safety Mechanism
      3. 6.6.3  ePWM Fault Detection Using XBAR
      4. 6.6.4  ePWM Synchronization Check
      5. 6.6.5  eQEP Application Level Safety Mechanisms
      6. 6.6.6  eQEP Quadrature Watchdog
      7. 6.6.7  eQEP Software Test of Quadrature Watchdog Functionality
      8. 6.6.8  Hardware Redundancy
      9. 6.6.9  HRPWM Built-In Self-Check and Diagnostic Capabilities
      10. 6.6.10 Information Redundancy Techniques
      11. 6.6.11 Monitoring of ePWM by eCAP
      12. 6.6.12 Monitoring of ePWM by ADC
      13. 6.6.13 Online Monitoring of Interrupts and Events
      14. 6.6.14 SDFM Comparator Filter for Online Monitoring
      15. 6.6.15 SD Modulator Clock Fail Detection Mechanism
      16. 6.6.16 Software Test of Function Including Error Tests
      17. 6.6.17 Monitoring of HRPWM by HRCAP
      18. 6.6.18 HRCAP Calibration Logic Test Feature
      19. 6.6.19 QMA Error Detection Logic
    7. 6.7 Analog I/O
      1. 6.7.1 ADC Information Redundancy Techniques
      2. 6.7.2 ADC Input Signal Integrity Check
      3. 6.7.3 ADC Signal Quality Check by Varying Acquisition Window
      4. 6.7.4 CMPSS Ramp Generator Functionality Check
      5. 6.7.5 DAC to ADC Loopback Check
      6. 6.7.6 DAC to Comparator Loopback Check
      7. 6.7.7 Opens/Shorts Detection Circuit for ADC
      8. 6.7.8 VDAC Conversion by ADC
      9. 6.7.9 Disabling Unused Sources of SOC Inputs to ADC
    8. 6.8 Data Transmission
      1. 6.8.1  Controller Area Network (MCAN, CAN-FD)
        1. 6.8.1.1 PWM Trip by MCAN
        2. 6.8.1.2 MCAN Stuff Error Detection
        3. 6.8.1.3 MCAN Form Error Detection
        4. 6.8.1.4 MCAN Acknowledge Error Detection
        5. 6.8.1.5 Timeout on FIFO Activity
        6. 6.8.1.6 Timestamp Consistency Checks
        7. 6.8.1.7 Tx-Event Checks
        8. 6.8.1.8 Interrupt on Message RAM Access Failure
      2. 6.8.2  ECAT
        1. 6.8.2.1  EtherCAT MDIO Command Error Indication
        2. 6.8.2.2  EtherCAT Sync-Manager
        3. 6.8.2.3  EtherCAT Working Counter Error Indication
        4. 6.8.2.4  EtherCAT Frame Error Indication
        5. 6.8.2.5  EtherCAT Physical Layer Error Indication
        6. 6.8.2.6  PDI Timeout Error Indication
        7. 6.8.2.7  EtherCAT EEPROM CRC Error Indication
        8. 6.8.2.8  EtherCAT EEPROM Not Done Error Indication
        9. 6.8.2.9  EtherCAT Data Link Error Indication
        10. 6.8.2.10 EtherCAT Phy Link Error Indication
        11. 6.8.2.11 Sync, GPO Monitoring Using External Monitor
        12. 6.8.2.12 EtherCAT Enhanced Link Detection With LED
        13. 6.8.2.13 HW Redundancy of GPIO, FMMU, Sync Manager and SYNC OUT
      3. 6.8.3  Bit Error Detection
      4. 6.8.4  CRC in Message
      5. 6.8.5  DCAN Acknowledge Error Detection
      6. 6.8.6  DCAN Form Error Detection
      7. 6.8.7  DCAN Stuff Error Detection
      8. 6.8.8  EMIF Access Latency Profiling Using On-Chip Timer
      9. 6.8.9  EMIF Access Protection Mechanism
      10. 6.8.10 EMIF Asynchronous Memory Timeout Protection Mechanism
      11. 6.8.11 I2C Access Latency Profiling Using On-Chip Timer
      12. 6.8.12 Information Redundancy Techniques Including End-to-End Safing
      13. 6.8.13 I2C Data Acknowledge Check
      14. 6.8.14 McBSP Receiver Overrun Detection
      15. 6.8.15 McBSP Receiver Sync Error Detection
      16. 6.8.16 McBSP Transmitter Sync Error Detection
      17. 6.8.17 McBSP Transmitter Underflow Detection
      18. 6.8.18 Parity in Message
      19. 6.8.19 SCI Break Error Detection
      20. 6.8.20 SCI Frame Error Detection
      21. 6.8.21 SCI Overrun Error Detection
      22. 6.8.22 Software Test of Function Using I/O Loopback
      23. 6.8.23 SPI Data Overrun Detection
      24. 6.8.24 Transmission Redundancy
      25. 6.8.25 FSI Data Overrun/Underrun Detection
      26. 6.8.26 FSI Frame Overrun Detection
      27. 6.8.27 FSI CRC Framing Checks
      28. 6.8.28 FSI ECC Framing Checks
      29. 6.8.29 FSI Frame Watchdog
      30. 6.8.30 FSI RX Ping Watchdog
      31. 6.8.31 FSI Tag Monitor
      32. 6.8.32 FSI Frame Type Error Detection
      33. 6.8.33 FSI End of Frame Error Detection
      34. 6.8.34 FSI Register Protection Mechanisms
      35. 6.8.35 PMBus Protocol CRC in Message
      36. 6.8.36 Clock Timeout
  9. 7References
  10.   A Safety Architecture Configurations
  11.   B Distributed Developments
    1.     B.1 How the Functional Safety Life Cycle Applies to Functional Safety-Compliant Products
    2.     B.2 Activities Performed by Texas Instruments
    3.     B.3 Information Provided
  12.   C Terms and Definitions
  13.   D Summary of Safety Features and Diagnostics
  14.   E Glossary
  15.   F Revision History

3.4.6 Operating States

The TMS320F2838xD/S MCU products have a common architectural definition of operating states. These operating states should be observed by the system developer in their software and system level design concepts. The operating states state machine is shown in Figure 3-10. The operating states can be classified into device boot phase and CPU1SS operation phase (applicable to all the devices), and CPU2SS operation phase (applicable to TMS320F2838xD class of devices). CPU2SS operation phase is initiated by CPU1SS operation phase. Any critical errors in either CPU1SS operation phase or CPU2SS operation phase cause the device to enter into safe state.

The various states of the device operating states state machine are:

  • Powered Off - This is the initial operating state of C2000 MCU. No power is applied to either core or I/O power supply and the device is non-functional. An external supervisor can perform this action (power-down the C2000 MCU) in any of the C2000 MCU states as response to a system level fault condition or a fault condition indicated by the C2000 MCU.
  • Reset State – In this state, the device reset is asserted either using the external pins or using any of the internal sources.
  • Safe State – In the Safe state, the device is either not performing any functional operations or an internal fault condition is indicated using the device I/O pins.
  • Cold Boot - In the cold boot state, key analog elements, digital control logic, and debug logic are initialized. The CPU remains powered but in reset. When the cold boot process is completed, the reset of the master CPU is internally released, leading to the warm boot stage.
  • Warm Boot - The CPU begins execution from Boot ROM during the warm boot stage. CPU initializes the device security (all memories come up as secure at the beginning of the warm boot and this stage configures the security as needed for the particular system), exception handling and calibration of analog components and initializes the peripheral boot mode if required. For more details regarding boot process, see the device-specific boot ROM specification.
  • Pre-operational - Transfer of control from boot code to customer code takes place during this phase. Application-specific configurations (for example, clock frequency, peripheral enable, pin mux, and so forth) are performed in this phase. Boot time self-test/proof-test required to ensure proper device operation is performed during this phase. See Section 6.5.8 (ROM8) for details.
  • Operational – This marks the system exiting the pre-operational state and entering the functional state. The device is capable of supporting safety critical functionality during operational mode.

The device start-up timeline for both the CPUs are shown in Figure 3-11.

GUID-E474E1B4-305D-4045-9FD7-1A09D8ABC169-low.gifFigure 3-11 TMS320F2838x MCU CPU Start-Up Timeline