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.

RM46L852: How to invoke an error to check the SafeTi library functions.

Part Number: RM46L852


Hello,

I want to know that i am trying to implement the safeti library on Herculus Rm46x.

Do i need to call the functions in the sys_main.c or anywhere else?

also i want to invoke some error to check if it is implemented correctly or not.

How to invoke an error?

is there any functions to invoke errors or something related to it? thanks

  • Hello,

    TI has developed SafeTI library which is ready to download from ti.com:

    You can call the function in main() or anywhere else. For example, you can call checkRAMECC() to test the CPU ECC mechnism for RAM accesses. You can call ccmSelfCheck() to self check the CCM module.

    Regards,

    QJ

  • Hello,

    Thanks QJ for your reply. I already have installed the safeTI library in my project. Now e.g if i am calling  SL_Init_ECCFlash(10, FLASHECC_DEFAULT) or SL_Init_Memory(RAMTYPE_RAM) in my main. As there isn't any error in the MCU these tests will always return true. But what if i want to demonstrate by invoking the error that if error occurs it will return false and we can say that there is an error and the safety test fails. Is there any functions in the safetI library or any thing else within MCU to inject an error?thanks

  • We cannot inject an error? I didnot get any response so far?
  • Hello Hassan,

    Much of what you are looking for is included in the SafeTI Diagnostic library demo app. Although we don't have demo apps for all devices at this point, the RM46L852 is present. For specific examples of testing diagnostics, see the sys_selftest.c source. However, I think you will have to consider that the primary purpose to inject the faults is to test the primary diagnostic measure using one or more of the tests for diagnostics. In some cases where a direct test for diagnostic is not possible/feasible, we rely on overlap of diagnostic mechanisms to protect the safety functions. Please reference the table in appendix A of the safety manual for identification of primary diagnostic mechanisms and tests for diagnostics for the primary diagnostic.