• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 149 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AM2612: AM2612 Functional Safety several questions from Cust

Rio Chan
Genius 16020 points

Part Number: AM2612

Champs:

My cust asked those questions, please reply for each.

1. How is the single code can achieve ASIL-B / SIL2? Any example / document to address this?

2. If the code working success rate is 100%, so, the safety is 100%, this has no problem. But, if the code will be fail somehow, so the sucess rate is 0%, why the fail rate can be 7x% or 9x%? Plz explain.

3. Is there any SIL-3 function safety code for BMS regarding the OTP/OCP/OVP? Any documentation?

4. The Pbist.c only shows the printf, how to determine my code is having the safety score is 90% and map this score into the FMEDA table?

    How the FMEDA table can judge my code's success rate?

    How the FMEDA table knows my code is safety score with 95% ? not 0%? 

5. After my studying, there is 3rd party tool can evluate my code success rate, what's the recommened tool?

Thanks.

BR Rio              

  • 0
    TI__Expert 7835 points

    Hi Rio,

    Most of these questions mix up hardware functional safety metrics with software functional safety.

    For hardware, metrics such as failure rate, diagnostic coverage, and FMEDA are used because hardware can experience random failures. For software, this does not apply in the same way. Software does not have random hardware failure; instead, software functional safety is addressed through systematic capability, meaning the required development, verification, and validation process used to ensure the software correctly implements the safety requirements and minimizes systematic faults.

    Because of this, concepts such as software success rate, software failure rate, or software safety percentage are generally not the correct way to evaluate software safety.

    TI currently does not provide application-level safety software such as SIL-3 BMS code for OTP/OCP/OVP. TI provides the MCU as a SEooC, and our current software safety support is mainly the self-test library and related device-level safety documentation.
    • ASIL-B / SIL2: A software component can support ASIL-B or SIL2 only when the full safety process, verification, and documentation meet the target standard requirements. It is not determined by the code alone.
    • 70% / 90% fail rate: These percentages usually refer to hardware diagnostic coverage, not software success or failure rate.
    • SIL-3 BMS code: TI does not currently provide this kind of application safety software.
    • PBIST / FMEDA / safety score: PBIST and FMEDA evaluate hardware diagnostics, not your application software “score.”
    • 3rd-party tool: We are not aware of a standard tool that evaluates “software success rate.” Typical software safety tools are static analysis, coding-rule checking, and test coverage tools.

    Han

  • 0 in reply to Han Zhang6
    TI__Genius 16020 points

    Thanks. Han, I will close this ticket.