This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TDA4VM-Q1: How to export functional safety diagnostic needs based on ASIL B systems

Part Number: TDA4VM-Q1
Other Parts Discussed in Thread: DRA829, TDA4VM

Hi team,

Here's an issue from the customer may need your help:

1) FMEDA tool,DRA829_TDA4VM_FMEDA_Automotive.xlsm:

a. How to enter the condition for ASIL B (90% diagnostic coverage) in the table? Or how to rate ASIL B?

b. how to select Safety mechanisms in Pin level tailoring, function and Diag Tailoring tab in Excel tool select? 

2) DRA829/TDA4VM Safety Manual Jacinto 7 Processors

a. In ASIL B systems, do the diagnostic requirements and recommendations in the Safety Manual have to be implemented one by one basis for 90% diagnostic coverage?

Could you help check this case? Thanks.

Best Regards,

Cherry

  • Hi Cherry,

    Will follow up with you, if there is existing FMEDA training that can be provided.

    Please also reference Safety Manual, Section 7 An In-Context Look at this Safety Element out of Context.   

    This section describes example use cases and goes into more detail on how to identify IPs that are critical to the safety function and how to configure the associated
    diagnostics

    Regards,

    kb

  • Cherry, 

    There is an internal training that was provided to China FAEs for FMEDA last year:  https://ti.webex.com/ti/ldr.php?RCID=d5213078cafca6292eef66969835a462

    To answer your questions: 

    1) You will have to refer to safety manual to determine groupings.  Using GPIO as an example, you would use following grouping for 90%.  

    and the group is defined in the safety manual as following safety mechanisms.  

     

    The safety mechanisms are named the same as the groupings in the safety manual.  For example you would select GPIO.DIAGS on the FMEDA since that grouping is what you are using to achieve 90% DC per the safety manual.   You would repeat this process for every safety critical IP in the system.  

    2) The safety manual recommends the diagnostics in a group.  For for 90% coverage we recommended implementing all the diagnostic listed in the group.  If there is a diagnostic that the customer does not think they need because it covers a failure mode that are not concerned about, the customer can reach out to TI to have further discussions.