• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 160 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: Diagnostic Library API issue

Cherry Zhou
Mastermind 22235 points
Part Number: RM57L843


Hi team,

Here's some issues from the customer may need your help:

The Diagnostic Library API is only used to test if a module has the ability to error-check (ECC), and it is not possible to detect if a module (such as memory) has made an error while a program is running. Is that right?

For example, SL_SelfTest_CAN() is an API that does not detect if there is a problem with the CAN's internal program operation, but can only test whether it has the ability to correct errors by simulating a 1- or 2-bit error injection?

If so, will the error generated by the analogue test trigger a level change on the nERROR pin?

Could you help check this case? Thanks.

Best Regards,

Cherry

  • 0
    TI__Guru**** 198766 points

    Hi Cherry,

    The ECC related SelfTest APIs, for example SL_SelfTest_CAN(), is to check if the ECC SECDED mechanism works correctly and if the detected error is reported to ESM including nERROR action.

    The CAN message RAM is protected by ECC (SECDED). The DCAN Message RAM contains message objects and ECC bits for the message objects. The ECC bits are stored in a dedicated RAM. They will be generated on write accesses and will be checked on read accesses. Whenever you read the message which contain an ECC error, the ECC error will be detected by the ECC logic. If a single-bit error is detected, the correction will be done. If a double-bit error is detected, then the error flag is set and interrupt is generated based on your setup.

    Cherry Zhou said:
    it is not possible to detect if a module (such as memory) has made an error while a program is running. Is that right?

    The error is only detected when a read operation is performed.