SPRT759A October   2023  – June 2024 TMS320F280021 , TMS320F280021-Q1 , TMS320F280023 , TMS320F280023-Q1 , TMS320F280023C , TMS320F280025 , TMS320F280025-Q1 , TMS320F280025C , TMS320F280025C-Q1 , TMS320F280033 , TMS320F280034 , TMS320F280034-Q1 , TMS320F280036-Q1 , TMS320F280036C-Q1 , TMS320F280037 , TMS320F280037-Q1 , TMS320F280037C , TMS320F280037C-Q1 , TMS320F280038-Q1 , TMS320F280038C-Q1 , TMS320F280039 , TMS320F280039-Q1 , TMS320F280039C , TMS320F280039C-Q1 , TMS320F280040-Q1 , TMS320F280040C-Q1 , TMS320F280041 , TMS320F280041-Q1 , TMS320F280041C , TMS320F280041C-Q1 , TMS320F280045 , TMS320F280048-Q1 , TMS320F280048C-Q1 , TMS320F280049 , TMS320F280049-Q1 , TMS320F280049C , TMS320F280049C-Q1 , TMS320F28075 , TMS320F28075-Q1 , TMS320F28076 , TMS320F28374D , TMS320F28374S , TMS320F28375D , TMS320F28375S , TMS320F28375S-Q1 , TMS320F28376D , TMS320F28376S , TMS320F28377D , TMS320F28377D-EP , TMS320F28377D-Q1 , TMS320F28377S , TMS320F28377S-Q1 , TMS320F28378D , TMS320F28378S , TMS320F28379D , TMS320F28379D-Q1 , TMS320F28379S , TMS320F28384D , TMS320F28384D-Q1 , TMS320F28384S , TMS320F28384S-Q1 , TMS320F28386D , TMS320F28386D-Q1 , TMS320F28386S , TMS320F28386S-Q1 , TMS320F28388D , TMS320F28388S , TMS320F28P650DH , TMS320F28P650DK , TMS320F28P650SH , TMS320F28P650SK , TMS320F28P659DH-Q1 , TMS320F28P659DK-Q1 , TMS320F28P659SH-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4.   Introduction
  5.   Overview of IEC 60730 and UL 1998 Classifications
    1.     C2000 Capability by Device Family
  6.   C2000 Safety Collateral
    1.     Getting Started
    2.     Functional Safety Manuals
    3.     Software Collateral
  7.   Implementing Acceptable Measures on C2000 Real-Time MCUs
    1.     Implementation Steps
    2.     Example Mapping
    3.     Additional Best Practices
  8.   Mapping Acceptable Control Measures to C2000 Unique Identifiers
    1.     Unique Identifier Reference
    2.     CPU Related Faults
    3.     Interrupt Related Faults
    4.     Clock Related Faults
    5.     Memory Related Faults
    6.     Internal Data Path Faults
    7.     Input/Output Related Faults
    8.     Communication, Monitoring Devices, and Custom Chip Faults
  9.   Glossary
  10.   References

Implementation Steps

To plan implementation of an acceptable measure, the suggested steps are:

Step Description References
Step 1 Map acceptable measures to C2000 Unique IDs:
The specifications typically present the developer with a choice of acceptable measures to detect a specific fault. This document presents a mapping of some acceptable measures to Unique IDs. In some cases more than one Unique ID may apply.
Step 2 Plan the implementation:
Read the description and guidelines, or suggestions, for implementing Unique ID. You will also learn if the Unique ID implementation is based on hardware, software or both.		 Device-specific Functional Safety Manual: Summary of Safety Features and Diagnostics
Step 3 Identify supporting software:
Identify if the Unique ID is supported by the SDL or an STL.
  • Device-specific Functional Safety Manual: Safety Diagnostics Libraries
  • This document: Software Collateral
  • SDL or STL documentation
In some cases, a Unique ID is not supported by an SDL/STL module. This occurs when the Unique ID corresponds to a hardware mechanism with minimal, or no, software requirements, or the Unique ID requires a system-dependent implementation.

In these cases reference:

  1. The FSM Unique ID description for implementation guidance and suggestions.
  2. The C2000Ware Software Development Kit software examples to implement the requirements based on the FSM guidance. For example:
    • Populating PIE vectors, including unused vectors.
    • Embedded real-time analysis and diagnostic module (ERAD) examples.
    • VCRC module library to calculate CRCs.
    • Peripheral configuration.
Step 4 Identify additional Unique IDs to implement:
Some IDs may not directly map to IEC 60370 but are still highly recommended. Many of these are hardware implementations and take little overhead in a system.