• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 29 subscribers
  • Views 329 views
  • Users 0 members are here
Support feedback
Options
Options

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.

RM57L843: SafeTI Diagnostic Library - Fault injection issue

Vikas Nichite
Intellectual 280 points
Part Number: RM57L843
Other Parts Discussed in Thread: HALCOGEN

Hello,

I have included all safety lib. as example in HALCOGEN, my project is compiling without error,

but when i check L2RAMECCCHECK then retVal is always false as i call retVal = SL_SelfTest_SRAM(SRAM_ECC_ERROR_FORCING_1BIT, TRUE, &result); and  code is stuck to if(retVal == false){while(1);,

Observation: 

1. After fault inject ESMHandler is getting call,

2. On returning from ESMHandler  the retVal is false and code is stuck at while,

Let me know is there is any Halcogen setting or any thing i missed.

Thanks and regard,

Vikas N.

  • 0
    TI__Mastermind 49120 points

    There are multiple reasons for which a "false" would be returned from the SL_SelfTest_SRAM() function. Can you make sure you are following the sequence as in the demo application that is in the safety diagnostic library?

  • 0 in reply to Sunil Oak
    Intellectual 280 points

    Yes the sequence is same as per demo application, 

    The SL_SelfTest_PBIST is working Properly except the fault injection i.e SL_SelfTest_SRAM,

    Thank you.

    Vikas N

  • 0 in reply to Vikas Nichite
    TI__Mastermind 49120 points

    Hello,

    Sorry missed your response, as the thread had gone quiet for quite a while. The demo project that is downloaded with the SDL has compiler optimization level 3 enabled. Do you have the same also for your project?

    Please turn off compiler optimizations for the project if it is enabled. Optimizations can be enabled at individual file level.

    Alternatively, disable compiler optimization from startup.c and selftest.c files.

    Let me know if this works for the RAM self-test.