• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 29 subscribers
  • Views 641 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.

Original question:

TMS570LS1227: Fapi and iso26262

TMS570LS1227: F021 Flash API certification

Lars Guenther
Intellectual 675 points
Part Number: TMS570LS1227
Other Parts Discussed in Thread: HALCOGEN

Hi all,

in one of the latest forum entries for the F021 Flash API Sunil wrote:

"Yes, the development process used for the flash API was certified for use in applications that require conformance up to ASIL D."

We are using this F021 Flash API. Our verifiaction and validation experts wants to have the certification paper, otherwise we should not use the F021 Flash API in our Software. They do not accept the Release Note.

Is it possible to get a certification paper for the F021 Flash API ?

Best regards

Lars

  • 0
    TI__Mastermind 49120 points
    Hi Lars,

    I misspoke earlier when I stated that the Flash API itself was created using a compliant software development process. I am pasting below from an older post related to this topic:

    The F021 Flash API Library was developed prior to establishment of a Function Safety Compliant Process at TI. In order to continue to support our customers and their safety needs, we have retroactively applied both static and dynamic testing together with their associated reports as part of a compliance support package (CSP) in order for this software component to be utilized within safety systems. Currently, the F021 Flash API Library is included in the Halcogen CSP package offered on TI.com. If your company is not using Halcogen or does not plan to use the Halcogen CSP, please let me know so we can discuss treatment of the F021 Library for safety. On a side note, in most cases, we have found that the actual use of the SW was not safety related in that it was only used to program the device as in a boot loader scenario or that the data that it was used to write in the role of EEPROM emulation was not safety critical. In the event that the data is safety critical, we recommend implementation of relevant safe guards of that information such as data redundancy, CRC checks of written data blocks, and read back of written data to insure proper operation.

    I will also correct the other post where I have mentioned the Flash API development process.

    Regards,
    Sunil