• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 82 subscribers
  • Views 201 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.

Original question:

TMS320F28377D: CPUMBIST and related demo/examples

TMS320F28377D: Regarding the use of modified function STL_March_testRAM

Sheldon He
Expert 8585 points
Part Number: TMS320F28377D


Hi Expert,

I will send you a copy with more information through email. Here is general what the question is. Thanks

============================

There are some problems when we use the modified function STL_March_testRAM(const STL_March_Pattern pattern, const uint32_t startAddress, const uint32_t length, const STL_March_InjectErrorHandle errorHandle) provided by TI in our program. The problem is described as follows:

1)     When the input parameter “errorHandle” is set to 0, our program can run normally, and the returned RAM test result is no error, this is ok;

2)     When the input parameter “errorHandle” is set to inject an error into RAM, our program cannot run normally. The specific code for injecting error is described as follows;

Note: The only difference between the code in case 1 and case 2 mentioned above is the part marked with red line in the figure below.
The questions we want to know is listed as follows:

A.    If the settings of “errorHandle” shown in the figure below is correct? If it is not correct, how should we set “errorHandle” to inject an error? Could you help to provide an example?

B.     How will the DSP act when a RAM error is detected? Can it continue to operate normally?

modified function STL_March_testRAM

  • 0
    TI__Guru 53995 points

    Can you provide more details on what is meant by "cannot run normally"? What is going wrong?

    A. The initialization of the error object looks fine. Those should be valid parameters.

    B In the case of an uncorrectable error (which is the case with the GS7 parity error being injected in this code), an error flag will be set in the UCERRFLG--call STL_March_checkErrorStatus() to check it--and the RAMUNCERR flag will be set in the NMI registers. Make sure that there is an NMI ISR registered in the vector table that can clear the error so operation can continue normally.

    Whitney