• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 101 subscribers
  • Views 185 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: functional safety and compiler optimization flag

Ugo Bertacchini
Intellectual 280 points
Part Number: TDA4VM

Hello,

we are developing a safety device which employs TDA4VM.

Instead of using a certified compiler we understood we can use the compiler provided inside the SDK (which is not certified), write the code following MISRA-C rules and then qualify the compiled binaries with your safety compiler qualification kit (www.ti.com/.../SAFETI_CQKIT).

Nevertheless, we were wondering whether you have recommendation with respect to compilation flags when compiling for safety application with the compilers provided in the SDKs, e.g.:
- compilation flags that must not be used (e.g. for “unsafe” optimization, nonstandard behavior);
- compilation flags that must be used ( e.g. with stricter, additional checks).

Thanks and regards.

  • 0
    TI__Guru* 93951 points

    Hi,

    Is there a particular S/W component from the SDK such as MCAL / SDL, and/or a particular H/W core A72/R5/C6/C7 that is of interest to you?   

    This may help in narrowing down scope of question.

    Thanks,

    kb

  • 0 in reply to KB
    Intellectual 280 points

    Hello KB,

    we will focus the development of safety code in R5, C6 and C7 cores (not in A72).

     The goal of the question is to understand if we have some known safety limitation in the compiler optimization flags we can use.

    Best regards