• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 83 subscribers
  • Views 671 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.

TMS320F2800154-Q1: Automotive software standard compliance

Crane Shao
Intellectual 980 points

Part Number: TMS320F2800154-Q1
Other Parts Discussed in Thread: C2000WARE

Hello,

TMS320F2800154 is designed for automotive. But, from what I know, the driver from C2000Ware doesn't comply to ISO26262 standard, including Misra C coding standard. So, how does it work to use this chip on automotive product? We need to fix all the non-compliance issues ourselves, or there is any support from TI about this?

Thanks!

Crane

  • 0
    TI__Expert 7715 points

    Hi Crane,

    The F280015x micro-controller hardware is certified ASIL-B for Automotive. In terms of software, safety critical software like Safety Test Library (STL) is also FuSa compliant. The C2000Ware driverlib APIs are meant to be a reference and are not  functional safety compliant. You will need to take the C2000Ware APIs being used in your application through the FuSa flow along with the application code. 

    Would you be able to share the list of C2000Ware IPs you are planning to use that require FuSa compliance? It will help us evaluate our FuSa software offering for C2000Ware.

    Thanks,

    Ashwini

  • 0 in reply to Ashwini Athalye
    Intellectual 980 points

    Hi Ashwini,

    Thank you for your reply.

    Ok got it. Can you give more information about your FuSa software offering? Generally, what does it includes and what is the process?

    For the C2000Ware API list used in the project source code, is there any way to generate that list? Or I need to search the source code to find out the APIs that are used in there?

    Thanks!

    Crane

  • 0 in reply to Crane Shao
    TI__Expert 7715 points

    Hi Crane,

    Apologies for the delayed reply.

    The following App Note has details. Please let me know if you need anything else.

    https://www.ti.com/lit/SWAB014

    Can you share just the list of IPs that will be a good starting point.

    Thanks,

    Ashwini

  • 0 in reply to Ashwini Athalye
    Intellectual 980 points

    Hi Ashwini,

    Thank you for your reply.

    I read the application notes and have the following questions:

    1. It looks like if we want our product FuSa compliant, we need to replace the APIs from C2000Ware to the ones from STL, right? If so, are they compatible?

    2. It looks the STL is the same for all C2000 MCUs, for example F28004x and F280015x, right?

    3. Since ISO26262 doesn't explicitly requires Misra compliant, is the STL Misra compliant as well?

    IP, you mean the internal peripheral? We are using these peripherals: ePWM, ADC, GPIO, SPI and I2C. Does timer and interrupt count?

    Curious how the list of IP is relevant to FuSa compliant?

    Thanks!

    Crane

  • 0 in reply to Crane Shao
    TI__Expert 7715 points

    Hi Crane,

    The STL is a Self-Test Library targeted for CPU Logic integrity test. This is not a replacement for the C2000Ware driverlib which has APIs for peripheral configuration. In short the STL does not cover safety mechanisms that utilize the peripherals.

    Thanks,

    Ashwini

  • 0 in reply to Ashwini Athalye
    Intellectual 980 points

    Hi Ashwini,

    If so, I didn't get from the App Note you shared about what the STL is and how the STL is relevant to my original question: How to get my firmware, which uses the driverlib, to get compliant with Misra C and ISO26262?

    Ashwini Athalye said:
    Can you share just the list of IPs that will be a good starting point.

    Is what I shared what you are asking for? If not, what it should be? If yes, what's after?

    Thanks!

    Crane