• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 317 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.

RM57L843: Since ESM module can capture kinds of faults and inform application thru callback function, why do we still use SafeTI diagnostic liarary to do selftest mannually

shenruming
Intellectual 575 points
Part Number: RM57L843


Hi,

I have a question about SafeTI diagnostic library.

As we know ESM module can capture kinds of faults and inform application thru calling callback function automatically, why do we still use SafeTI diagnostic liarary to do selftest mannually?

Thanks.

  • 0
    TI__Guru**** 197426 points

    Hi Shenruming,

    The fault injection API of SDL are used to create faults at run time such that the application developer may be able to simulate faults. The faults are processed for additional information and intimated to application via registered callbacks. 

    The self-test should be triggered manually.

  • 0 in reply to QJ Wang
    Intellectual 575 points

    Hi QJ,

    Take SRAM diagnostic library for example.

    In my understanding, just SRAM_XXX_INJECT are used to inject fault and then ESM interrupt call callback function to response to the artificial fault, right?

    If so, what are the other options used for, such as SRAM_ECC_ERROR_FORCING_IBIT?

    If they're not used for fault injection, they must be used to detect fault initiatively and put the test result into pointer parameter or return value.

    In this case, we need not use ESM with callback function. Right?

    If so, why not use ESM interrupt handling and callback mecahnism to replace it?

    After all, in addition to fault injection testing, ESM can also discover and report actual device faults. 

    Can you please help confirm the above 4 questions?

    Please correct me if my understanding is not correct. Thanks.

  • 0 in reply to shenruming
    TI__Guru**** 197426 points
    shenruming said:
    In my understanding, just SRAM_XXX_INJECT are used to inject fault and then ESM interrupt call callback function to response to the artificial fault, right?

    Yes, you are correct.

    shenruming said:
    If so, what are the other options used for, such as SRAM_ECC_ERROR_FORCING_IBIT?

    The ESM callback is disabled for Error forcing test and selftest.

  • 0 in reply to QJ Wang
    Intellectual 575 points

    Hello QJ,

    Thanks for your reply.

    From your words, I got that ESM module is just for fault injection, not for selftest.

    I have another question on this topic.

    When we call API SL_SelfTest_SRAM to do selftest, the test result may be normal or fail. Then we need to treat the test result carefully in our application.

    But when we do fault injection by passing paramter of injection test type, how to deal with the test result delivered with test result parameter or return value?

    We can ignore the test result returned from test API? After all, ESM module will send out it by callback function when it detects the injected fault. Right?

  • 0 in reply to shenruming
    TI__Guru**** 197426 points

    If the test result is "PASS", you can ignore it. If the test result is "FAIL", you need to stop and do more test to check if it is a random failure or permament failure.