SPRUID8D September 2020 – January 2022 TMS320F280040-Q1 , TMS320F280040C-Q1 , TMS320F280041 , TMS320F280041-Q1 , TMS320F280041C , TMS320F280041C-Q1 , TMS320F280045 , TMS320F280048-Q1 , TMS320F280048C-Q1 , TMS320F280049 , TMS320F280049-Q1 , TMS320F280049C , TMS320F280049C-Q1
C2000 is a trademark of Texas Instruments.
All trademarks are the property of their respective owners.
The products supported by this document have been assessed to be meet a systematic capability compliance of ASIL D (according to ISO 26262) and SIL 3 (according to IEC 61508). For more information, see the Texas Instrument's functional safety hardware development process.
This Functional Safety Manual is part of the Functional Safety-Compliant design package to aid customers who are designing systems in compliance with ISO26262 or IEC61508 functional safety standards.
This document is a functional safety manual for the Texas Instruments TMS320F28004x safety critical microcontroller product family. The product family utilizes a common safety architecture that is implemented in multiple application focused products.
Product configurations supported by this functional safety manual include silicon revision B of the following products listed in Table 1-1. The device revision can be determined by the REVID field of the device identification registers outlined in the product data sheet.
Orderable Devices | Supported Safety Integrity Level |
---|---|
F280048CPMQR | ASIL B |
F280048PMQR | ASIL B |
F280049CPMS | ASIL B |
F280049CPZQR | ASIL B |
F280049CPZS | ASIL B |
F280049PMS | ASIL B |
F280049PMSR | ASIL B |
F280049PZQ | ASIL B |
F280049PZQR | ASIL B |
F280049PZS | ASIL B |
F280049PZSR | ASIL B |
F280040CPMQR | QM |
F280040PMQR | QM |
F280041CPMS | QM |
F280041CPZQR | QM |
F280041CPZS | QM |
F280041CRSHSR | QM |
F280041PMS | QM |
F280041PMSR | QM |
F280041PZQR | QM |
F280041PZS | QM |
F280041PZSR | QM |
F280041RSHSR | QM |
F280045PMS | QM |
F280045PMSR | QM |
F280045PZS | QM |
F280045PZSR | QM |
F280045RSHSR | QM |
F280049CRSHSR | QM |
F280049CRSHS | QM |
F280049RSHSR | QM |
This Functional Safety Manual provides information needed by system developers to assist in the creation of a safety critical system using a supported TMS320F28004x MCU. This document contains:
The following information is documented in the Detailed Functional Safety Analysis Report (SAR) for TMS320F28004x C2000™ MCUs, which is only available under Functional Safety NDA and is not repeated in this document:
It is expected that the user of this document should have a general familiarity with the TMS320F28004x product families. More information can be found at www.ti.com/C2000.
This document is intended to be used in conjunction with the pertinent data sheets, technical reference manuals, and other documentation for the products being supplied.
For information which is beyond the scope of the listed deliverables, please contact your TI sales representative or www.ti.com.
This section summarizes the TMS320F28004x product safety capability. Each TMS320F28004x product:
For functional safety development, it is necessary to manage both systematic and random faults. Texas Instruments follows a new-product development process for all of its components which helps to decrease the probability of systematic failures. This new-product development process is described in Section 3.1. Components being designed for functional safety applications will additionally follow the requirements of TI's functional safety development process, which is described in Section 3.2.
Texas Instruments has been developing components for automotive and industrial markets since 1996. Automotive markets have strong requirements regarding quality management and product reliability. The TI new-product development process features many elements necessary to manage systematic faults. Additionally, the documentation and reports for these components can be used to assist with compliance to a wide range of standards for customer’s end applications including automotive and industrial systems (e.g ISO 26262-4:2018, IEC 61508-2:2010).
This component was developed using TI’s new product development process which has been certified as compliant to ISO 9001 / IATF 16949 as assessed by Bureau Veritas (BV).
The standard development process breaks development into phases:
Figure 3-1 shows the standard process.
The TI functional safety development flow derives from ISO 26262:2018 and IEC 61508:2010 a set of requirements and methodologies to be applied to semiconductor development. This flow is combined with TI's standard new product development process to develop Functional Safety-Compliant components. The details of this functional safety development flow are described in the TI internal specification - Functional Safety Hardware.
Key elements of the TI functional safety-development flow are as follows:
Table 3-1 lists these functional safety development activities that are overlaid atop the standard development flow in Figure 3-1.
For more information about which functional safety lifecycle activities TI performs, see Section B.
The customer facing work products derived from this Functional Safety-Compliant process are applicable to many other functional safety standards beyond ISO 26262:2018 and IEC 61508:2010.
Assess | Plan | Create | Validate | Sustain and End-of-Life |
---|---|---|---|---|
Determine if functional safety process execution is required | Define component target SIL/ASIL capability | Develop component level functional safety requirements | Validate functional safety design in silicon | Document any reported issues (as needed) |
Nominate a functional safety manager | Generate functional safety plan | Include functional safety requirements in design specification | Characterize the functional safety design | Perform incident reporting of sustaining operations (as needed) |
End of Phase Audit | Verify the functional safety plan | Verify the design specification | Qualify the functional safety design (per AEC-Q100) | Update work products (as needed) |
Initiate functional safety case | Start functional safety design | Finalize functional safety case | ||
Analyze target applications to generate system level functional safety assumptions | Perform qualitative analysis of design (i.e. failure mode analysis) | Perform assessment of project | ||
End of Phase Audit | Verify the qualitative analysis | Release functional safety manual | ||
Verify the functional safety design | Release functional safety analysis report | |||
Perform quantitative analysis of design (i.e. FMEDA) | Release functional safety report | |||
Verify the quantitative analysis | End of Phase Audit | |||
Iterate functional safety design as necessary | ||||
End of Phase Audit |